Investigate TypeScript intellisense slowness
See original GitHub issueMultiple users have reported TypeScript intellisense slowness for Chakra 1.0. We definitely want to make sure the DX for Chakra is excellent, so if this affecting you, please respond with the following information:
- Project type (next/CRA/etc.)
- Chakra version
- OS version
- IDE+version
- TypeScript version
- Paste a copy of your
tsconfig.json
Issue Analytics
- State:
- Created 3 years ago
- Reactions:9
- Comments:28 (18 by maintainers)
Top Results From Across the Web
Typescript intellisense is slow · Issue #45327 - GitHub
I use keyboard shortcut to trigger it. There is still much CPU and memory available but the intellisense is slow.
Read more >Typescript background compilation is very slow, sometimes ...
Typescript background compilation is very slow, sometimes hangs - Visual Studio Feedback.
Read more >VScode intellisense very slow when 'node_modules' is present
VScode intelliSense is way too slow when working with a certain TypeScript, NextJs project. The problem seemed to be the node_modules folder ......
Read more >Troubleshooting Tips for IntelliSense Slowness - C++ Team Blog
Having spent a lot of time helping customers with slow IntelliSense, I have found that their performance issues are almost always related to...
Read more >Slow typescript intellisense in React Nextjs project - Reddit
Slow typescript intellisense in React Nextjs project · You really should be using an SSD as your primary drive for multiple reasons these...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
We’ve made good improvements to the types of all components. Expect the TypeScript IntelliSense to be fast after the next
rc
release.We’ve also moved most component prop definition from
type
tointerface
which is a massive win when it comes to speed of resolving types. All these with theas
prop still working well 🥳Thanks to @ljosberinn for leading the effort.
The typescript intellisense is based on the typescript language server that tsc itself uses, so we can use the tsc compile time as a metric of intellisense speed.
Looking at the code there are a lot of types that could be optimized
PropsOf
to declare the components props type we should declare the props as a concrete type, this way tsc has less code to evaluatePropsOf
inChakraComponent
and other relative types