We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug
cmd+click (or ctrl+click on windows) doesn't seem to work on npm specifier paths.
To Reproduce
deno.json
{ "imports": { "svelte": "npm:svelte@4.2.8", "svelte/": "npm:/svelte@4.2.8/" } }
foo.ts
import * as sv from "svelte/internal"; console.log(sv);
deno run -A foo.ts
svelte/internal
Expected behavior
cmd+click (or ctrl+click on windows) should go to the source definition.
Screenshots
Versions
vscode: insiders from 2023-12-05 deno: 1.38.5 extension: v3.28.0
The text was updated successfully, but these errors were encountered:
There seems to be a slight improvement, I can go to the module but definition from imported files inside of the module can't be reached.
vscode: 1.89.1 extention: 3.37.1 deno 1.43.4 (release, x86_64-unknown-linux-gnu) v8 12.4.254.13 typescript 5.4.5
Sorry, something went wrong.
@marvinhagemeister I upgraded to deno 1.43.6, now it works \o/
No branches or pull requests
Describe the bug
cmd+click (or ctrl+click on windows) doesn't seem to work on npm specifier paths.
To Reproduce
deno.json
with these contents:foo.ts
with these contents:deno run -A foo.ts
foo.ts
in vscode and try to click on thesvelte/internal
import specifier.Expected behavior
cmd+click (or ctrl+click on windows) should go to the source definition.
Screenshots
lsp-resolve-npm.mp4
Versions
vscode: insiders from 2023-12-05 deno: 1.38.5 extension: v3.28.0
The text was updated successfully, but these errors were encountered: