WebStorm 2017.2.1 is now available

WebStorm 2017.2.1, the bug-fix update for the recently released WebStorm 2017.2 is now available!

You can install this update using Toolbox App. If you’re using WebStorm 2017.2 or 2017.2.1 EAP, you can update directly from the IDE.

If you’re still using an earlier version, check out the new features in WebStorm 2017.2 and download it from our website.

What is fixed in WebStorm 2017.2.1:

  • Karma integration now properly sees changes when re-compiling the code (WEB-12496 and WEB-21308)
  • React render method is no longer marked as static (WEB-19028)
  • Flow: auto import now works for types (WEB-24910); support for union optional type as arrow function return type (WEB-27666)
  • Auto import for React components now works in .tsx files (WEB-20211)
  • Tab limit can again be set to 1 (IDEA-173369)
  • Errors from ESLint are now highlighted in .vue files (WEB-27868)
  • Debugging React Native apps: you can now use Chrome as a debugging backend instead of Node.js 8 (WEB-27323)

You can find a full list of addressed issues in the Release Notes.

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.

4 Responses to WebStorm 2017.2.1 is now available

  1. Jakub Beránek says:

    Thank you for this patch, React Native debugging with Chrome backend is a welcome addition :-)

    Would it be possible to add an option to specify command line parameters to the ‘react-native-cli start’ (packager) command or make it respect the ‘npm run start’ script?

    Here’s my scenario:
    I need to specify parameters to the ‘react-native-cli start’ command (otherwise my application won’t run properly). However WebStorm only lets me set parameters for the run-[android|ios] command.

    When I start the debug session, it fails, because it runs the RN-CLI start without my parameters.
    When I start the packager server and then the debug session, the debug session fails because it tries to start the packager on it’s own and it dies (because the TCP port is taken).
    When I start the debug session, then kill its packager and start packager with my parameters, the debug session dies.

    So I’m basically out of luck :-)
    Is there any workaround? Thank you for answer.

    • Ekaterina Prigara says:

      Unfortunately, there’s no workaround now, but we are going to add a possibility to pass the options in the nearest future. Please follow this issue for updates: https://youtrack.jetbrains.com/issue/WEB-27797

      • Jakub Beránek says:

        Thank you for your answer :-)

        By the way, is there any way to contribute this change (as a PR for example) or is that only available for the IDEs with community versions (IntelliJ Community, PyCharm community)?

        • Ekaterina Prigara says:

          The IntelliJ platform (the one all JetBrains IDE are based on) and some WebStorm functionality are open sourced, but not the React Native support.
          But thank you for your interest in contributing to WebStorm! We appreciate that!

Leave a Reply

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