Serverless Stack

man, I’m ready to rage-quit VS Code. anyone else have this issue where you save a simple file and it shows this for like a whole minute?oddly enough, it’s only in my SST project :thinking_face:

Huh I’m not sure if this is the same one but <@U01JVDKASAC> was close to rage quitting VSCode over a lint issue too. He had to restart it.

ha.  I mean, this is why I left Webstorm, because VS Code was so much snappier. but now.. :man-shrugging:

I found that working with any project with anything approaching scale made VSC grind to a halt in various ways - linting, debugging, intellisense. I feel like I should be on commission for JetBrains the number of people I’ve said “use WebStorm” to instead.

I think the latest update has some issues.

I came from Webstorm. it’s good, but MAN is it a giant beast. they should’ve not used Java IMO, but C#/C++ instead.

LOL, I’ve found that giving WebStorm the memory it needs and it works well. With VC you don’t have that flexibility

also, Webstorm’s TypeScript engine kept quitting on me

and it took them forever to fix it, then it broke again

which is not acceptable for paid software

Oh, I’ve been using it for the past 6 months without issue

maybe it’s good now. and I know you work with Vue too

I had this problem, it was ESLint and another extension that were in conflict

yeah, although….Vue has been the thing I’ve kept with VSC for! Mainly because Volar and Vetur were so good. However, in the latest release there are lots of Vue related changes but haven’t tried them out yet

ok. disabled ESLint. when I reformat the code using Prettier, it also hangs and there’s a progress bar at the top. so.. must be another extension

Personally I had to disabled Import Cost, but it could be something else. Let me find exactly what I used to fix it, some kind of helper in VSCode

Basicaly just start Bisect in VSCode, it&lt;ll disable half your extension and you can test it, then keep going until you find the one which is causing the problem

had no idea that was a thing. thanks for that :slightly_smiling_face:

Worked pretty well for me, hope it fixes your issue too!

of course, now it behaves fine because it knows it’s under suspicion :laughing:

<@U03E44RBCTE> wow, two culprits! Error Lens and IntelliSense for CSS class names. the former is leaving error msgs all over the code even after you fix something, and the latter was responsible for hanging VS Code when cmd-clicking on variables or hovering over them to get details

Glad you fixed it! It was driving me crazy to have to wait a minute every time I was hitting save :stuck_out_tongue:

<@U03E44RBCTE> ha. Import Cost was actually the culprit, not the CSS intellisense

yeah I think it got broken by recent VSCode updates somehow

I am having this issue currently. I will try to disable import cost.