![\"released_blog_pic\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2021\/11\/Release_Blog_image_1280x720_-WebStorm.png\")
<\/p>\n
If you only have a few minutes to explore what\u2019s new in WebStorm 2021.3, watch this video<\/a> where Paul Everitt<\/a>, Developer Advocate at JetBrains, walks you through the most notable changes. If you feel like diving deeper, read on!<\/p>\n The new features and improvements fall into these categories:<\/p>\n This release comes with a number of improvements for working with monorepos. The most notable change is that automatically added imports now respect the project structure by treating each folder in the project with package.json<\/em> as a separate package.<\/p>\n We understand that WebStorm\u2019s performance may not be optimal at times, so we\u2019re constantly working to improve it. Quite often, the changes related to performance are subtle, and you may not notice them unless you use a timer or a CPU profiler. In this release, we’ve managed to achieve more noticeable results, decreasing the indexing times for JavaScript files by 20%.<\/p>\n We hope this improvement will help you to get working faster when you open a new project or do a massive Git update. Please note that the change will be less noticeable if your project mainly consists of TypeScript or other types of files.<\/p>\n Starting from v2021.3 you can download remote ES6 modules using a quick-fix on the import path in ES6 files. The module with all its dependencies will be downloaded and linked as a project library. The functionality should work the same way it does in the browser. To give it a try, place the caret on the import path, then press \u2325\u23ce \/ Alt+Enter<\/em> and select Download module<\/em>.<\/p>\n Support for private fields was added to WebStorm back in 2018. However, as this support was based on the old proposal from TC39, it has since diverged from the standard. To comply with the standard, we\u2019ve reworked the existing support from the ground up \u2013 WebStorm 2021.3 will support ES2022 private class members. When you use private names \u2013 elements starting with #<\/em> \u2013 for your fields, accessors, or methods, everything should work as expected. For example, here\u2019s how the rename refactoring will work in v2021.3.<\/p>\n There are two new intentions for organizing your code in WebStorm 2021.3.<\/p>\n You can now quickly put comma-separated elements on one or multiple lines. The new intention works for array and object literals, parameter and argument lists, XML, HTML, and JSX attributes, and other similar elements.<\/p>\n To try the intention, place the caret on the elements you want to alter, then press \u2325\u23ce \/ Alt+Enter<\/em> and select either Put comma-separated elements on one line<\/em> or Put comma-separated elements on multiple lines<\/em> as appropriate. For XML, HTML, and JSX, you\u2019ll see slightly different wording for this action \u2013 Put attributes on separate lines<\/em> or Put attributes on one line<\/em>.<\/p>\n The second intention that was added relates to JSDoc comments. WebStorm can now help you replace single and multi-line comments with JSDoc comments in one click. As usual, you can access the available context actions with \u2325\u23ce \/ Alt+Enter<\/em>.<\/p>\n Another improvement in this release touches .js <\/em>and .d.ts<\/em> files. We\u2019ve improved mapping between them and added gutter icons for better navigation. To learn more about the changes, read this blog post<\/a>.<\/p>\n Over the years, we’ve added features<\/a> to help you add and update packages from the package.json<\/em> file, as well as to help you get relevant information about those packages. With this release, we\u2019ve made some changes that should make the management of project dependencies easier.<\/p>\n You can now update npm packages to the latest version right from the editor. Open your package.json <\/em>file, place the caret on the package version you want to update, then press \u2325\u23ce \/ Alt+Enter<\/em> and select Update \u2018package name\u2019 to the latest version<\/em>. A quick-fix will also be shown when you hover over the package version.<\/p>\n By default, the new inspection only provides a quick-fix, and doesn\u2019t highlight the outdated package in any way. If you want the warnings to be more prominent, you can change the inspection severity level in Preferences \/ Settings | Editor | Inspections<\/em> \u2013 look for Update package.json dependencies<\/em> there.<\/p>\n Previously, WebStorm would allow you to manage your packages through the corresponding section in Preferences \/ Settings | Languages and Frameworks | Node.js and NPM<\/em>. As only a few users managed their packages this way, we decided to remove this section and introduce a more straightforward way to handle the task \u2013 the new inspection described above.<\/p>\n Lastly, we\u2019ve renamed the Node.js and NPM<\/em> section in Preferences \/ Settings<\/em> to Node.js<\/em> to avoid any confusion. Just like before, you can use it to select a Node interpreter and the package manager of your choice: npm, pnpm, or Yarn.<\/p>\n Last year we introduced support for Deno in WebStorm. It relied on WebStorm’s integration with the TypeScript service as well as on the typescript-deno plugin<\/a>. There were several drawbacks to this implementation, and it hasn\u2019t been working reliably lately. Because of this, we\u2019ve completely reworked it and migrated to the Deno LSP. We\u2019ve also fixed a bunch of known issues. You can learn more about the biggest changes that we have made here<\/a>.<\/p>\n To learn more about working with Deno, see this blog post<\/a>. It already includes information about the recent changes.<\/p>\n One of the most pressing problems that we\u2019ve addressed in this release is support for Angular 13. It was broken because of the changes to the Angular Package Format. WebStorm 2021.3 takes these changes into account and supports the new version of Angular.<\/p>\n We\u2019ve improved the way code completion works in HTML. Now, whenever you type a tag name or an abbreviation in the editor, or invoke code completion, WebStorm will show you relevant suggestions right away. Previously, it would only show them if you typed < <\/em> first. We realized that this wasn\u2019t very comfortable for those of you who aren\u2019t used to typing < <\/em>and ><\/em> and for those of you who aren\u2019t familiar with Emmet.<\/p>\n Additionally, code completion for character entity references should work better now.<\/p>\n In between the 2021.2 and 2021.3 releases, we\u2019ve shipped a bunch of long-awaited fixes for Vue, including support for script setup<\/em><\/a>. In this release, we\u2019ve added another useful improvement \u2013 WebStorm 2021.3 supports TypeScript type checking in Vue templates. The IDE will let you know when an incorrect type is used in the expressions bound to properties.<\/p>\n This will also work for React attributes.<\/p>\n In this release, we\u2019ve significantly improved WebStorm\u2019s built-in HTTP client. We\u2019ve added a lot of new functionality, including support for binary responses, output redirection to a custom file or directory, support for text and JSON streams, and support for HTTP request identifiers.<\/p>\n Read this blog post<\/a> to take a closer look at these new features.<\/p>\n As one of the biggest and longest-awaited updates of this release \u2013 WebStorm now has support for remote development workflows<\/a>! You can connect to a remote machine with an IDE backend running and work on a project located there as if it were located on your local machine. We hope this helps you stay more productive and flexible while allowing you to work securely from anywhere.<\/p>\n Support for remote development workflows is provided through our new application: JetBrains Gateway. It serves as an entry point for all your remote backends and doesn\u2019t require you to have an IDE installed on your local machine. You can grab the latest version of JetBrains Gateway from our website<\/a>. Here\u2019s what you\u2019ll see after doing this:<\/p>\n For more information on how to get started, please refer to the documentation<\/a>.<\/p>\n Please note that this is a beta version of the remote development functionality<\/strong> and we\u2019re still actively working to improve it. Please give the new functionality a try and let us know what you think. You can share your feedback or report any bugs here<\/a>.<\/p>\n For this release, we made a few significant improvements that support the workflow where Node.js is installed in Docker and then used by WebStorm\u2019s integrations with JavaScript tooling. Your IDE will now let you use the Node.js remote interpreter with ESLint, Mocha, Jest, npm, pnpm, and yarn.<\/p>\n Node.js remote interpreter support for ESLint has been available since v2021.2 as an experimental feature. From here on out, it will be active by default.<\/p>\n To try out the new feature, start by adding a remote Node.js interpreter. This can be done by going to Preferences \/ Settings | Languages & Frameworks | Node.js<\/em>, opening the drop-down list under the Node interpreter<\/em> field and clicking Add<\/em>. Then select Add Remote\u2026<\/em> and specify one of the existing Docker images in the dialog that appears.<\/p>\n Then go back to your Preferences \/ Settings<\/em> and make sure the Package manager<\/em> field has the correct path to the installation folder of a package manager in your Docker image.<\/p>\n Then you can go back to the editor and install the dependencies in your project using Node.js and your package manager inside Docker. At this point, you should be able to start working as you normally would when using Node.js locally. For example, if you want to lint a JavaScript file with ESLint, open that file in the editor. The errors should be highlighted automatically.<\/p>\n We\u2019ve also extended Node.js remote interpreter support to Mocha, Jest, npm, pnpm, and yarn scripts. You can find instructions for each of the supported technologies below:<\/p>\n You can now specify an HTTP or SOCKS proxy server for your SSH configuration<\/a> in Preferences \/ Settings | Tools | SSH Configurations<\/em>.<\/p>\n Under the new HTTP\/SOCKS Proxy<\/em> section, you can select the proxy type, enter a hostname and a port, and, if necessary, apply authentication with a login and password.<\/p>\n It is also possible to sync your SSH proxy settings with the global IDE ones. To do so, select the Use global IDE proxy settings<\/em> checkbox.<\/p>\n Connecting to Docker has become faster! You can simply double-click on the node you need or use the new shortcut: \u2318\u23ce<\/em> on macOS or Ctrl+Enter<\/em> on Windows and Linux. The Start container<\/em> action can also be invoked with this shortcut.<\/p>\n The new Clean up<\/em> action works just like the prune<\/em><\/a> terminal command. When you right-click on the Networks<\/em>, Volumes<\/em>, Containers<\/em>, or Images<\/em> node, you can select Clean up<\/em>, and the IDE will delete the unused objects. You can also apply this action to the Docker root node to prune all the unnecessary objects in one click.<\/p>\n It is now easy to connect to a Docker daemon from Minikube. Go to Preferences \/ Settings | Build, Execution, Deployment<\/em> and select the Minikube<\/em> radio button. In the field next to it, the IDE will automatically display the detected Minikube’s docker-daemon environments that you can connect to.<\/p>\n WebStorm supports Compose V2<\/a>, which allows you to run Docker Compose commands as docker compose<\/em>, instead of docker-compose<\/em> (with a dash).<\/p>\n To activate this option, go to Preferences \/ Settings | Build, Execution, Deployment | Docker | Tools<\/em> and tick the Use Compose V2<\/em> checkbox.<\/p>\n Image layers allow you to track all of the commands that are applied to images<\/a>. To access them, select an image and go to the Layers<\/em> tab. From there, when you choose a command, you can click on the Analyze image for more information<\/em> link on the right-hand side of the screen for more detailed information about the changes applied to each layer.<\/p>\n If you have a preconfigured container that you want to use later, you can save it as an image. Go to the Services<\/em> tool window, right-click on the container, and select Image | Save as a new Image<\/em>.<\/p>\n WebStorm now supports Podman<\/a> as an alternative way to manage pods, containers, and images. Before using Podman in the IDE, please configure a connection<\/a> first.<\/p>\n Once Podman has been installed and configured on your OS, you can connect to it via Preferences \/ Settings | Build, Execution, Deployment | Docker<\/em> by selecting the TCP socket<\/em> radio button and filling out the required fields.<\/p>\n Have several configurations running and want to see their results simultaneously? You can now split your Run<\/em> tool window! To do this, drag the desired tab to the highlighted area and drop it there. To unsplit the tool window, you can drag the tab back or right-click the top pane and select Unsplit<\/em> from the context menu.<\/p>\n In WebStorm, we had two very similar instances \u2013 Favorites<\/em> and Bookmarks<\/em>. The difference could sometimes be confusing, so we decided to stick to just one \u2013 Bookmarks<\/em>. We\u2019ve reworked the workflow for this functionality and made a new tool window for it.<\/p>\n From now on, any files, folders, and classes you mark as important with the F3<\/em> shortcut on macOS or F11<\/em> on Windows \/ Linux will be located under the new Bookmarks<\/em> tool window.<\/p>\n When you add a bookmark, WebStorm puts it in the node named after your project. The IDE automatically creates this node beforehand and stores all your prioritized items there by default. Any new bookmarks will appear at the top of the list inside this node. However, you can organize them manually by dragging them to new lists, which you can name as you like.<\/p>\n The Show Usages<\/em><\/a> feature has received a small yet handy improvement in this release. When you view the usages of a symbol with \u2325\u2318F7 \/ Ctrl+Alt+F7, <\/em>or by pressing \u2318 \/ Ctrl<\/em> and clicking on the definition, you can now turn on the source code preview for a found usage by clicking the square icon.<\/p>\n When searching for actions, Search Everywhere<\/em><\/a> in WebStorm is now powered by machine learning by default. We\u2019ve trained an ML-based formula that takes into account:<\/p>\n We hope you find that the ML-based models boost your search quality and return results tailored to your specific needs.<\/p>\n WebStorm\u2019s terminal now supports the new ConPTY API<\/a> on Windows. Using this as a backend for the terminal helps address several problems that users were having with the old implementation, which was based on winpty<\/a>. Also, 24-bit colors are now supported.<\/p>\n Additionally, the newly added typeahead support predicts text modifications and displays them in light grey right away. This feature allows you to type in the terminal equally fast, whether you work on a local or a remote machine.<\/p>\n In this release, we\u2019ve improved the discoverability of the Evaluate Expression<\/em> feature. Previously, many users resorted to using watches instead of the Evaluate<\/em> dialog.<\/p>\n Now, the Evaluate Expression <\/em>field is accessible right in the Debug<\/em> tool window, making the most convenient way to evaluate expressions more obvious.<\/p>\n WebStorm 2021.3 brings a new, faster way to diagnose and fix issues that prevent your IDE from working properly. If you have problems with WebStorm, invoke the new Repair IDE…<\/em> action from the File<\/em> menu. It will guide you through a sequence of steps to troubleshoot some of the most common problems.<\/p>\n We’ve addressed some accessibility issues to make it more comfortable to work in the screen reader mode. We\u2019ve disabled the tool window widget pop-up and the quick documentation pop-up that used to appear on a mouse hover.<\/p>\n We\u2019ve also fixed an issue with calling the Go to Declaration or Usages<\/em> pop-up.<\/p>\n The accessibility support on macOS has also been improved. We\u2019ve resolved several issues with voiceover focus and made it possible to create projects using a screen reader. To minimize distractions while you’re coding, we’ve decreased the number of help tooltips that play sounds.<\/p>\n Did you know you can change the editor font size using the mouse wheel? Previously, this feature worked only for the current file. Now you can make it work for all opened files. Go to Preferences \/ Settings | Editor | General<\/em>, tick Change font size with Command \/ Ctrl + Mouse Wheel in<\/em>, and then choose All editors <\/em>option.<\/p>\n To help you configure your version control systems faster, we\u2019ve made VCS settings more discoverable and more clearly structured. Here are some of the changes you\u2019ll find in Preferences \/ Settings | Version Control<\/em>.<\/p>\n The Version Control<\/em> node now lists all the available settings. You can navigate to the settings by clicking on them.<\/p>\n We improved the layout inside the Git<\/em> node. We divided all the settings into sections that account for the most important processes: Commit<\/em>, Push<\/em>, and Update<\/em>. Additionally, the parameters inside these sections are now organized more logically.<\/p>\n We\u2019ve also added a separate node for Directory mappings<\/em>, and the background operations are now switched on by default. The Background<\/em> node no longer exists.<\/p>\n Sometimes, you may have several commits that are ready to be shipped while others are still works in progress. In such cases, you may want to push only the ones you are sure about. With this release, WebStorm will let you push commits up to the one you have selected in the Log<\/em> tab of the Git<\/em> tool window. To do so, pick the necessary commit, right-click on it to open the context menu, and select a new Push All up to Here <\/em>action.<\/p>\n The Checkout and Rebase onto Current<\/em> action allows you to check out the selected branch and rebase it on top of a branch that is currently checked out. Previously, this action was available for local branches only. Starting from v2021.3, you can apply this action to remote branches, too.<\/p>\n Previously, WebStorm would show you the difference between commits in a separate dialog. Starting from this release, the IDE will display this information in a new Changes<\/em> tool window. To open the new tool window, in the Log<\/em> tab of your version control system right-click on a revision and pick Compare with Local<\/em> from the context menu.<\/p>\n We\u2019ve added the new Align Changes Highlighting<\/em> option to the Diff<\/em> screen settings that can be found under the gear icon. This feature makes the Diff easier to read, especially when there are complex modifications, because it aligns the unchanged lines so that they are displayed next to each other. This helps you see the code that has been added or removed more clearly.<\/p>\n Those are the most notable highlights! For the full list of new features and enhancements available in WebStorm 2021.3<\/a>, see the release notes<\/a>. Please share your feedback with us and report any issues you encounter to our issue tracker<\/a>.<\/p>\n The WebStorm team<\/em><\/p>\n","protected":false},"author":1219,"featured_media":204073,"comment_status":"closed","ping_status":"closed","template":"","categories":[907],"tags":[91,6734],"cross-post-tag":[],"acf":[],"_links":{"self":[{"href":"https:\/\/blog.jetbrains.com\/ja\/wp-json\/wp\/v2\/webstorm\/200183"}],"collection":[{"href":"https:\/\/blog.jetbrains.com\/ja\/wp-json\/wp\/v2\/webstorm"}],"about":[{"href":"https:\/\/blog.jetbrains.com\/ja\/wp-json\/wp\/v2\/types\/webstorm"}],"author":[{"embeddable":true,"href":"https:\/\/blog.jetbrains.com\/ja\/wp-json\/wp\/v2\/users\/1219"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.jetbrains.com\/ja\/wp-json\/wp\/v2\/comments?post=200183"}],"version-history":[{"count":9,"href":"https:\/\/blog.jetbrains.com\/ja\/wp-json\/wp\/v2\/webstorm\/200183\/revisions"}],"predecessor-version":[{"id":211556,"href":"https:\/\/blog.jetbrains.com\/ja\/wp-json\/wp\/v2\/webstorm\/200183\/revisions\/211556"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.jetbrains.com\/ja\/wp-json\/wp\/v2\/media\/204073"}],"wp:attachment":[{"href":"https:\/\/blog.jetbrains.com\/ja\/wp-json\/wp\/v2\/media?parent=200183"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.jetbrains.com\/ja\/wp-json\/wp\/v2\/categories?post=200183"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.jetbrains.com\/ja\/wp-json\/wp\/v2\/tags?post=200183"},{"taxonomy":"cross-post-tag","embeddable":true,"href":"https:\/\/blog.jetbrains.com\/ja\/wp-json\/wp\/v2\/cross-post-tag?post=200183"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\n
JavaScript & TypeScript<\/h2>\n
Improved support for monorepos<\/h3>\n
Faster indexing of JavaScript files<\/h3>\n
Support for URLs in import statements<\/h3>\n
![\"support-for-urls-in-import-statements\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2021\/10\/support-for-urls-in-import-statements.png\")
<\/p>\nRefactoring support for ES2022 private class members<\/h3>\n
![\"rename-refactoring-private-class-members\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2021\/10\/rename-refactoring-private-class-members.png\")
<\/p>\nNew intentions for organizing code<\/h3>\n
![\"intention-for-putting-elements-on-separate-lines-and-back-webstorm\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2021\/10\/intention-for-putting-elements-on-separate-lines-and-back-webstorm.png\")
<\/p>\n![\"replace-with-jsdoc-comment\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2021\/11\/replace-with-jsdoc-comment.png\")
<\/p>\nBetter mapping between .js and .d.ts files<\/h3>\n
![\"mapping-between-js-and-dts-files\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2021\/10\/mapping-between-js-and-dts-files.png\")
<\/p>\nFrameworks & Technologies<\/h2>\n
New inspection for updating dependencies<\/h3>\n
![\"update-package-in-package-json-quick-fix\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2021\/10\/update-package-in-package-json-quick-fix.png\")
<\/p>\n![\"update-inspection-severity-level-package-json\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2021\/10\/update-inspection-severity-level-package-json.png\")
<\/p>\n![\"node-js-section-in-preferences\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2021\/10\/node-js-section-in-preferences.png\")
<\/p>\nReworked Deno integration<\/h3>\n
Angular 13 support<\/h3>\n
Improved HTML completion<\/h3>\n
![\"html-tag-completion-webstorm\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2021\/10\/html-tag-completion-webstorm.png\")
<\/p>\nType checking for Vue and React properties<\/h3>\n
![\"vue-typescript-type-checking\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2021\/11\/vue-typescript-type-checking.png\")
<\/p>\nNew features for HTTP client<\/h3>\n
![\"image-response-http\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2021\/11\/image-in-response-webstorm.png\")
<\/p>\nRemote Development<\/h2>\n
Running WebStorm remotely<\/h3>\n
![\"jetbrains-gateway\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2021\/11\/jetbrains-gateway-webstorm-blog.png\")
<\/p>\nDevelopment with remote Node.js<\/h3>\n
![\"node-remote-interpreter-settings\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2021\/11\/node-remote-interpreter-settings.png\")
<\/p>\n\n
Proxy support for SSH connections<\/h3>\n
![\"http-socks-proxy-settings-webstorm\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2021\/10\/http-socks-proxy-settings-webstorm.png\")
<\/p>\nDocker<\/h2>\n
Easier connection process<\/h3>\n
![\"docker-connection\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2021\/11\/docker-connection.png\")
<\/p>\nNew Clean up<\/em> action<\/h3>\n
![\"docker-clean-up\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2021\/11\/docker-clean-up.png\")
<\/p>\nConnection to Docker from Minikube<\/h3>\n
![\"docker-minicube\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2021\/11\/docker-minicube.png\")
<\/p>\nSupport for Compose V2<\/h3>\n
![\"compose-v2\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2021\/11\/compose-v2.png\")
<\/p>\nImage layers<\/h3>\n
![\"image-layers\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2021\/11\/image-layers.png\")
<\/p>\nSave container as image<\/h3>\n
![\"container-image\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2021\/11\/container-image.png\")
<\/p>\nPodman support<\/h3>\n
User Experience<\/h2>\n
Ability to split the Run<\/em> tool window<\/h3>\n
![\"split-run-tool-window\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2021\/10\/split-run-tool-window.png\")
<\/p>\nNew Bookmarks<\/em> tool window<\/h3>\n
![\"bookmarks-tool-window-webstorm\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2021\/09\/bookmarks-tool-window-webstorm.png\")
<\/p>\nSource preview for Show Usages<\/em><\/h3>\n
![\"preview-in-show-usages-webstorm\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2021\/10\/preview-in-show-usages-webstorm.png\")
<\/p>\nML-based search for actions in Search Everywhere<\/em><\/h3>\n
\n
![\"ml-actions-2021.3\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2021\/11\/ml-actions-2021.3.png\")
<\/p>\n![\"ml-actions-2021.2\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2021\/11\/ml-actions-2021.2.png\")
<\/p>\nImprovements to the terminal<\/h3>\n
![\"conpty-support\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2021\/10\/conpty-support.png\")
<\/p>\nEvaluate expressions from the debugger<\/h3>\n
![\"evaluate-expression-in-webstorm-2021-3\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2021\/10\/evaluate-expression-in-webstorm-2021-3.png\")
<\/p>\nBuilt-in troubleshooting tool<\/h3>\n
![\"repair_ide\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2021\/11\/repair_ide.png\")
<\/p>\nAccessibility updates<\/h3>\n
Ability to change font size for all tabs<\/h3>\n
![\"change-font-size\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2021\/11\/change-font-size.png\")
<\/p>\nVersion Control<\/h2>\n
Reorganized VCS settings<\/h3>\n
![\"webstorm-vcs-settings-2021-3\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2021\/09\/webstorm-vcs-settings-2021-3.png\")
<\/p>\n![\"git-node-in-webstorm-2021-3\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2021\/09\/git-node-in-webstorm-2021-3.png\")
<\/p>\nNew Push All up to Here<\/em> action<\/h3>\n
![\"push-all-up-to-here-in-webstorm\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2021\/10\/push-all-up-to-here-in-webstorm.png\")
<\/p>\nCheckout and Rebase onto Current<\/em> for remote branches<\/h3>\n
![\"checkout-and-rebase-onto-current-for-remote-branches-webstorm\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2021\/09\/checkout-and-rebase-onto-current-for-remote-branches-webstorm.png\")
<\/p>\nNew Changes<\/em> tool window<\/h3>\n
![\"changes-tool-window\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2021\/11\/changes-window-compare.png\")
<\/p>\nAlign Changes Highlighting<\/h3>\n
![\"align-changes-highlighting\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2021\/11\/align-changes-highlighting.png\")
<\/p>\n