You can debug React Native apps in WebStorm now. You can set node as a debugging backend in the debug configuration with node < 8 or
-
-
Replying to @WebStormIDE @vvsevolodovich and
use Chrome as a debugging backend (then debug doesn't depend on node version). The experience in the IDE will be the same.
1 reply 0 retweets 1 like -
Replying to @WebStormIDE @vvsevolodovich and
More details here: https://youtrack.jetbrains.com/issue/WEB-27323
1 reply 0 retweets 1 like -
Replying to @WebStormIDE @cpojer and
Thanks for help! Although I am getting trouble debug through Chrome because WS tries to launch the Chrome from the project directory(???)
1 reply 0 retweets 0 likes -
Replying to @vvsevolodovich @cpojer and
You now need to specify the full path to Chrome (see my comment: https://youtrack.jetbrains.com/issue/WEB-27323#comment=27-2378000 …) We'll fix that in the next update.
1 reply 0 retweets 0 likes -
Replying to @WebStormIDE @cpojer and
That doesn't help, the Chrome app is still searched in the working directory. Looks like now there is now no debugging in
@WebStormIDE1 reply 0 retweets 0 likes -
Replying to @vvsevolodovich
Can't reproduce that :( Can you please send us the screenshot of the run/debug configuration and the browser configuration and the IDE logs
1 reply 0 retweets 0 likes -
Replying to @WebStormIDE @vvsevolodovich
Oh, wait, might've found a similar issue, will double-check and send a workaround. But anyway we hope to fix the original issue asap
1 reply 0 retweets 0 likes -
Replying to @WebStormIDE
Support level of my dream, thanks a lot! Can't wait)
1 reply 0 retweets 0 likes -
Replying to @vvsevolodovich
It seems that the correct path is lost on the IDE restart :( Related issues are https://youtrack.jetbrains.com/issue/IDEA-174479 … and https://youtrack.jetbrains.com/issue/WEB-27889
1 reply 0 retweets 0 likes
But we'll fix this one asap (so that no path changes would be required): https://youtrack.jetbrains.com/issue/WEB-27607 Hope the fix'll land in WS 2017.2.3 stable
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.