Module paths aliases NOT integrating automatically with vscode #15779
Unanswered
tomasgil123
asked this question in
Help
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Bug report
Vscode complains it is unable to resolve path to module when using absolute paths, but modules are found when run "npm run dev".
To Reproduce
Download the branch custom_eslint_config from the following repository and open it in vscode: https://github.com/tomasgil123/nextjs-blog/tree/custom_eslint_config
Expected behavior
Vscode should NOT complain about absolute paths which actually work.
Screenshots
My jsconfig.json:

Vscode complaining about the absolute path:

My folder structure:

System information
Beta Was this translation helpful? Give feedback.
All reactions