@JetBrainsIDE @anstarovoyt hey guys! My friends and I are struggling with the unstable work of WebStorm lately. Especially, when trying to open the search using "double-shift", it just stucks and freezes whole IDE for 5-10 seconds every time.
-
Show this thread
-
Also, there is a number of smaller bugs like if I am trying to convert some type into a generic parameter, it concats with the parent type. It is a pretty frequent situation as React uses a lot of envelopes that essentially the same. Thus, I face this issue on the every day basispic.twitter.com/NJM0fLECqS
2 replies 0 retweets 0 likesShow this thread -
As a lot of your customers are using BEM-like syntax it will be nice to add the support for CSS module variables resolution. I'd like to write &__toggle instead of .nav_bar__toggle as it removes the overhead of nesting repetition in the bundle but IDE indicates it as an errorpic.twitter.com/bqdxJsoL1S
2 replies 0 retweets 0 likesShow this thread -
Although I have a .nvmrc file that indicates that I prefer to use the latest version of Node and NPM, IDE always switches to the v10.x every time I open the project. I think this behaviour is not preferable and I hope you will fix in the future releases :)
2 replies 0 retweets 0 likesShow this thread -
What's exactly in your .nvmrc file? Is this version installed on your machine? Currently, the IDE selects a node version from .nvmrc only if it's installed on your machine and you have system node (`node` alias) selected in Preferences - Node.js and npm and not an exact version.pic.twitter.com/xldVLLUEkm
1 reply 0 retweets 2 likes -
I've got `lts/*` in my .nvmrc and node v12.13 installed on my machine. The 12th version is LTS for now, I suppose it should be automatically be selected when IDE openspic.twitter.com/IDvJxqe2cg
1 reply 0 retweets 0 likes
Thanks! WebStorm 2020.1 (currently available under an early access program: ) can understand aliases including lts/*: https://youtrack.jetbrains.com/issue/WEB-42577 Please give it a try!
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.