WebStorm 2020.1.1, the first bug-fix update for the recently released WebStorm 2020.1, is now available!
You can update to it using the Toolbox App or right from the IDE. You can also download WebStorm 2020.1.1 from our website.
This bug-fix update comes with a couple of long-awaited enhancements, such as:
- A new option for running eslint –fix on save (WEB-24452): To enable this option for the current project, go to Preferences/Settings | Languages and Frameworks | JavaScript | Code Quality Tools | ESLint and tick the Run eslint –fix on save checkbox. To turn the new option on for all new projects, from the main menu go to File | New Project Settings | Preferences/Settings for New Projects and tick the same checkbox. Either way, don’t forget to disable the file watcher you’ve been using for this purpose.
- Improvements to WSL 2 support (WEB-44463, WEB-44507): You can now use the TypeScript Language Service, linters, and Prettier in projects located in the WSL file system. Besides that, we’ve fixed the issue where the IDE failed to stop the running Node.js process whenever you tried to hit the Stop button (for information on how to use Node.js on WSL, see our documentation).
Here are some smaller but notable changes:
- Support for the ESLint 6.7 Suggestions API was added (WEB-44070).
- Hammer.js events are now recognized in Angular templates (WEB-43773).
- Several performance problems were solved (WEB-44844, WEB-43906, WEB-45024, IDEA-237965, and WEB-44548).
- Dependencies from pnpm workspaces are now properly indexed (WEB-44669).
- A number of disturbing, platform-wide bugs were fixed (including IDEA-229467, IDEA-233252, and IDEA-232070).
For the full list of issues addressed in WebStorm 2020.1.1, please see the release notes.
The WebStorm team
> disturbing, platform-wide bugs
I so much love it when vendors are honest. Thank you. I hope management is supportive.
Hi,
We have an open issue tracker where users can express how disturbing a specific problem for them is by voting for the corresponding issue. All the bugs mentioned in that part of the blog post got quite a lot of votes so I’d say that they can be classified as “disturbing” :)
imac is stuck when using the latest version, what is the reason? Memory 8G
Hi,
We can’t say what the reason is without more context around the problem and proper investigation. Please file a new issue here: https://youtrack.jetbrains.com/issues/WEB, sharing more information as described here: https://intellij-support.jetbrains.com/hc/en-us/articles/207241235-Reporting-performance-problems. Our support team may also want to look at the IDE logs, which can be collected from the main menu (Help | Collect Logs…).
since 2020.1 the typing has become sluggish and especially in the terminal window which became practically unusable. Had to revert back to 2019.3. Mac Catalina. What gives?
Hello Andrei,
Is it applicable to v2020.1.1 as well? If you decide to go back to v2020.1/v2020.1.1 and find yourself experiencing the same problem there, please share more details with our support team: https://intellij-support.jetbrains.com/hc/en-us/requests/new (see https://intellij-support.jetbrains.com/hc/en-us/articles/207241235-Reporting-performance-problems for more info). They may also want to look at the IDE logs (Help | Collect Logs…). Unfortunately, we can’t troubleshoot a problem without more context around it.
The new Color Picker UX when clicking on the color shortcut on the left side of the window is really bad and a huge usability step backwards. Not having the normal Color Picker (alt-c) forces me to use undo to return to original color if I try 5 or 6 that I don’t like. Also, the interactive picker tool in this new UX doesn’t seem to work at all. We use this tool A LOT, so this is a huge productivity-loss issue. Is there someway to configure WebStorm to always use the normal/default Color Picker UX (alt-c) instead of this new one?
Hi John,
Thanks for sharing your feedback. You can get the old color picker back by going to Registry (Shift+Shift, type Registry and open it) and unticking the ide.new.color.picker option there. Please let me know if it works for you.
Ekaterina, Yes, fantastic! Changing the setting in the registry restores the original color picker. Thank you so much!
Thanks for the update, John! I’m happy to hear that it helped.