I'm a software engineer too and I use TypeScript, React.js, and Node.js daily.
Thanks for this article who helped me to solve this automatic import in Vs Code issue.
May I ask you which font and theme you use in Vs Code?
I saw it many times in tutos and I would like to have it :)
It is supposed to exclude any node_modules folders at any depth, not just the root level node_modules folder (see this stack overflow post.
TBH I'm not entirely sure when this case would come up, but it certainly won't hurt to include it, since you wouldn't want Intellisense to be searching any node_modules folders.
It's likely that "exclude": ["node_modules"] is sufficient though.
For anyone reading in the future, "**/node_modules/*" helps when you have sub-directories/sub-projects that have their own node_modules [and package.json]
Same here,
auto import works as intended but it also checks the missing props on imported components, giving me errors all over. Modifying is not an option as it gives a lot error...
Has anybody found any solution for that ?
We're a place where coders share, stay up-to-date and grow their careers.
I'm a software engineer too and I use TypeScript, React.js, and Node.js daily.
Thanks for this article who helped me to solve this automatic import in Vs Code issue.
May I ask you which font and theme you use in Vs Code?
I saw it many times in tutos and I would like to have it :)
Have a nice day!
Emanuela
Cobalt2 by Wes Bos
Glad it helped!
Like Andrejs said, the theme is Cobalt2 and the font is Operator Mono. Fira Mono is another similar, free mono spaced font :)
Nice, helpful and to the point
Hi Shane,
After reading your post I have a doubt. In the last line of your script:
Shouldn't it be
"node_modules/**/*"instead of"**/node_modules/*"?Hi @zonaguillermo, thanks for reading :)
This is the suggested pattern from the VS Code docs.
It is supposed to exclude any
node_modulesfolders at any depth, not just the root levelnode_modulesfolder (see this stack overflow post.TBH I'm not entirely sure when this case would come up, but it certainly won't hurt to include it, since you wouldn't want Intellisense to be searching any
node_modulesfolders.It's likely that
"exclude": ["node_modules"]is sufficient though.For anyone reading in the future,
"**/node_modules/*"helps when you have sub-directories/sub-projects that have their ownnode_modules[and package.json]Thanks Shane for de response,
I read these post and I see it more clearly now
I'm using TailwindCSS, so after creating jsconfig.json I had an issue:
If I delete "module": "ES6", the error will disappear.
I don't know why, but if you add the string into jsconfig.json:
it will work.
This can be helpful -> github.com/romansndlr/react-vite-r...
Doesn't work. I am using Vue.js

if i add checkJs then i have also error on types, like i'm working with ts files
Same here,
auto import works as intended but it also checks the missing props on imported components, giving me errors all over. Modifying is not an option as it gives a lot error...
Has anybody found any solution for that ?