WebStorm 2017.1 EAP, 171.2272: Standard code style, completion in package.json

Please welcome a new Early Access Preview build for WebStorm 2017.1 (171.2272.15)! You can download it here and install it side-by-side with your current stable WebStorm version, or if you have the previous EAP build, you should soon get a notification in the IDE about a patch update.

Completion for dependencies in package.json

Adding new project dependencies to package.json became easier: WebStorm now provides code completion for package names and shows info about the latest versions.



Support for JavaScript Standard Style

WebStorm now adds support for JavaScript Standard Style, a popular JavaScript code style.

Now you can configure WebStorm code style options for JavaScript to follow the main rules Standard declares and they will be applied when you type the code or reformat it.

For that go to Preferences | Editor | Code style | JavaScript and click Set from Predefined Style – Standard and the style will replace your current scheme.


Since Standard is based on ESLint, you can use Standard via WebStorm’s ESLint integration. If you open a new project and Standard is listed in package.json, WebStorm will notice that and will enable linting with Standard automatically. WebStorm will also suggest to set Standard code style for formatting (also if you have ESLint with Standard plugin).


You can also enable Standard in the ESLint Preferences (Languages & Frameworks | JavaScript | Code quality tools | ESLint): you need to select a path to Standard package installed globally or locally in the project.

You can find the full list of issues addressed in this EAP build in the Release notes.

Learn more about other new features in WebStorm 2017.1:

  • WebStorm 2017.1 EAP, 171.1834: Run Mocha tests with the gutter icon; The test status is now shown right next to the test; Integration with the Angular language service; Linters are now detected and enabled by default for the new projects; Support for emoji in the editor; Zero-latency typing is now enabled by default.
  • WebStorm 2017.1 EAP, 171.2014: New intentions that convert forEach and for..in iterations over arrays to for..of; Code style options for quotes and ternary operators; New inspection Equality operator may cause type coercion.
  • WebStorm 2017.1 EAP, 171.2455: Improved integration with TSLint; Code style options for the use of semicolons in JavaScript and TypeScript.
  • WebStorm 2017.1 EAP, 171.2822: Initial support for Vue.js; Code style option for trailing comma; Debugging Dart VM tests.

Please report your feedback to our issue tracker. To get notifications of new EAP builds as they become available, subscribe to the EAP channel in Preferences | Appearance & Behavior | System Settings | Updates.

– JetBrains 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 Early Access Preview and tagged . Bookmark the permalink.

30 Responses to WebStorm 2017.1 EAP, 171.2272: Standard code style, completion in package.json

  1. Filip Szczechowiak says:

    Hi, is there any eta when this: https://youtrack.jetbrains.com/issue/IDEA-159223 will hit beta release?

    PS. this is something for what most devs using docker was waiting for..

  2. Lasse says:

    If used with the postcss plugin you cannot open TypeScript tsx files for example. Breaks the editor.

  3. Please, please fix indentation in Angular 2 template strings. It’s annoying as hell having to manually enter tabs every time you edit a template string and using the fragment editor is even more annoying: https://stackoverflow.com/questions/36208948/webstorm-template-string-html-format-with-angular-2

    Please, even VSCode has this working…

  4. Alfred Obialo says:

    Will there be support for nativescript cli?

  5. Paul says:

    Having the Google Code Style Guidelines as a preset would be also awesome.

  6. Alex Maroz says:

    In MacOS in the terminal tab CTRL+C not working anymore. I can’t interrupt the process. After hitting CTRL+C it just inserts “new line” symbol in terminal.

  7. zhang says:

    After the installation is successful, the application cannot be opened

  8. soliury says:

    I have a problem, the standard don’t read config from package.json.
    Sometime, I want to ignore some file, or to format the .vue file. And the webstorm don’t work

  9. Bryan Chu says:

    Hi, I think Webstorm’s language of “Specify the path to Standard package to use Standard Code Style” is incorrect/confusing?


    It should point to the eslint package that is installed during standard’s installation from npm as if I point it to node_modules/standard, there is an error as listed by the question on stackoverflow.


    • Bryan Chu says:

      actually, I apologize, the solution I listed above is if the user has a .eslint.rc in their project and webstorm, well eslint defaults to the nearest .eslint.rc. terribly sorry

      • Ekaterina Prigara says:

        Hi Brian,
        the steps described in the blog post are correct – you need to specify the path to the Standard package.
        Some users have stumbled upon the issue similar to the one you’re referring to, but neither we nor the user were not able to reproduce it again. We have fixed some Standard-related issues in WebStorm 2017.1.2, please give it a try – it is now available as a Release candidate, will be released today or tomorrow.

        • Bryan Chu says:

          Hi Ekaterina,

          Apologies, Webstorm instructions are correct. I had an .eslint.rc in my project’s root from a previous project. Once I removed the legacy .eslint.rc, all was well. Thank you for the prompt reply.

  10. For anyone running into an issue with the new Standard Style support (Throwing Error: “ESLint initialization Error: Use of const in strict mode”): Make sure your node interpreter isn’t too old. I had a 0.10.x version in there and that caused Standard Style support to throw an error.

  11. At the moment I’m having troubles with Standard Style support in conjunction with React. E.g. in a file defining a React component I need to import React from 'react', but Standard Style complains about: “‘React’ is defined but never used (no-unused-vars)”.

    The same goes for imports of other React components, let’s say import Button from './Button' which is then used in jsx syntax. Still Standard Style complains about the Button that is never used.

    I need to add, that when running Standard Style from the command line for the same file, there are no complaints (I used standard from my node_modules and it’s the same I pointed ESLint inside of Webstorm to)…

    How can this be resolved?

  12. Nick says:

    I don’t understand why reformatting the code doesn’t follow the standard style. The code still keeps on complaining about things like react/jsx-tag-spacing?

Leave a Reply

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