{"id":245446,"date":"2022-05-10T16:11:09","date_gmt":"2022-05-10T15:11:09","guid":{"rendered":"https:\/\/blog.jetbrains.com\/?post_type=webstorm&#038;p=245446"},"modified":"2022-08-09T17:17:14","modified_gmt":"2022-08-09T16:17:14","slug":"webstorm-2022-2-roadmap","status":"publish","type":"webstorm","link":"https:\/\/blog.jetbrains.com\/de\/webstorm\/2022\/05\/webstorm-2022-2-roadmap","title":{"rendered":"What\u2019s Next: WebStorm 2022.2 Roadmap"},"content":{"rendered":"\n<p>Last month, we rolled out <a href=\"https:\/\/blog.jetbrains.com\/webstorm\/2022\/04\/webstorm-2022-1\/\">WebStorm 2022.1<\/a>, our first major update of 2022. Today we want to tell you about our plans for the next release coming this July. The main focus will be on improving the overall quality of the product and fixing some long-standing bugs.<\/p>\n\n\n\n<ul><li><strong>Improvements for Vue<\/strong>. Our support for Vue 3 has lagged behind some of the latest Vue updates. To address this, we\u2019ll be prioritizing Vue 3 bug fixes and features so we can solve the most critical problems. You can also expect <a href=\"https:\/\/youtrack.jetbrains.com\/issue\/WEB-46507\/Support-for-vite\" target=\"_blank\" rel=\"noopener\">support for Vite<\/a>, a popular build tool, in the first bug-fix update for WebStorm 2022.1.<\/li><li><strong>TypeScript housekeeping<\/strong>. We\u2019re working on a bunch of TypeScript-related tasks to keep WebStorm\u2019s TypeScript support in good shape. We\u2019ve updated the bundled version to 4.6, and we\u2019re getting ready for the TypeScript 4.7 release by adding support for new language features like <code>extends<\/code> constraints on <code>infer<\/code> type variables (<a href=\"https:\/\/youtrack.jetbrains.com\/issue\/WEB-55516\" target=\"_blank\" rel=\"noopener\">WEB-55516<\/a>) and optional variance annotations for type parameters (<a href=\"https:\/\/youtrack.jetbrains.com\/issue\/WEB-55517\/TypeScript-4.7:-Optional-Variance-Annotations-for-Type-Parameter\" target=\"_blank\" rel=\"noopener\">WEB-55517<\/a>).<\/li><li><strong>Minor updates for Angular<\/strong>. We\u2019re planning to ship some fixes for Angular users, including the one for the wrong <code>keyvalue<\/code> pipe type evaluation (<a href=\"https:\/\/youtrack.jetbrains.com\/issue\/WEB-51209\/Angular-KeyValue-pipe-wrong-TS-generic-type-evaluation\" target=\"_blank\" rel=\"noopener\">WEB-51209<\/a>). We&#8217;re also looking into what improvements are going to land in Angular 14 to understand what we\u2019ll need to be implemented on the IDE side. We\u2019ve already solved a couple of related problems (<a href=\"https:\/\/youtrack.jetbrains.com\/issue\/WEB-55218\" target=\"_blank\" rel=\"noopener\">WEB-55218<\/a> and <a href=\"https:\/\/youtrack.jetbrains.com\/issue\/WEB-55519\" target=\"_blank\" rel=\"noopener\">WEB-55519<\/a>). Additionally, we\u2019re going to remove the AngularJS project template from the <em>New Project <\/em>dialog, as AngularJS has reached its end of support.<\/li><li><strong>A new built-in remote development workflow<\/strong>. With WebStorm 2021.3, we introduced a beta version of our <a href=\"https:\/\/www.jetbrains.com\/help\/webstorm\/remote-development-starting-page.html\" target=\"_blank\" rel=\"noopener\">new remote development workflow<\/a>, with JetBrains Gateway. We were planning to bundle it with v2022.1, but we had to postpone this decision until the next release. We hope we\u2019ll fix the remaining bugs and make the functionality available out of the box in v2022.2.<\/li><\/ul>\n\n\n\n<p>That\u2019s about it. We can\u2019t guarantee that all these improvements will be included, but we\u2019ll do our best to make it happen. Stay tuned for information about the upcoming start of the Early Access Program for 2022.2!<\/p>\n\n\n\n<p>P.S. We\u2019re actively looking for brave souls to join our team as software developers. If you\u2019ve ever thought about becoming an <a href=\"https:\/\/blog.jetbrains.com\/webstorm\/2021\/05\/a-day-in-the-life-of-a-webstorm-developer\/\">IDE developer<\/a> and have knowledge of Java or Kotlin, don\u2019t miss the chance to <strong>apply for a WebStorm software developer position <\/strong><a href=\"https:\/\/www.jetbrains.com\/careers\/jobs\/senior-software-developer-webstorm-131\/\" target=\"_blank\" rel=\"noopener\"><strong>here<\/strong><\/a>.<\/p>\n\n\n\n<p><em>The WebStorm team<\/em><\/p>\n","protected":false},"author":989,"featured_media":245448,"comment_status":"closed","ping_status":"closed","template":"","categories":[89],"tags":[1731,6984],"cross-post-tag":[],"acf":[],"_links":{"self":[{"href":"https:\/\/blog.jetbrains.com\/de\/wp-json\/wp\/v2\/webstorm\/245446"}],"collection":[{"href":"https:\/\/blog.jetbrains.com\/de\/wp-json\/wp\/v2\/webstorm"}],"about":[{"href":"https:\/\/blog.jetbrains.com\/de\/wp-json\/wp\/v2\/types\/webstorm"}],"author":[{"embeddable":true,"href":"https:\/\/blog.jetbrains.com\/de\/wp-json\/wp\/v2\/users\/989"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.jetbrains.com\/de\/wp-json\/wp\/v2\/comments?post=245446"}],"version-history":[{"count":9,"href":"https:\/\/blog.jetbrains.com\/de\/wp-json\/wp\/v2\/webstorm\/245446\/revisions"}],"predecessor-version":[{"id":245548,"href":"https:\/\/blog.jetbrains.com\/de\/wp-json\/wp\/v2\/webstorm\/245446\/revisions\/245548"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.jetbrains.com\/de\/wp-json\/wp\/v2\/media\/245448"}],"wp:attachment":[{"href":"https:\/\/blog.jetbrains.com\/de\/wp-json\/wp\/v2\/media?parent=245446"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.jetbrains.com\/de\/wp-json\/wp\/v2\/categories?post=245446"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.jetbrains.com\/de\/wp-json\/wp\/v2\/tags?post=245446"},{"taxonomy":"cross-post-tag","embeddable":true,"href":"https:\/\/blog.jetbrains.com\/de\/wp-json\/wp\/v2\/cross-post-tag?post=245446"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}