You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Deno LSP should not use the information from package.json if there's already an deno.jsonc.
Could not set npm package requirements. Error getting response at https://registry.npmjs.org/@mantine/core for package "@mantine/core": An npm specifier not found in cache: "@mantine/core", --cached-only is specified.
for example, despite having enablePaths defined, vscode deno extension tries to analyze node path (src/App.tsx) which is not in enablePaths, ending up in error.
Describe the bug
Deno LSP occasionally loses tsconfig lib info when working in mixed nodejs and deno environment.
To Reproduce
It's not guaranteed to be reproducible, but i got into this bug via
scripts/
subdirectoryscripts/
, suddenlylib
info is gone such as"lib": ["deno.window"],
.vscode/settings.json
deno.jsonc
tsconfig.json
Expected behavior
Deno LSP should not use the information from
package.json
if there's already andeno.jsonc
.for example, despite having
enablePaths
defined, vscode deno extension tries to analyze node path (src/App.tsx
) which is not inenablePaths
, ending up in error.Screenshots
2024-03-21_08-37-44.mp4
Versions
vscode: 1.87.0 deno: 1.41.3+2ce6451 extension: v3.35.1
The text was updated successfully, but these errors were encountered: