-
Notifications
You must be signed in to change notification settings - Fork 5.4k
New issue
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
Import maps (from deno.json > "imports") don't work in VS Code #25631
Comments
Is it fixed in the latest Deno version? |
Click the |
Thank you for the help. I'm somewhat new to TS/Deno and coding in VS Code, so I didn't know running the program would help the issue. Thanks again! |
You have closed the issue. Unfortunately I still have the problem. |
@cristian-spiescu What happens if you upgrade Deno to the latest (1.46.3)? |
@cristian-spiescu is the .vscode folder in the root directory of your vscode project? |
Version: Deno 1.41.2
It's only after the standard lib moved to JSR that I found out about the deno add command, and the "import maps" feature. Leveraging this,
deno.json
>imports
is somehow the equivalent ofpackage.json
>dependencies
.Before this, I was thinking that the pattern of
deps.ts
is the equivalent ofpackage.json
>dependencies
.However, I observe that in my case, VS Code doesn't recognize
deno.json
>imports
. I.e., I have this:But the IDE complains about this:
The program executes successfully. So Deno itself did recognize the import.
I tried various combination of
settings.json
:I also inspected
Output > Deno Language Server
, but nothing seemed suspect.Searching the Internet didn't gave much results. #20210 seems a bit related, but the context there (i.e. a
deno.json
being in a subdir of the project) is not similar to mine.The text was updated successfully, but these errors were encountered: