Skip to content
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

VS Code: "Not prefixed with... and not in import map from ..." #23835

Open
saeho opened this issue May 15, 2024 · 5 comments
Open

VS Code: "Not prefixed with... and not in import map from ..." #23835

saeho opened this issue May 15, 2024 · 5 comments
Labels
needs info needs further information to be properly triaged

Comments

@saeho
Copy link

saeho commented May 15, 2024

Version: Deno 1.14.3

Hello,

I have a VS code issue where import-map configured NPM packages are showing as errors. I saw a few threads like this but none of the threads I read solved my problem (even though the issues were very similar.

Here's an example:

On the Server Deno repo
This will show as an error in VS Code ("not prefixed with / and not in import map from..."):

import { ApolloServer } from '@apollo/server';

This is my deno.json:

"imports": {
    "@apollo/server": "npm:@apollo/server@^4.10.4",
    "graphql": "npm:graphql@^16.8.1"
  }

However, this exact imports map works in my Fresh Deno app repo and VS Code does not complain.

@lucacasonato
Copy link
Member

Is the deno.json at the root of your repo? Do you have a repo I can take a look at?

@lucacasonato lucacasonato added the needs info needs further information to be properly triaged label Jun 8, 2024
@saeho
Copy link
Author

saeho commented Jun 9, 2024

Yes, deno.json is at the root, and deno.json file works properly as it should. All the imports does the job properly, it's just VS Code that fails.

You can take a look at the repo but it's private. Can I give you private access?

@lucacasonato
Copy link
Member

Sure, can you invite @nayeemrmn and @nathanwhit?

@nayeemrmn
Copy link
Collaborator

If you're using deno.enablePaths ensure it contains the deno.json.

@nayeemrmn
Copy link
Collaborator

Also, try running deno upgrade.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs info needs further information to be properly triaged
Projects
None yet
Development

No branches or pull requests

3 participants