-
Notifications
You must be signed in to change notification settings - Fork 12.9k
Use node moduleResolution everywhere #47687
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
Conversation
TestRunner was already using it, but upstream projects (e.g. Compiler) were not, causing TestRunner to re-parse and re-bind all upstream files in (at least) editor scenarios), slowing down initial project load. In local testing, this cut a find-all-refs call in checker.ts from 5s to 2.5s.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All for it, I can't believe this would harm anything.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the concern might've been with accidentally importing things. I don't think it's a big enough concern to block this change.
Just tried a build with this change. After a cold start the language service is definitely quicker to respond to a find-all-references. Nice find! |
I'm planning to add some tracing so we can warn others if it's happening to them. |
...to help detect misconfigurations like microsoft#47687.
...to help detect misconfigurations like #47687.
Just want to say - thank you for adding this trace. It helped us debug why |
TestRunner was already using it, but upstream projects (e.g. Compiler) were not, causing TestRunner to re-parse and re-bind all upstream files in (at least) editor scenarios), slowing down initial project load.
In local testing, this cut a find-all-refs call in checker.ts from 5s to 2.5s.