-
Notifications
You must be signed in to change notification settings - Fork 12.8k
Can't use auto import when node_modules are named "node_modules" #29629
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
Comments
Does this reproduce in the latest VS Code insiders build with all extensions disabled? |
Same thing here on Insiders also |
I also have this issue. I can confirm that changing the name of "node_modules" to "node_modules2" fixes the issue. Is there another fix that does not require this change? |
I confirmed this using TS 3.3-rc and a new angular app created from the CLI.
|
This issue provides a repro: microsoft/vscode#67505 |
Probably related: #29039 |
The reason renaming the node_modules folder works is that the default value of It’s possible that’s what’s happening, but there’s not enough information here to know for sure yet. To test that theory, can you try adding an |
I just did this myself, and the auto-import for I will note, though, that despite our current stance that this is a “working as intended,” we are paying attention to the fact that users are frequently confused by this behavior and/or request that the behavior change, and I’m brainstorming ways to make the experience better. Just can’t promise anything specific yet. |
This issue has been marked as a 'Duplicate' and has seen no recent activity. It has been automatically closed for house-keeping purposes. |
I have the same issue with HttpClientModule. Just see no suggestion. #29629 (comment) |
Steps to Reproduce:
Then no auto import is available. BUT!! if I change name from


node_modules/
tonode_modules2/
then everything is fine. I've tried few "fixes" with no success.Screens
Does this issue occur when all extensions are disabled?: Yes
The text was updated successfully, but these errors were encountered: