Nathan Whitaker 08f5e797b6 fix(check/lsp): fall back to @types/* packages if npm package doesn't have types (#28185) ... Fixes https://github.com/denoland/deno/issues/27569. Fixes https://github.com/denoland/deno/issues/27215. This PR makes it so type resolution falls back to looking for definitely typed packages (`@types/foo`) if a given NPM package does not contain type declarations. One complication is choosing _which_ version of the `@types/*` package to use, if the project depends on multiple versions. The heuristic here is to try to match the major and minor versions, falling back to the latest version. So if you have ``` @types/foo: 0.1.0, 0.2.0, 3.1.0, 3.1.2, 4.0.0 foo: 3.1.0 ``` we would choose `@types/foo@3.1.2` when resolving types for `foo`. --- Note that this only uses `@types/` packages if you _already_ depend on them. So a follow up to this PR could be to add a diagnostic and quickfix to install `@types/foo` if we don't find types for `foo`.		2025-02-19 23:55:06 +00:00
..
server	fix(check/lsp): fall back to @types/* packages if npm package doesn't have types (#28185)	2025-02-19 23:55:06 +00:00
std@1f032bb7e1	chore: update std in test util (#27892)	2025-01-31 08:52:32 -05:00