foster/denoland-deno
0
0
Fork 0
mirror of https://github.com/denoland/deno.git synced 2025-02-24 06:02:18 -05:00
Code Issues Packages 1 Wiki Activity
denoland-deno/tests/registry/npm/@denotest/augments-global/1.0.0/package.json

13 lines
223 B
JSON
Raw Normal View History

fix(check/lsp): correctly resolve compilerOptions.types (#27686) Fixes https://github.com/denoland/deno/issues/27062 In the LSP we were passing `npm` specifiers to TSC as roots, but TSC needs fully resolved specifiers (like the actual file path). In `deno check` we were often excluding the specifiers entirely from the roots. In both cases, we need to resolve the specifiers fully and then pass them to tsc
2025-01-15 18:48:10 -08:00
{
"name": "@denotest/augments-global",
"version": "1.0.0",
fix(check/lsp): fix bugs with tsc type resolution, allow npm packages to augment `ImportMeta` (#27690) Fixes #26224. Fixes #27042. There were three bugs here: - we were only resolving `/// <reference types` directives starting with `npm:`, which meant we failed to resolve bare specifiers (this broke the `/// <reference types="vite/client">` directive in most of the vite templates) - the `$node_modules` workaround caused us to fail to read files for tsc. For instance tsc would construct new paths based on specifiers containing `$node_modules`, and since we hadn't created those we weren't mapping them back to the original (this broke some type resolution within `vite/client`) - our separation of `ImportMeta` across node and deno globals in tsc meant that npm packages couldn't augment `ImportMeta` (this broke `vite/client`'s augmentation to add `import.meta.env` and others) After this, the only remaining issue in the vanilla vite template is our error on `/vite.svg` (which is an ambient module), and I'll look into that next.
2025-01-16 11:20:04 -08:00
"types": "./index.d.ts",
"exports": {
".": {
"types": "./index.d.ts"
},
"./import-meta": {
"types": "./import-meta.d.ts"
}
}
fix(check/lsp): correctly resolve compilerOptions.types (#27686) Fixes https://github.com/denoland/deno/issues/27062 In the LSP we were passing `npm` specifiers to TSC as roots, but TSC needs fully resolved specifiers (like the actual file path). In `deno check` we were often excluding the specifiers entirely from the roots. In both cases, we need to resolve the specifiers fully and then pass them to tsc
2025-01-15 18:48:10 -08:00
}
Copy permalink