{"id":89669,"date":"2020-10-29T15:50:10","date_gmt":"2020-10-29T15:50:10","guid":{"rendered":"https:\/\/blog.jetbrains.com\/?post_type=webstorm&#038;p=89669"},"modified":"2020-11-09T18:07:34","modified_gmt":"2020-11-09T17:07:34","slug":"webstorm-2020-3-eap-6","status":"publish","type":"webstorm","link":"https:\/\/blog.jetbrains.com\/zh-hans\/webstorm\/2020\/10\/webstorm-2020-3-eap-6","title":{"rendered":"WebStorm 2020.3 EAP #6: Support for Code With Me, Git Staging Area, and More"},"content":{"rendered":"<p>WebStorm 2020.3 EAP build #6 is now available with a lot of enhancements! Please try them out and <a href=\"https:\/\/youtrack.jetbrains.com\/issues\/WEB\" target=\"_blank\" rel=\"noopener\">share your feedback<\/a> with us so we can make the v2020.3 release better for you.<!--more--><\/p>\n<\/p>\n<p>If you\u2019re unfamiliar with our Early Access Program, check out <a href=\"https:\/\/blog.jetbrains.com\/zh-hans\/webstorm\/2020\/09\/webstorm-eap\">this<\/a> blog post where we explain what the EAP is about and some of the reasons you may want to take part in it (spoiler: you could get a free WebStorm license). To catch up on all the new features, check out our <a href=\"https:\/\/blog.jetbrains.com\/webstorm\/tag\/webstorm-2020-3\/\">previous EAP blog posts<\/a>.<\/p>\n<p>The <a href=\"https:\/\/www.jetbrains.com\/toolbox\/app\/\" target=\"_blank\" rel=\"noopener\">Toolbox App<\/a> is the easiest way to get the EAP builds and keep both your stable and EAP versions up to date. Or you can manually download the EAP builds from our <a href=\"https:\/\/www.jetbrains.com\/webstorm\/nextversion\/\" target=\"_blank\" rel=\"noopener\">website<\/a>.<\/p>\n<p align=\"center\"><a class=\"jb-download-button\" href=\"https:\/\/www.jetbrains.com\/webstorm\/nextversion\" target=\"_blank\" rel=\"noopener\">DOWNLOAD WEBSTORM 2020.3 EAP<\/a><\/p>\n<p><strong>Important! WebStorm EAP builds are not fully tested and might be unstable.<\/strong><\/p>\n<p>Here are some of the highlights of WebStorm 2020.3 EAP #6. For the full list of issues fixed in this update, see the <a href=\"https:\/\/confluence.jetbrains.com\/display\/WI\/WebStorm+203.5419.24+Release+Notes\" target=\"_blank\" rel=\"noopener\">release notes<\/a>.<\/p>\n<ul>\n<li><a href=\"https:\/\/blog.jetbrains.com\/zh-hans\/webstorm\/2020\/10\/webstorm-2020-3-eap-6#support_for_remote_collaborative_development_and_pair_programming\">Support for remote collaborative development and pair programming<\/a><\/li>\n<li><a href=\"https:\/\/blog.jetbrains.com\/zh-hans\/webstorm\/2020\/10\/webstorm-2020-3-eap-6#basic_support_for_multiple_webpack_configs\">Basic support for multiple webpack configs<\/a><\/li>\n<li><a href=\"https:\/\/blog.jetbrains.com\/zh-hans\/webstorm\/2020\/10\/webstorm-2020-3-eap-6#support_for_git_staging_area\">Support for Git staging area<\/a><\/li>\n<li><a href=\"https:\/\/blog.jetbrains.com\/zh-hans\/webstorm\/2020\/10\/webstorm-2020-3-eap-6#improved_work_with_branches\">Improved work with branches<\/a><\/li>\n<\/ul>\n<h2 id=\"support_for_remote_collaborative_development_and_pair_programming\">Support for remote collaborative development and pair programming<\/h2>\n<p>WebStorm 2020.3 now supports Code With Me, our <a href=\"https:\/\/blog.jetbrains.com\/zh-hans\/blog\/2020\/09\/28\/code-with-me-eap\">new tool<\/a> for remote collaborative development and pair programming. The update to this tool lets you configure permissions and includes some important fixes. Read <a href=\"https:\/\/blog.jetbrains.com\/zh-hans\/blog\/2020\/10\/23\/code-with-me-jetbrains-ides-v2020-3\">this blog post<\/a> to learn more about the latest changes to Code With Me.<\/p>\n<h2 id=\"basic_support_for_multiple_webpack_configs\">Basic support for multiple webpack configs<\/h2>\n<p>In v2020.3, we\u2019ve taken our first steps towards implementing support for multiple webpack configs. Now, WebStorm will let you choose between detecting webpack configuration files manually or automatically. The new options can be found in <em>Preferences\/Settings | Languages &amp; Frameworks | JavaScript | Webpack<\/em>.<\/p>\n<p><img decoding=\"async\" alt=\"basic-support-for-multiple-webpack-configs\" width=\"600\" src=\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2020\/10\/basic-support-for-multiple-webpack-configs.png\"\/><\/p>\n<p>The manual setup works the same as it did before and uses the file you specified in the settings. If you choose the automatic setup, WebStorm will use module resolution rules from the webpack configuration file located in the same folder as the current file or any of its parent folders.<\/p>\n<h2 id=\"support_for_git_staging_area\">Support for Git staging area<\/h2>\n<p><strong>Note:<\/strong> This functionality is only available for the <a href=\"https:\/\/www.jetbrains.com\/help\/webstorm\/commit-and-push-changes.html#commit\" target=\"_blank\" rel=\"noopener\"><em>Commit<\/em> tool window<\/a>.<\/p>\n<p>With this update, we\u2019ve introduced support for the Git staging area. To turn it on, tick the <em>Enable staging area<\/em> checkbox in <em>Preferences\/Settings | Version Control | Git<\/em>. Once you do, the support for changelists will be disabled.<\/p>\n<p>If you go back to the commit UI, you\u2019ll see that it contains staged and unstaged files. When you\u2019re ready to stage a file, simply click the <em>+ <\/em>icon next to it. The file will appear under the <em>Staged<\/em> node.<\/p>\n<p><img decoding=\"async\" alt=\"stage-unstage-file\" width=\"600\" data-gif-src=\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2020\/10\/stage-unstage-file.gif\" src=\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2020\/10\/stage-unstage-file.png\"\/><\/p>\n<p>You can also stage changes right from the gutter.<\/p>\n<p><img decoding=\"async\" alt=\"stage-changes-from-gutter\" width=\"600\" src=\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2020\/10\/stage-changes-from-gutter.png\"\/><\/p>\n<p><em>Show Diff<\/em> is another way to add your changes to the staging area.<\/p>\n<p><img decoding=\"async\" alt=\"stage-file-from-show-diff\" width=\"600\" data-gif-src=\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2020\/10\/stage-file-from-show-diff.gif\" src=\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2020\/10\/stage-file-from-show-diff.png\"\/><\/p>\n<p>When you click <em>Commit<\/em>, all staged files will be committed.<\/p>\n<h2 id=\"improved_work_with_branches\">Improved work with branches<\/h2>\n<p>Several enhancements in this EAP touch upon branches. First, the IDE now automatically corrects unaccepted symbols in the names of new branches, helping you create branches in line with the accepted format.<\/p>\n<p><img decoding=\"async\" alt=\"branch-wrong-symbols-used-ws\" width=\"600\" data-gif-src=\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2020\/10\/branch-wrong-symbols-used-ws.gif\" src=\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2020\/10\/branch-wrong-symbols-used-ws.png\"\/><\/p>\n<p>Second, the IDE will now show you all the actions available for the currently selected branch, just like it would for other branches.<\/p>\n<p><img decoding=\"async\" alt=\"new-actions-for-current-branch-ws\" width=\"600\" src=\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2020\/10\/new-actions-for-current-branch-ws.png\"\/><\/p>\n<p>Finally, for remote branches, we\u2019ve renamed the <em>Merge into Current <\/em>and <em>Rebase Current onto Selected<\/em> actions to <em>Pull into Current Using Merge<\/em> and <em>Pull into Current Using Rebase<\/em>, respectively.<\/p>\n<p>That\u2019s it for the biggest highlights. This build also comes with some smaller, but still important changes such as:<\/p>\n<ul>\n<li>\nIn the past, the <a href=\"https:\/\/www.jetbrains.com\/help\/webstorm\/using-patches.html\" target=\"_blank\" rel=\"noopener\">patch<\/a> format varied depending on the version control that was used. We\u2019ve got feedback that this was inconvenient and slowed work down. In light of these concerns, we\u2019ve changed the default format for patches. They are now created in the Git format.\n<\/li>\n<li>\nWebStorm now comes bundled with TypeScript 4.0.\n<\/li>\n<li>\nWe\u2019ve fixed several issues with the links in the output of tools not being clickable (<a href=\"https:\/\/youtrack.jetbrains.com\/issue\/WEB-22867\" target=\"_blank\" rel=\"noopener\">WEB-22867<\/a>, <a href=\"https:\/\/youtrack.jetbrains.com\/issue\/WEB-37265\" target=\"_blank\" rel=\"noopener\">WEB-37265<\/a>, <a href=\"https:\/\/youtrack.jetbrains.com\/issue\/WEB-47897\" target=\"_blank\" rel=\"noopener\">WEB-47897<\/a>, <a href=\"https:\/\/youtrack.jetbrains.com\/issue\/WEB-44742\" target=\"_blank\" rel=\"noopener\">WEB-44742<\/a>, and <a href=\"https:\/\/youtrack.jetbrains.com\/issue\/WEB-46790\" target=\"_blank\" rel=\"noopener\">WEB-46790<\/a>).\n<\/li>\n<li>\nWe\u2019ve removed the <em>React JSX<\/em> option from <em>Preferences\/Settings | Languages and Frameworks | JavaScript<\/em>. If you&#8217;re using the JSX syntax in your JavaScript code, the language version will be set to <em>ECMAScript 6+<\/em>. If you want to be warned when the JSX syntax is used by mistake, you can turn the <em>React JSX syntax<\/em> inspection on in <em>Preferences\/Settings | Editor | Inspections<\/em>.\n<\/li>\n<\/ul>\n<p>Please report any issues you encounter to our <a href=\"https:\/\/youtrack.jetbrains.com\/issues\/WEB\" target=\"_blank\" rel=\"noopener\">issue tracker<\/a>, and stay tuned for next week\u2019s update!<\/p>\n<p><em>The WebStorm team<\/em><\/p>\n","protected":false},"author":989,"featured_media":89730,"comment_status":"closed","ping_status":"closed","template":"","categories":[826],"tags":[285,91,2805,6260],"cross-post-tag":[],"acf":[],"_links":{"self":[{"href":"https:\/\/blog.jetbrains.com\/zh-hans\/wp-json\/wp\/v2\/webstorm\/89669"}],"collection":[{"href":"https:\/\/blog.jetbrains.com\/zh-hans\/wp-json\/wp\/v2\/webstorm"}],"about":[{"href":"https:\/\/blog.jetbrains.com\/zh-hans\/wp-json\/wp\/v2\/types\/webstorm"}],"author":[{"embeddable":true,"href":"https:\/\/blog.jetbrains.com\/zh-hans\/wp-json\/wp\/v2\/users\/989"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.jetbrains.com\/zh-hans\/wp-json\/wp\/v2\/comments?post=89669"}],"version-history":[{"count":3,"href":"https:\/\/blog.jetbrains.com\/zh-hans\/wp-json\/wp\/v2\/webstorm\/89669\/revisions"}],"predecessor-version":[{"id":94010,"href":"https:\/\/blog.jetbrains.com\/zh-hans\/wp-json\/wp\/v2\/webstorm\/89669\/revisions\/94010"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.jetbrains.com\/zh-hans\/wp-json\/wp\/v2\/media\/89730"}],"wp:attachment":[{"href":"https:\/\/blog.jetbrains.com\/zh-hans\/wp-json\/wp\/v2\/media?parent=89669"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.jetbrains.com\/zh-hans\/wp-json\/wp\/v2\/categories?post=89669"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.jetbrains.com\/zh-hans\/wp-json\/wp\/v2\/tags?post=89669"},{"taxonomy":"cross-post-tag","embeddable":true,"href":"https:\/\/blog.jetbrains.com\/zh-hans\/wp-json\/wp\/v2\/cross-post-tag?post=89669"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}