Today we’re happy to announce the beta release of WebStorm 2019.3! In this release cycle, we’ve focused mainly on fixing lingering bugs and performance issues, yet we’ve also managed to add some great new functionality. We encourage you to try it out and share your feedback with us.
Let’s take a brief look at the major improvements available in the beta version of WebStorm 2019.3.
Faster startup
On startup, you can now expect WebStorm to display the welcome screen and open your already indexed projects 20% faster than before. For now, the results are better for some operating systems than others, but we’ll keep improving this over the next release cycle.
More advanced Vue.js support
With every new WebStorm version released this year, we’ve extended its support for Vue.js, making it easier to build great apps with Vue.js. WebStorm 2019.3 is no exception: it comes with code completion for slot names, support for components defined in separate files, and quick documentation for Vue symbols (F1).
Name suggestions for new symbols in JavaScript
As you add new variable and parameter names in JavaScript or TypeScript files, you’ll now get name suggestions based on the names of classes, interfaces, and type aliases defined in the project, standard libraries, and dependencies you’re using.
For new variables, functions, classes, and interfaces, you’ll also get suggestions for names that were already used in the same scope but haven’t yet been defined and are marked as unresolved.
Support for the latest versions of popular technologies
WebStorm 2019.3 supports schematics with Angular 9 and the Plug’n’Play feature from Yarn 2. Plus, it can help you work with key TypeScript 3.7 features, such as optional chaining, nullish coalescing, and assertion signatures, with no additional configuration required.
Completion for CSS libraries on CDN
If you’re using Bootstrap or another CSS library and have it linked from a CDN in your HTML file, you can now get completion for the class names from that library, without adding its sources to the project.
Reworked UI for cloning projects
When you clone a project from a VCS, you’ll see an updated Get from Version Control dialog shown on the welcome screen and the VCS menu. The main goal of this update is to improve the experience of getting projects from GitHub: you can now log in to your GitHub account, explore the list of repositories, and clone projects to WebStorm right from the updated dialog.
Run Anything action
You can now launch tools like npm and Yarn, open recent projects, and start a run/debug configuration using a single Run Anything action (Ctrl-Ctrl) – there is no need to memorize all the shortcuts for these specific actions anymore.
Some other fixes and improvements include:
- You can now enable global file watchers by default for all new projects.
- You can push changes from one branch while working with another.
- For components without propTypes, WebStorm won’t report an unresolved property in this specific case.
- When searching for text in a file with Cmd/Ctrl-F, you can now limit the search to only the selected part of the code.
- There’s now a separate refactoring for extracting a constant (Alt-Cmd-C on macOS, Ctrl-Alt-C on Windows/Linux).
- TODOs in JSX code are now detected much better.
- It’s now possible to inject template languages into your code, including Pug (ex-Jade), Handlebars, and EJS.
Finally, just so you aren’t caught off guard, the timeline for GitHub pull requests won’t be included in WebStorm 2019.3. We’ll continue enhancing our support for GitHub pull requests, and we plan to make it available in one of our future releases.
Please report any issues on our issue tracker, and stay tuned for the upcoming release announcement!
The WebStorm Team
Hi, thank you for an update, been using 2013.3 EAP and was really happy about new stuff.
I’ve created a ticket of a behaviour that I’ve noticed, but not sure whether it’s a bug: https://youtrack.jetbrains.com/issue/WEB-42510
Hi, Ivan! Thanks for reporting this unexpected behavior. We’ll continue investigating it as part of this platform-wide issue: https://youtrack.jetbrains.com/issue/IDEA-169791. Please follow it for updates.
Thanks a lot, and sorry for the duplicate, I did try to find if this has been reported, but as you’ve witnessed I failed.
Is https://youtrack.jetbrains.com/issue/WEB-41564 going to be fixed for 2019.3? It’s a pretty big showstopper for me as Vue user.
Hello, Kirill! We’ll try to investigate and resolve this soon, however, the fix will be available in one of the bug-fix updates for WebStorm 2019.3, not in the release build – unfortunately, it’s too late to add any major fixes to the release build at the moment. Sorry for any inconvenience it might be causing you.