WebStorm 2018.3.1 is available

WebStorm 2018.3.1, the first bug-fix update for the recently released WebStorm 2018.3, is now available!

Update to it using Toolbox App or from the IDE. You can also download WebStorm 2018.3.1 from our website.

What’s new:

  • Support for TypeScript 3.2 features: BigInt (WEB-34802), object rest and spread on generic types (WEB-35664), configuration inheritance via node_modules packages (WEB-35522), and more.
  • Code completion for Vue.js instance methods and properties (WEB-28529).
  • Option to disable icons on the editor gutter for implemented and overridden methods (WEB-32824).
  • Configurable syntax highlighting for Angular templates (WEB-35815).
  • Support for the ECMAScript throw expression proposal (WEB-35752).

What’s fixed:

  • Methods and properties are now resolved in Angular templates written in Pug (WEB-35848).
  • 18 issues in the Angular support were fixed.
  • Shortcuts for “Close tab” and “Select next/previous tab” now work again in the terminal (IDEA-200854).
  • The prompt to override terminal history was removed (IDEA-202523).
  • Select in… now works in the Search Everywhere popup (IDEA-197872).
  • The problem with Replace in selection was fixed (IDEA-200011).
  • Indentation now works correctly when the display scaling is 250% or higher (IDEA-202087).
  • The problem with indexing when package.json contains "//" in dependencies was fixed (WEB-36082).

Please also see the Release Notes.

The WebStorm Team

About Ekaterina Prigara

Ekaterina Prigara is WebStorm product marketing manager at JetBrains. She's passionate about new technologies, UX and coffee.
This entry was posted in Release Announcements and tagged , . Bookmark the permalink.

9 Responses to WebStorm 2018.3.1 is available

  1. Stewart says:

    Any plans to support inline decorators, i.e.,
    export default @observer class MyComponent extends Component {

    …which gives a parsing error?

  2. Aliaksandr Hubitski says:

    “Go to definition” F12 still doesn’t work in Angular templates. It works fine in 2018.2.

    • Ekaterina Prigara says:

      Hello Aliaksandr, can you please provide a bit more details about the problem? For what symbols exactly it doesn’t work? Component tags, attributes, expressions in curly braces?.. A screencast showing an issue and a sample project would help. Thank you!

Leave a Reply

Your email address will not be published. Required fields are marked *