Check back to this blog next year for progress reports on this. This will allow WebStorm to deliver more accurate completion suggestions and thus make it easier for you to write quality code faster. We’ve started experimenting with code completion powered by machine learning for JavaScript and TypeScript. We’re going to make WebStorm more helpful for working with the technologies it supports. Helping you get more out of the supported technologies Everything described in that post applies to WebStorm as well. If you want to learn more about the planned performance improvements, you can take a look at the blog post which unveiled the IntelliJ Platform roadmap. In the next release cycle, we’ll try to extend this support to other types of plugins. In WebStorm 2019.3, this already works for most theme and keymap plugins. We also want to ease the process of installing and updating plugins so that you can manage them without restarting the IDE. We’ll keep optimizing this part of the IDE.īesides that, we plan to lay some groundwork that will make indexing less disruptive to let you perform more actions while the indexing is still in progress. In 2019, we’ve introduced a number of architectural changes that have significantly reduced the startup times. Until we released v2019.3, a common performance problem WebStorm users faced had been its sluggish startup. Let’s take a closer look at what exactly we’re going to focus on. Second, we’ll add some new functionality and enhance support for frameworks and commonly used tools like Prettier to help you work with them more efficiently. First of all, we’ll continue to optimize performance in order to make WebStorm more lightweight. We’re now ready to share our plans for the upcoming release, which is scheduled for the beginning of April 2020. The end of the year kept us pretty busy: we released WebStorm’s third major update in 2019, published the first bug-fix update for it, and came to terms with the roadmap for v2020.1.
0 Comments
Leave a Reply. |