Early Access Program Features

IntelliJ IDEA 2016.3 EAP Adds React Native Debugger

Last week we’ve announced a public preview of IntelliJ IDEA 2016.3. Today we’re publishing a fresh EAP build. Please give it a thorough look, and let us know (through our issue tracker) about any issues you’ll find.

In addition to bugfixes, this RC brings the support for React Native. Now you can run and debug React Native apps without leaving IntelliJ IDEA.

All it takes is a new React Native Run/Debug configuration. Just create one, select the target platform, and make sure that path to the React Native CLI package is correct.

The support assumes that you already have React Native installed and configured for the iOS or Android development. For OS X, we recommend to install Watchman, that worked good for us so far.

Note that currently there’s one limitation: the debugger isn’t compatible with Node 5. Make sure you have upgraded your Node to 6 or 7.

P.S: If you’ve missed the public preview announcement, make sure to read it to learn about other new features in IntelliJ IDEA 2016.3.

Develop with Pleasure!

Comments below can no longer be edited.

14 Responses to IntelliJ IDEA 2016.3 EAP Adds React Native Debugger

  1. Avatar

    John Shelley says:

    October 28, 2016

    Will this be for the Community Edition or only the Ultimate Edition of Intellij? I downloaded the Community Edition but I don’t see the React Native run configuration when I go to add a new configuration.

    • Avatar

      Andrey Cheptsov says:

      November 8, 2016

      It’s for Ultimate only as it depends on JavaScript/React.

  2. Avatar

    James Parsons says:

    November 8, 2016

    Does it support creating React Native projects or do we have to import them?

  3. Avatar

    iris says:

    November 10, 2016

    With React Native version 0.37.0,debug throw Exception “Maximum call stack size exceeded error”。
    Version 0.36.0 is OK。

    • Avatar

      Chris says:

      November 12, 2016

      I am getting the same error. Runs fine, without exception, if I run the app through Xcode without the WebStorm debugger.

    • Avatar

      Igor says:

      November 14, 2016

      Same for me. RN 0.37.0, ‘Maximum call stack size exceeded’.

    • Avatar

      farwayer says:

      November 22, 2016

      The same error 🙁

    • Avatar

      Amit says:

      November 23, 2016

      Same error too,

    • Avatar

      Amit says:

      November 23, 2016

      Problem persists in 0.38.0 as well – any way to fix this?

    • Avatar

      Luis says:

      November 24, 2016

      Same error

      Maximum call stack size exceeded
      Failed to print error: Requiring module “356”, which threw an exception.

    • Avatar

      M says:

      November 27, 2016

      Same err

      • Avatar

        Michael says:

        November 29, 2016

        I am having the same error with React-Native 0.38 and WebStorm 2016.3.1
        Build #WS-163.7743.51

    • Avatar

      Sam Bishop says:

      December 6, 2016

      React-Native 0.38.1,
      WebStorm 2016.3.1 – Build #WS-163.7743.51, built on November 23, 2016

      Run works ok. Debug Fails.

      Seems to be the same issue, “Maximum call stack size exceeded”.
      In my case, `Requiring module “229”… is there a YT issue for this yet?
      The only relevant one I could find, https://youtrack.jetbrains.com/issue/WEB-24443
      following the rabbit warren lead me to the issue being an upstream nodeJS bug, and MS have worked around it in https://github.com/Microsoft/vscode-react-native/pull/342, is WebStorm implementing the same or a similar workaround, and when will we be getting our hands on it ?

  4. Avatar

    Luke says:

    May 21, 2017

    Great, works great in IntelliJ Ultimate 2017.1.2.
    This setup guide at this link was essential: https://blog.jetbrains.com/webstorm/2016/12/developing-mobile-apps-with-react-native-in-webstorm/

Discover more