Callnote

What's new in this version:

WebStorm 2021.3
The new features and improvements fall into these categories:
- JavaScript & TypeScript: improvements for working with monorepos, faster indexing times for JavaScript files, a quick-fix for downloading remote ES6 modules, support for ES2022 private class members, and more.
- Frameworks & Technologies: easier management of project dependencies, reworked Deno plugin, support for Angular 13, better HTML completion, and more
- Remote Development: JetBrains Gateway for remote development, Node.js remote interpreter updates, and proxy support for SSH connections
- Docker: improved connection process, a new Clean up action, Minikube integration, support for Compose V2, and more
- User Experience: the ability to split the Run tool window, a new Bookmarks tool window, ML-based search for actions in Search Everywhere, and more
- Version Control: reorganized VCS settings, improved workflow for pushing commits, a new Changes tool window, and more


WebStorm 2021.2.3
- Solved several problems with CSS highlighting and color preview
- Fixed the issue causing run configurations not to work with npm 7
- The TypeScript engine should no longer randomly stop working in Vue projects


WebStorm 2021.2.2
Fixed:
- the bug with the Stop button not terminating running processes on the first attempt
- a number of issues with Tailwind CSS

Added:
- support for inline SCSS in Angular 12
- support for ESLint 8.0

- Code completion now works for style sheet properties and values in React Native apps
- Enable external diff tool should now work as expected


WebStorm 2021.2.1
Improvements for Vue:
- WebStorm 2021.2.1 includes several long-awaited improvements for Vue support. The IDE now supports the final version of script setup RFC.
- Last year, we added support for an experimental version of script setup, where the export keyword was required. Since then, the RFC has changed. With the stable release of script setup in Vue 3.2, we reworked the existing support for this feature so you can use it in your project without any issues.

Other improvements for Vue in this release include:
- Vue 3 style selectors like :deep and :slotted are now supported
- Code completion won’t break when the parent element is an unknown tag
- Solved several problems with Composition API
- Fixed the issue with the wrong inferred prop type when a prop has the required attribute
- The TypeScript service should no longer stop working in your Vue projects
- Fixed various regressions in Pug support

Here are some other notable fixes:
- Added the ability to choose if you want to insert braces on code completion
- Solved the problem causing the IDE to freeze when opening a project from WSL 2
- Added support for shorthand properties in Angular templates
- Reworked support for Tailwind CSS to make it possible to use JIT mode
- Ctrl+arrow keys used in the built-in terminal should now work as expected


WebStorm 2021.2
Code Editing:
Reload pages in the browser on save:
- WebStorm lets you preview HTML files in a browser using the built-in web server, and now it will automatically update the pages in a browser as you edit and save your HTML, CSS, and JavaScript files.
- To get started, open an HTML file in the editor, hover over it, and click on the icon for the browser you want to use – all browsers are supported. You can also preview the file in a browser by going to View | Open in Browser in the main menu.
- The new feature may sound similar to the Live Edit feature that WebStorm has had for some time already. You can and may still need to use Live Edit if you want to see changes when you can’t open the page on the built-in IDE server. With the new feature, we wanted to provide a more straightforward experience and make the reloading process more predictable and available in all browsers.

Built-in HTML preview update:
- The built-in HTML preview that was introduced in 2021.1 now has a new workflow. Instead of automatically saving the file and reloading the page on typing, it will now only update the page on save, just like the preview in the browser. We will add the option to choose between these behaviors in the next release cycle.

Actions on save:
- Would you like to perform certain operations on the explicit save action? From now on, WebStorm will properly support this workflow. There have already been quite a few things that you could set up to work on saving files. For example, WebStorm would let you run Prettier on save. With this release, we’ve reworked all the existing functionality and collected it in one place, topping it off with the ability to reformat code and optimize imports on save.
- To customize WebStorm’s behavior on save, go to Preferences / Settings | Tools | Actions on Save. There you’ll find a list of actions that can be triggered with ⌘S / Ctrl+S.
- To turn an action on, tick the checkbox next to its name. Most of the actions will be triggered on any save, which includes autosave and explicit save actions. For file watchers and the Upload to default server action, you can choose between two options whenever you want them to be activated.
- If you want to adjust settings for a specific action, hover over that action – you’ll see a link to the configuration options available for it. Click on it to jump to the related page in the IDE settings.

Improvements for scratch files:
- With scratch files, you can make notes or draft code outside of the project context. To make them easier to work with, we’ve included two improvements in this release.
- First, you can now select some code, press ⌥⏎ / Alt+Enter, and then choose Create new scratch file from selection to quickly create a new scratch containing the same code.
- In addition to that, WebStorm will automatically remove empty scratch files as soon as you close them to help keep your workspace clean.

Improvements for Code With Me:
- When you’re in Following mode during a Code With Me session, you can now keep track of what code completion suggestions the person you’re following uses
- Additionally, Code With Me recently launched two new relay servers: one on the west coast of the US and another one in South Africa. This has made the ping almost three times faster.

JavaScript and TypeScript:
Auto-import for require():
- The next improvement in this release is for Node.js developers. As you may know, WebStorm adds missing import statements as you complete symbols in ES6 modules. It will now do the same in the CommonJS modules – require statements will be inserted on code completion.
- Whenever the IDE isn’t sure which syntax should be used in a file, it will show you a popup allowing you to choose between ES6 and CommonJS syntax.

Support for TypeScript types in JSDoc comments:
- One of the most anticipated improvements in v2021.2 – WebStorm now properly supports the TypeScript syntax used within JSDoc comments in your .js files. With this release, we’ve reworked and expanded the existing support, making WebStorm recognize more syntactic constructs. We’ve also fixed a lot of known issues. For example, optional properties in @typedef declarations are now supported.

New action for adding arrow functions:
- We added a new live template to help you add arrow functions more quickly. You can use it to surround a block of code with an arrow function using ⌥⌘J / Ctrl+Alt+J. You can also type arf and press ⇥ / Tab to expand the template and add an empty arrow function, as shown below.

Previewing files when debugging:
- The preview tab that used to work only for files in the Project tool window now works for files that open during debugging. This can help you avoid polluting the editor with multiple files that open in separate tabs when you stop at a breakpoint or step through the code.
- If you enable the preview, these files will all appear successively in one tab. You can turn this feature on in Preferences / Settings | Editor | General | Editor Tabs.

Frameworks and Technologies:
Code completion for private npm packages:
- Adding new project dependencies to package.json has become even easier, as code completion now works for private npm packages. The IDE will let you browse information about the latest versions of the package, just like it does for public packages.

Rename refactoring for React useState hooks:
- You will no longer need to spend a lot of time on refactoring useState values and functions one by one in React hooks – WebStorm can now rename both for you! To try this out, place the caret on a state value and invoke the Rename refactoring with ⇧F6 / Shift+F6 or by going to Refactor | Rename from the right-click context menu.

Support for classnames and clsx libraries:
- We’ve got another useful improvement for React users in this release. WebStorm now supports popular classnames and clsx libraries, helping you deal with your CSS class names more efficiently. The IDE will show completion suggestions for your CSS classes and resolve all symbols in string literals and properties with literal names.
- The IDE will show completion suggestions for strings as you type. To see completion suggestions for objects used within your classNames functions, press Ctrl+Space.

Better completion for endpoint URLs:
- If you’re working with Express.js, you can now get an overview of route handlers in the Endpoints tool window. This tool window isn’t available in WebStorm by default, but you can add it by installing the corresponding plugin from Preferences / Settings | Plugins. The tool window can also come in handy if you need to work with APIs.
- Also, it’s now possible to search for Express route declarations. For this, go to Navigate | URL Mapping…. from the main menu.

There are two more nice improvements for your client-side code:
- If you work with AngularJS, you can use completion for the endpoint URLs detected in the project’s $http methods
- For Axios, completion works for the endpoint URLs in the methods of a new Axios instance

Generic support for web-types:
- We’ve extended support for web-types, an open-source standard for documenting web frameworks. It was previously focused on Vue support, but now you can use it to enrich the coding assistance for custom components in your HTML files. Watch this webinar recording to learn more.

Other notable improvements:
- Starting from v2021.2, you will no longer find the Firefox Remote option under the available run/debug configurations. This run/debug configuration stopped working with the release of Firefox 65 in January 2019, so we decided to remove it from WebStorm to avoid any confusion (WEB-50869).
- Quick fixes suggested by WebStorm are now shown before the fixes like Suppress for current file suggested by linters. We’ve made this change because the actions suggested by the IDE may be more relevant in a lot of cases. We’ve also removed the Linter settings… and Edit linter config file quick fixes (WEB-47440).
- We’ve reviewed the list of browsers shown by default in the browser icon popup and removed less popular options. On macOS or Linux, you will no longer see Opera and Edge. The latter is still shown by default on Windows (WEB-50871).
- To avoid potential security issues, the values of variables stored in .env files will no longer be shown during code completion if those files are excluded or added to .gitignore (WEB-46834).

Version Control:
GPG signature support:
- You can now sign your commits with a GPG key to secure them. You can enable this feature via Preferences / Settings | Version Control | Git. If it’s your first time using a GPG key, you’ll need to configure it. To use an existing preconfigured GPG key, you can just select it from the drop-down list.

Enhancements for pre-commit checks:
- WebStorm allows you to perform a wide range of actions before a commit. With v2021.2, we’ve expanded the list of these actions with the ability to run tests. To try it out, click the gear icon in the Commit tool window, select the Run Tests option, and choose the necessary run configuration. The IDE will test your file and let you know if anything goes wrong.
- Additionally, you can now customize the Cleanup option by clicking Choose profile next to it, just like you could for Analyze code.
- Lastly, the progress and results of pre-commit checks are now shown in the Commit area, without disturbing you with additional modal dialogs.

Text search in Local History revisions:
- We’ve added a search field to the Local History dialog to help you quickly get to the necessary text in your revisions. Now, when you right-click on any changed file and select Local History | Show History in the context menu, you can navigate around your file history by typing the query in this field.

Unified behavior for the Show Diff action:
- Starting from v2021.2, WebStorm will display the difference between the initial and changed files in the editor. It doesn’t matter how you invoke the Show Diff action – via a shortcut, icon, from the context menu, from Log or File History, or by clicking on a file in the Commit tool window – the IDE will open the diff in the editor by default.
- If you find it more convenient to track changes in a separate window, you can drag the desired file from the editor. If you do, WebStorm will remember this and will open future diffs in a separate window. To go back to the default display, click the gear icon and select Show Diff in Editor Tab.

Usability:
Faster way to reorganize tool windows:
- It is now easier to reorganize tool windows. Hover over the top of the tool window you want to move, then drag it to where you want it and drop it there. This will work if you want to detach a tool window from the main WebStorm window, too – just drag it outside of the IDE frame.

Easier customization of project icons:
- Did you know you can change your project icons? You can do this in the projects list on the Welcome screen. Upload custom icons by right-clicking on any project and selecting Change Project Icon… from the context menu. We’ve reworked the dialogue window from which you can download your SVG icon to make this process more straightforward.

Automatic cache and logs cleanup:
- Now, after each major update, your IDE will automatically clean up any cache and log directories that were last updated more than 180 days ago. The system settings and plugins directories will stay intact. To trigger this process manually, go to Help | Delete Leftover IDE Directories… in the main menu.

Improvements for the Preferences / Settings dialog:
- There is now a node with advanced settings in your Preferences / Settings dialog. You can find some new configuration options there, including the ability to set a left margin in Distraction-free mode.
- Additionally, you can now navigate back and forth between open sections in your Preferences / Settings dialog. To do so, use the arrows in the right-hand corner of the window.

New features for the built-in terminal:
- We’ve added three new features to our built-in terminal. First, you can now select the cursor shape. Choose whichever you like best!
- Second, WebStorm now supports Use Option as Meta key, similar to the same-name option in the native Terminal on macOS. This allows the ⌥ key on the keyboard to act as a meta modifier that can be used in combination with other keys instead of just as an Escape key.
- We’ve made it more convenient to work with the http links shown in the terminal output. You can now copy those links or open them in the browser of your choice. For this, use the corresponding actions from the context menu available on right-click.
- Update notifications from the Toolbox App
- Now you won’t miss any critical product updates from the Toolbox App. WebStorm will inform you if a new version is available for download and offer you to upgrade to it. You’ll need to have Toolbox App 1.20.8804 or later for this.


WebStorm 2021.1.3
Fixed:
- the issue with the debugger not reconnecting automatically
- the regression bug causing the Stretch to Right / Stretch to Left actions not to work as expected
- the bug causing the Compare with branch dialog to close unexpectedly
- Solved the problem with images not being rendered in the Documentation popup


WebStorm 2021.1.2
- Updated the bundled webpack schema
- Fixed a number of issues with the Extract Angular component refactoring
- Added support for several TypeScript 4.3 features
- Chinese characters are now displayed correctly when the Quick Documentation action is used


WebStorm 2021.1.1
Extract Angular components:
- We’ve added a long-awaited feature for Angular users – the ability to extract components from your templates. To try it out, select the component you want to extract, open the context menu with a right-click, and go to Refactor | Extract Component. You can also invoke this action from the Refactor This popup or by assigning a custom shortcut to it under Preferences / Settings | Keymap – just look for the Extract Component action with an Angular icon there
- Solved the problem with corrupted indexes that caused Find in Files to show no results
- Fixed the selection issue in the Switcher and Recent Files popups
- The Open in Terminal action now correctly opens the project file directory
- New component options syntax in vue-class-component v8 are now supported
- You can now copy imports from a type declaration
- In CSS, :where() and :is() pseudo-classes are now supported
- Fixed the UI issues in the Commit view when the Chinese or Korean language packs are enabled


WebStorm 2021.1
This release was mainly focused on improving the quality of WebStorm, but we also made sure to deliver some new features. The list of features and improvements can be divided into these categories:
- JavaScript and TypeScript: ML-assisted code completion enabled by default, improved completion suggestions for symbol names, better JSDoc syntax highlighting, and the ability to turn off inspections on a file-by-file basis.
- Frameworks and Technologies: bundled service for remote collaborative development and pair programming, support for CSS modules in Vue, HTTP client improvements, configurable scope for ESLint, JSON Lines support, and JetBrains Space integration.
- HTML and CSS: several improvements for Stylelint, a built-in HTML preview, and the ability to check the selector specificity when working with CSS
- User Interface: adjustable editor font weight, the ability to maximize tabs when you split the editor, bundled MDN documentation, and more
- Version Control: improvements for working with pull requests, support for Git commit message templates, a new Save to Shelf action, and configurable profiles for pre-commit inspections.


WebStorm 2020.3.3
- Change log not available for this version


WebStorm 2020.3.2
- Change log not available for this version


WebStorm 2020.3.1
For Tailwind, we’ve added support for more use cases:
- Completion for Tailwind class names now works in the HTML code inside JavaScript template literals
- The IDE Tailwind support now works in projects that use Yarn PnP (WEB-48226) as well as in the projects located in the WSL file system
- We’ve improved support for components in the Nuxt projects
- Documentation popup in the JavaScript, HTML and CSS code now correctly shows docs from MDN
- Fixed performance issue with the rendered editor docs
- Paths in the ESLint report in the npm tool window are now clickable
- Comments from the GitHub PRs are no longer shown twice in files
- Fixed the problem with checking out a GitHub project using the JetBrains Toolbox browser extension


WebStorm 2020.3
- Change log not available for this version


WebStorm 2020.2.4
- Fixed a problem with opening projects in a new window on macOS Big Sur
- Fixed a number of regression bugs that affected Vue.js users


WebStorm 2020.2.3
- The Search Everywhere popup no longer opens partially offscreen
- Angular Schematics are now loaded correctly
- Fixed the performance issue with optics-ts in TypeScript projects


WebStorm 2020.2.2
- Fixed syntax errors showing in the ng-options attribute
- Automatic code reformatting with Prettier no longer breaks Live Template expanding
- Fixed index files not working with @use in Sass
- File watchers now work properly with Sass’s @use and @forward rules
- LightEdit mode is now used for selected file extensions only


WebStorm 2020.2.1
- Change log not available for this version


WebStorm 2020.2
The new features and improvements fall into these categories:
- Frameworks and Technologies: an option to use Prettier as the default formatter, various improvements for Vue.js, and support for Git installed in WSL 2
- JavaScript and TypeScript: new smart intentions, rendered JSDoc comments, ML-assisted code completion, and debugger enhancements
- HTML and Style Sheets: better support for Sass’s module system, WebP support, and code completion for CSS selectors in querySelector methods
- Version Control: more advanced support for GitHub pull requests, redesigned dialogs for several Git actions, and a new action for squashing commits from the log
- Code Editing: new tools for finding problems in your code and an action for adding carets at the end of each selected line


WebStorm 2020.1.4
Fixed:
- Context menus in the Project view can now be opened if you’re using a language pack
- The problem causing the IDE to crash was solved


WebStorm 2020.1.3
- Several performance problems were solved
- Extra # is no longer added when completing #-private fields
- The bug with the Structure view failing to filter attributes and methods for JavaScript files was fixed


WebStorm 2020.1.2
Fixed:
- All known Node.js-related problems with WSL were solved
- The problem with CSS3 grid layout properties being improperly formatted was solved
- Angular Material events are now properly recognized after running ng build
- Several performance problems were solved
- Wrong project names and paths are no longer shown when you open a project using a shell script


WebStorm 2020.1.1
Bug fixes:
- A new option for running eslint –fix on save (WEB-24452): To enable this option for the current project, go to Preferences/Settings | Languages and Frameworks | JavaScript | Code Quality Tools | ESLint and tick the Run eslint –fix on save checkbox. To turn the new option on for all new projects, from the main menu go to File | New Project Settings | Preferences/Settings for New Projects and tick the same checkbox. Either way, don’t forget to disable the file watcher you’ve been using for this purpose.
- Improvements to WSL 2 support (WEB-44463, WEB-44507): You can now use the TypeScript Language Service, linters, and Prettier in projects located in the WSL file system. Besides that, we’ve fixed the issue where the IDE failed to stop the running Node.js process whenever you tried to hit the Stop button (for information on how to use Node.js on WSL, see our documentation).

Changes:
- Support for the ESLint 6.7 Suggestions API was added
- Hammer.js events are now recognized in Angular templates
- Several performance problems were solved
- Dependencies from pnpm workspaces are now properly indexed
- A number of disturbing, platform-wide bugs were fixed


WebStorm 2020.1
- WebStorm 2020.1, the first major update this year, is now available! It comes with a more polished look and feel, out-of-the-box support for Vuex and Composition API, an option to run Prettier on save, and improvements for JavaScript and TypeScript.
- If you only have a few minutes to explore what’s new in WebStorm 2020.1, watch this video where Paul Everitt, WebStorm Developer Advocate, reviews the most notable improvements. If you feel like diving a little deeper, read on!

The new features and improvements fall into these categories:
- Look and Feel: a new default editor font, a unified light theme, Zen mode for focused coding, quick documentation on hover, LightEdit mode for quick editing, and a customizable status bar.
- Frameworks: Vuex and Composition API support, completion for Vue in HTML files with CDN links, improvements to React support, and full support for Angular 9.
- JavaScript and TypeScript: more useful quick documentation, new smart intentions and inspections, support for TypeScript 3.8 features, and a reworked UI of the Introduce Field refactoring.
- Tools: run Prettier on save, split terminal sessions, bundled spell checker, Jest enhancements, TypeScript support with Yarn 2, and more flexible sharing of run configurations.
- Version Control: a reworked dialog for rebasing commits, improved work with branches, changes to the commit flow, and installing Git from the IDE


WebStorm 2019.3.4
- Change log not available for this version


WebStorm 2019.3.3
- Change log not available for this version


WebStorm 2019.3.2
New features:
- Support for loading Sass built-in modules with @use
- Initial support for type-only imports and exports in TypeScript 3.8

Fixed:
- Code completion for Node.js 13.5+ can now be enabled correctly on Windows
- Running tests with react-scripts now works again when using nvm
- The problem with running Karma tests in Angular apps was fixed
- yarn install is no longer incorrectly replaced with yarn add
- The issue with the resolve for Flow modules was fixed
- A couple of performance problems with JavaScript and TypeScript were solved


WebStorm 2019.3.1
New features and improvements:
- Support for TypeScript 3.7’s declare property modifier
- An option to fold template literals in JavaScript and TypeScript
- Improved resolve for Meteor packages

Fixed:
- The IDE correctly restores the layout of tool windows
- In .js and .ts files, Tab now selects a completion suggestion instead of expanding the Emmet abbreviation
- Several performance issues were fixed including WEB-42708 and WEB-42657
- The problem with debugging Node.js async hooks was solved


WebStorm 2019.3
Performance:
Faster startup:
- So far, one of the most common performance problems faced by WebStorm users has been the sluggish startup of the IDE. In the last two release cycles, we have devoted a lot of effort to reducing the time that users have had to wait for the welcome screen to show and for the IDE to open projects that are already indexed. As a result, you can now expect WebStorm to handle this 20% faster than previous versions

Frameworks & Tools:
Vue completion for separate files:
- More advanced code completion for Vue.js
- To help you increase the speed of your coding, WebStorm can now autocomplete slot names for you. This works for the slot names defined in the project components and component libraries such as Vuetify, Quasar, and BootstrapVue
- Plus, WebStorm now understands the link between parts of the component located in separate files and delivers accurate completion suggestions for props, data, and methods not defined in a single .vue file

Quick documentation in Vue.js projects:
- With WebStorm 2019.3, you can now check out documentation for components and directives defined in Vue.js and some popular component libraries. For this, simply press F1 on the name of a component or directive in your code

Support for the latest versions of popular technologies:
- WebStorm 2019.3 comes with support for 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: optional chaining, nullish coalescing, and assertion signatures

Better support for props in React components:
- For components without propTypes, WebStorm will no longer report an unresolved property for props.something in the component definition if it sees that props are passed in the component usage

JavaScript & TypeScript:
Template language injections:
- Need to work with a code fragment in a language different from the main language of the file? You can now inject such code fragments into your files, including Pug, Handlebars, and EJS, by pressing Alt-Enter

Name suggestions for new symbols:
- 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

HTML & Style Sheets:
Completion for CSS libraries on CDN:
- If you’re using Bootstrap or another CSS library in your project and you 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. To enable this, simply press Alt-Enter on the link in the HTML file and select Download library

Version Control:
Reworked UI for cloning projects:
- When you clone a project from a version control system, you’ll now see an updated Get from Version Control dialog shown on the welcome screen and the VCS menu.
With this redesign, we mainly wanted to improve the experience of getting projects from GitHub: you can now log in to your GitHub account right from the updated dialog. Once you’ve logged in, you can explore the list of repositories in your account and the organizations you belong to and clone projects to WebStorm right from there.

Pushing changes from any branch:
- Need to push changes from one branch while working with the other? With the latest update, you no longer need to switch to the branch you want to push changes from – simply select it from the Branches popup and hit Push

A more streamlined commit process:
- Now you can make commits right from the Version Control tool window – a separate dialog won’t block the rest of the IDE. For this, tick Commit from the Local Changes without showing a dialog in Preferences/Settings | Version Control | Commit Dialog

New actions for checking out branches:
- To resolve a number of usability issues, we replaced a single Checkout as... action with two new ones: a unified Checkout action for remote branches and the New Branch from Selected... action for both remote and local branches
- IDE

Run anything action:
New action for running tools and configurations:
- Need to launch tools like npm and Yarn, open recent projects, or start a run/debug configuration? You can now do it all from one place using the Run Anything action (Ctrl-Ctrl)

Searching in the selection only:
- With the new In Selection filter (Cmd/Ctrl-F twice), you can find specific pieces of information faster by narrowing down your searches to the selected parts of code in a file

Unbundling Dart support:
- Starting with WebStorm 2019.3, the Dart plugin will no longer be bundled. This was done to shorten the release cycles for it – bundled plugins can only be updated together with an update of the entire IDE. So, if you use Dart, you’ll now need to install the same Dart plugin from Preferences/Settings | Plugins

Enabling global file watchers by default:
- If you’re using a third-party tool like Prettier for a project and have it configured via a file watcher, it’s likely you may want this configuration to be automatically applied to all the new projects you create. Now you can achieve this by enabling global file watchers by default


WebStorm 2019.2.4
- Change log not available for this version


WebStorm 2019.2.3
- Change log not available for this version


WebStorm 2019.2.2
Fixed:
- CORS problem when debugging in Chrome caused by the x-ijt header was fixed
- Working directory is now set automatically when running a JavaScript scratch file with Node.js
- File watchers that reformat the code now better handle cases when file and class are renamed
- Shortcut for the “Stretch to Left” action for resizing Project View now works again
- Problem with saving updated settings for new projects was fixed


WebStorm 2019.2.1
New:
- In Angular projects, a different TSLint configuration specified in the angular.json file can be used for test files
- Better support for Vue components with TypeScript decorators
- Improved suggestions for scoped packages in package.json
- Support for CSS Media Queries Level 5
- “Duplicate declaration” inspection now works for TypeScript

What’s fixed:
- False-positive “Mismatched property value” error in SCSS and Sass files was fixed
- Invalid item no longer appears in the code completion suggestions
- Move refactoring now allows moving symbols between .ts and .tsx files
- Tabs inside JSDoc are now preserved when formatting the code
- Problems with typing some symbols using AltGr were fixed


WebStorm 2019.2
- Change log not available for this version


WebStorm 2019.1.3
- Change log not available for this version


WebStorm 2019.1.2
- Change log not available for this version


WebStorm 2019.1.1

- The first bug-fix update for the recently released WebStorm 2019.1, is now available
- Update to it using Toolbox App, or from the IDE. You can also download WebStorm 2019.1.1 from our website
- Syntax highlighting in the type info tooltip and documentation
- The tooltip that shows the expression type (Cmd/Ctrl-hover) in JavaScript and TypeScript files now has a syntax highlighting

Type info highlighting:
- We’ve also added highlighting for the code samples shown in the documentation popup

Highlighting in docs:
- Configuration for the use of aliases and path mappings in imports
- It is now possible to configure how aliases and path mappings will be used when adding imports automatically in JavaScript and TypeScript files. If you want to use relative paths when importing a symbol in the nearby file and use path mappings or aliases everywhere else in your app, you can select Only in files outside specified paths in the new option Use path mappings/aliases in Preferences / Settings | Editor | Code Style | JavaScript or TypeScript – Imports.

Other improvements and fixes in WebStorm 2019.1.1:
- Support for Cucumber step definitions written using strings
- New Reload in Browser action in the JavaScript debug tool window
- Performance problem when editing some TypeScript types was fixed
- Jump from the terminal to the editor for Esc
- Improved font rendering on macOS

The WebStorm Team:
- Posted in Release Announcements | Tagged newsletter, WebStorm 2019.1 | Leave a comment
- Featured plugin: JS GraphQL
- Posted on April 16, 2019 by Ekaterina Prigara
- The JS GraphQL plugin is one the most popular plugins for WebStorm, IntelliJ IDEA, and other JetBrains IDEs, and we are very excited about the release of its second version
- In this blog post we’ll have a closer look at the updated plugin and how it can help you work with GraphQL in your JavaScript apps
- We want to thank Jim Meyer, the author of the plugin, for the amazing work he has done to build this plugin!

Working with schema files:
- The plugin brings full support for the GraphQL Schema Definition Language (SDL). That means your .graphql file will include syntax highlighting, and as you start typing, you will get suggestions for the keywords and built-in and custom types, as well as interfaces and enums

Completion in schema file:
- Cmd/Ctrl-click the type name to navigate to its definition
- The plugin will check that all the types you’ve used are defined somewhere in the file, and it will show an error message if they’re not. Press Alt-Enter to fix the problem with one of the available quick-fixes


WebStorm 2019.1

Here are the features and improvements grouped by the WebStorm subsystems:
- JavaScript and TypeScript support: intentions for destructuring; convert function with Promise to async function; convert properties in constructor to class fields; inspections for switch statements; add or remove export; extended error messages in TypeScript
- Style sheets support: updated docs for CSS and browser compatibility check; extract CSS variable; camel case support for CSS Modules; support for Less 3.0 features
- HTML support: improved HTML documentation
- Development with Angular: new inspections for Angular projects; easier navigation in Angular projects
- Development with React: improved completion for merged props; Extract Method refactoring for custom React Hooks
- Development with Vue.js: better support for Vue projects with TypeScript
- Node.js and npm: completion for npm scripts; version range tooltip for dependencies; run and debug Node.js app when using Docker Compose; simple Node.js project template
- Linters integrations: improved support for ESLint and TSLint in complex projects; support for TSLint as TypeScript plugin
- Debugging: new debugger console
- Testing: highlighting for failed line in test; testing with Cucumber and TypeScript
- IDE improvements: Recent Locations popup; save project as a template; soft-wraps for selected file types
- Version Control: cherry-pick a file from a commit from the VCS log; incoming and outgoing commits


WebStorm 2018.3.5
- Change log not available for this version


WebStorm 2018.3.4
- Change log not available for this version


WebStorm 2018.3.3

New:
- Support for Set Literals in Dart
- Completion for attribute bindings in Angular (e.g. [atrr.foo] )
- Better coding assistance for some Ionic and @angular/flex-layout attributes

Fixed:
- Wrong indent after self-closing JSX tags in JavaScript and TypeScript files (WEB-36263)
- Decorators are now supported in the class expressions like let newTest = @test class Test or export default @observer class Test
- When using the bundled TypeScript service in Angular apps, the Angular language service is now disabled. Its current version is not compatible with TypeScript 3.2.1 and was reporting false errors in the template files


WebStorm 2018.3.2 Build 183.4886.41

New:
- Completion for Bootstrap Vue and Shards Vue components
- Better support for Prettier 1.15 and above
- The Extract interface refactoring now works for objects
- The IDE now bundles TypeScript 3.2

Fixed:
- The Optimize imports action now keeps the comment on top when ‘Sort imports
- by modules’ is on
- The usage of the Angular template reference variable in the ViewChild selector is now resolved
- The problem with using Hebrew in Find in path dialog was fixed


WebStorm 2018.3.1 Build 183.4588.47
- Change log not available for this version


WebStorm 2018.3 Build 183.4284.130
- Change log not available for this version


WebStorm 2018.2.6 Build 182.5107.19

Fixes
- The Search everywhere dialog on Linux no longer closes when you press Enter
- The usual UI for Find in path on Linux is now back
- On macOS Mojave, the input no longer freezes after adding the accented characters from the popup


WebStorm 2018.2.5 Build 182.4892.25
- Change log not available for this version


WebStorm 2018.2.4 Build 182.4505.50
- Change log not available for this version


WebStorm 2018.2.2 Build 182.4323.44

New:
- You can now pass additional option to Angular CLI when creating a new project from the IDE Welcome screen. As you start typing the option name or press Ctrl-Space, WebStorm will show you available options and their description
- We have also improved the way the new Add all missing TypeScript import action works: before, the action wasn’t available for symbols with multiple import options, and now, if you invoke the action for such symbol, WebStorm will add all unambiguous missing imports in this file and then will show you a popup where you can select the desired import for this symbol

Fixed:
- Vue component imports are now resolved correctly in the Vue CLI 3 apps located not in the root of the project
- The problem with the slash symbol in the CoffeeScript files has been fixed
- The Extract React Component refactoring now handles better the key attribute


WebStorm 2018.2.2 Build 182.4129.32

JavaScript and TypeScript:
New inspection tooltip:
- The new inspection tooltip now not only shows the description of an error or warning, but also the best quick fix for it
- Press Alt-Shift-Enter to apply it or press Alt-Enter to see a full list of the available automatic fixes that WebStorm offers there

Find unused code:
- With the new Code Coverage feature, you can find any unused code in your client-side app. Start a JavaScript Debug configuration with coverage in WebStorm, interact with your app in Chrome, and then stop the configuration. The report will show you what and how much code was used in each file and folder

New intentions:
- To make you even more productive when working with JavaScript and TypeScript, WebStorm has a bunch of new intentions that are available when you press Alt-Enter. Here are just some of them: Implement interface, Create derived class, Implement members of an interface or abstract class, Generate cases for 'switch', and Iterate with 'for..of'

TypeScript improvements:
- WebStorm now supports all the new language features that were added in the latest TypeScript 2.9 and the upcoming TypeScript 3.0 releases
- In addition to that, WebStorm now offers more quick fixes provided by the TypeScript language service itself, like Annotate with type from JSDoc

Frameworks:
Extract and convert React component:
- Need to refactor your React component into two? Forget copy and paste: select the JSX code in the render method and use Refactor - Extract Component
- And with the new intentions, you can now convert React class components into functional components and back again

New integrations with Angular CLI:
- Add features to your app with the New… | Angular Dependency… action. The IDE will use the Angular CLI ng add command which installs the dependency and updates the app with a special installation script
- You can now also generate the code with the Angular schematics defined in libraries like @angular/material using the New… | Angular Schematic… action

Completion for events in Vue.js:
- In Vue templates, WebStorm now provides code completion for events. Event names are suggested after v-on: or if you use the shorthand notation @event. There’s also code completion for event modifiers

Testing:
Rerun failed tests:
- When you run tests with Karma, Jest, or Mocha in WebStorm, you can now rerun only the failed tests, instead of running all the tests after you’ve made a fix

Diff view for Jest snapshots:
- If your Jest test has failed because of the mismatch in the snapshot, you can now see why using the familiar IDE side-by-side diff view
- It’s also now possible to quickly jump from the test file to the related snapshot by clicking on the new icon next to the test in the editor

Tools:
Support for Node.js on WSL:
- You can now use Node.js on Windows Subsystem for Linux to run and debug your Node.js application in WebStorm as well as for all other development tasks in the IDE, like running tests, using linters, and build tools

Reconnect Node.js debugger:
- Thanks to the new Reconnect automatically option in the Attach to Node.js/Chrome debug configuration, it is now easier to debug Node.js apps that use nodemon. When the node process is reloaded after the change, you don’t need to restart the debugger yourself to continue debugging

Global file watchers:
- You can now store the configured File Watchers in the IDE settings and use them in different projects. Before, a File Watcher could only be configured for a specific project. With File Watchers you can automatically run a command-line tool when you change or save a file in the IDE

Other improvements:
- New cleaner, simpler icons on the IDE toolbar and tool windows ensure readability and reduce visual clutter
- Run and debug your app, commit changes and update the project right from the Touch Bar on MacBook
- A new collection of over 50 code snippets for React development
- WebStorm now indexes a new Angular project two times faster, with no compromises affecting the quality of code completion and resolve
- You can now add custom templates for postfix completion in the JavaScript and TypeScript files
- With the new Drop frame action in the JavaScript and Node.js debuggers, you can re-enter a function if you missed a critical spot you would like to see again
- Press Alt-Enter on a line with a breakpoint and see the breakpoint-related actions in the list of intentions
- Support for JSON5 is now available in the files with the .json5 extension
- JSON Schemas files are now automatically downloaded from schemastore.org and applied to your files, based on the file name
- You can be logged into multiple GitHub accounts
- New Browse Repository at Revision action allows you to explore files in your project at any given revision without a checkout


WebStorm 2018.2.1 Build 182.3911.37

New:
- Auto imports now work better in projects that use lerna, yarn workspaces or TypeScript 3.0 project references
- The bundled TypeScript version was update to 3.0
- “Surround selection on typing quote or brace” option is now on by default
- Support for the Nullish Coalescing proposal in JavaScript

Fixed:
- JavaScript code completion now works better in webpack configuration files
- Changing the opening tag of the Vue component now updates the closing tag as well


WebStorm 2018.2 Build 182.3684.70
Here are the features and improvements grouped by the WebStorm subsystems:
- Development with React: Extract React Component refactoring, convert class components into functional components, code snippets, and improved completion for props in React and React Native apps
- Development with Angular: faster project startup, add new features using the integration with ng add, and run schematics from the IDE
- Development with Vue.js: completion for Vue events and event modifiers
- Node.js development: support for Node.js on Windows Subsystem for Linux, an ability to automatically reconnect the debugger to the running node process, and remote mappings in Attach to Node.js configuration
- Built-in tools: find unused code in the client-side app with Code Coverage reports, global File Watchers
- Editor: new UI for inspection tooltip
- JavaScript and TypeScript support: custom templates for postfix completion, and TypeScript 2.9 and 3.0 supported
- JSON support: JSON5, and Iimproved support for JSON Schemas
- Linters integrations: different highlighting for TSLint errors and warnings, and an ability to automatically apply code style rules from all types of ESLint and TSLint configuration files
- Debugging: breakpoint intentions, Drop Frame action, and debugging JavaScript scratch files
- Testing: rerun failed tests, navigate to Jest snapshot, compare Jest snapshots, and debugging Karma tests using Chrome Headless
- Version Control: Browse Repository at Revision action, completion for tags, register roots automatically
- Other IDE improvements: Touch Bar support


WebStorm 2018.1.5 Build 181.5281.31
- JavaScript Bug WEB-32790 WebStorm decides to stop accessing .d.ts files for es features for a project
- Node.js Bug WEB-32719 Add v8 to Node.js core modules
- TypeScript Bug WEB-32634 False positive Type mismatch error inside Angular Injectable
- No subsystem Bug IDEA-193747 Clicking Help | Register does nothing in a Toolbox-installed PhpStorm
- User Interface Bug IDEA-192713 focus is lost on opening Find Usages tool window
- Performance IDEA-192184 Goto Class/File/Symbol popups leak via native window and focus traversal policy
- Version Control Performance IDEA-192017 Unshelving creates a thread for each shelved file
- Version Control. Git Bug IDEA-191656 Git commit history with control characters causes intellij to spin, consuming CPU and repeating the same stack in the idea.log


WebStorm 2018.1.4 Build 181.5087.27
- It’s now possible to run and debug tests using Karma run/debug configurations in projects generated with Angular CLI 6 (WEB-32653)
- In Flow files, you can now press Cmd/Ctrl and hover over a symbol to see its type info. That works in projects where Flow server is used for navigation, code completion, and type hinting – the corresponding checkbox in Preferences | Languages and Frameworks | JavaScript should be checked. Navigation to the definition in Flow now works significantly faster than before


WebStorm 2018.1.3 Build 181.4892.44
- Change log not available for this version


WebStorm 2018.1.2 Build 181.4668.60
- Change log not available for this version


WebStorm 2018.1.1 Build 181.4445.68

New:
- Better support for Yarn workspaces: WebStorm now provides proper code completion for the dependencies listed in the workspace’s package.json
- In the JavaScript and TypeScript code style settings you can now configure whether to add file extensions in imports or not
- The bundled TypeScript package has been updated to version 2.8
- Stylelint now works in the Vue single-file components and the HTML files

Fixed:
- Move statement up and down now works for the JSX code (Shift-Cmd-Up/Down on macOS or Ctrl-Shift-Up/Down on Windows and Linux)
- The code completion for methods and properties defined in the CommonJS modules has been improved
- The problem with editing the Pug files is now fixed
- There is more about some of the improvements below

Support for Yarn workspaces:
- Yarn workspaces help you organize multiple packages into a single repo. When using Yarn workspaces, the dependencies of all the packages are installed together and are put into the node_modules folder at the root of your project and not next to the package.json file of each workspace


WebStorm 2017.3.3 Build 173.4301.22
New:
- Responses from the new REST Client are now formatted automatically
- Node.js debugger now supports –experimental-modules flag

Fixed:
- False positive errors from the eslint-plugin-import ESLint plugin were fixed
- Debug for apps created with Angular CLI 1.5.5+
- Debugging the app’s main process with Electron 1.8.1+
- Meteor debugger now uses –inspect by default


WebStorm 2017.3.1 Build 173.3942.31
New:
- Support for Fragments in React 16.2
- Configuration for the auto-completion after the = sign in JSX attributes is now available in the HTML Code Style preferences
- Customizable syntax highlighting for TypeScript decorators
- Extended error messages in the Flow tool window
- New option "Start template string interpolation on $"

Fixed:
- Unresolved React props when using @types/react
- Slow code completion for CSS classes in HTML files
- Optimize imports in Vue files
- Updating tasks from the issue trackers in the IDE
- Extend selection inside the script tag


WebStorm 2017.3 Build 173.3727.108
- Enjoy improved code completion and documentation for standard JavaScript objects and methods
- Move class methods up the class hierarchy safely with the new ‘Pull member up’ refactoring
- Use the new ‘Extract type’ and ‘Extract interface’ refactorings in TypeScript
- Enjoy better code completion and navigation and new code snippets for Vue.js
- Run tests with Jest in watch mode, update failing snapshots in one click, and explore code coverage reports in the IDE
- Test REST APIs right from the editor