You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I believe the original suggestions may have come from your path-intellisense extension. I say that because I don't know think we ever properly supported the paths config option for our built-in path intellisense (microsoft/TypeScript#19113)
Using VS Code insiders, can you try setting "typescript.quickSuggestionsForPaths": false. This should prevent our built-in path intellisense from automatically kicking in
I've tried with latest VS Code Insiders – import path autocomplete does not recognize tsconfig's paths option correctly. Keys from the paths map appear as is, they are not being processed from globs to matches.
Tried with and without quickSuggestionsForPaths, path-intellisense extension.
Version 1.18.0-insider (1.18.0-insider), 2ab10d5, 2017-11-01T06:07:36.569Z
This issue has been closed automatically because it needs more information and has not had recent activity. Please refer to our guidelines for filing issues. Thank you for your contributions.
Problem:
Path suggestions for absolute paths (configured in tsconfig) break for import statements in version 1.17 as soon as @typings are installed.
Without the @typings folder anywhere in the project, everything works fine.
In version 1.16.1 it even works fine WITH the typings installed :
But when I do for instance :
after that is installed, this is what I get for suggestions instead of above screenshot (it seems that it only suggests installed types) :
(1 theme extensions excluded)
Steps to Reproduce:
Reproduces without extensions: No (doesn't work either way)
The text was updated successfully, but these errors were encountered: