Typescript running very slowly (in VSCode) #623
Replies: 2 comments 3 replies
-
@sandgraham I think I've noticed the same thing. I will do some tests to make sure. PS I've never used Github discussions before and it feels weird that this has to be submitted as an 'answer' when I just want to add a comment. |
Beta Was this translation helpful? Give feedback.
-
Thanks for that. Good news is, this week we're starting a "TypeScript sprint". Where we'll be addressing many of the known TS related issues, including its performance. I'll post an update when this is released. Thanks! 🚀 |
Beta Was this translation helpful? Give feedback.
-
Hi, I've noticed that as I've started building components with stitches, the typescript checking/intellisense in VSCode has started to slow down dramatically (I also use ESLint).
It's pretty common for me to wait a few seconds to see a TS linting error appear or disappear. Autocompletion for variant props or style objects takes a few seconds to appear as well. Often when I open a file using/defining a styled component the fans on my laptop start whirring loudly.
I think it might have something to do with using
StitchesVariants
or the polymorphic typing util- which I have to use often when wrapping a styled component. Importing either generally gets the fans started (but sometimes just using a styled component is enough).When I started my project with stitches it was pretty awesome how the types seemed to flow through everything. But as the project has grown (still not that big), the sluggish type checking/intellisense issue has become more pronounced.
I'm wondering if others have run into this issue and if so how they might have alleviated it.
Beta Was this translation helpful? Give feedback.
All reactions