-
Notifications
You must be signed in to change notification settings - Fork 12.5k
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
VSCode intellisense not working with typescript 3.7.5 in Angular projects #37187
Comments
Does it work as expected with Ts 3.8? I believe they fixed a few bugs related to newer angular versions in that release |
I pushed up the setup that was generated by angular's cli tool: https://github.com/admosity/angular-9-vscode-intellisense Maybe it could just be me... |
Verified in 3.9.0-dev.20200303 |
Ideally |
This issue has been marked as a 'Duplicate' and has seen no recent activity. It has been automatically closed for house-keeping purposes. |
@admosity did you ever find a solution? This seems like an issue I have at work. We have a parent library/project which contains all the dependancies in its package json (angular, rxjs, etc). Our child apps have only the parent in their package.json now so we don't need to worry about updating every app's package.json, but now imports don't work. I've tried adding to |
TS Template added by @mjbvz
TypeScript Version: 3.7.5
Search Terms
Using the latest vscode with Typescript 3.7.5, intellisense breaks for anything referencing
node_modules
. This is reflected on new projects created with@angular/cli
as well. Tested on an Angular 7 project to see if the version difference between Angular 7 and Angular 9 made a difference.Steps to Reproduce:
node_modules
(e.g. ReactiveFormsModule from Angular).ctrl+space
or whatever is the intellisense hotkey is configured..No Suggestions
appears.Switching to the lower workspace Typescript version in my Angular 7 setup I can get the suggestions to show again.
Video reproduction with Typescript version switch:
On a fresh Angular 9 setup:
Does this issue occur when all extensions are disabled?: Yes
Same project in Atom:
EDIT: This appears to be happening in Atom with Typescript 3.7.5 as well now in the Angular 9 setup. Might be specifically a Typescript 3.7.5 issue.
EDIT EDIT: It seems that adding
node_modules/@angular
as a typeRoot fixes some issues:TSCONFIG:
It seems that adding
node_modules/@angular
as a typeRoot fixes some issues:The text was updated successfully, but these errors were encountered: