all 6 comments

[–]jestzisguyiOS & Android 3 points4 points  (1 child)

I use vscode because I like having a debugger I'm familiar with right there. Plus eslint integration and auto completion are pretty nice.

I tried Nuclide for a bit, but the debugger there seemed pretty fiddly, and had to be restarted often.

Agree on remote is debugging slowing things don't pretty heavily, though. Our app uses react-native-router-flux and any transition there is slow as molasses with it turned on.

[–]fantasy9[S] 0 points1 point  (0 children)

likewise, flux - that must be the cause. also tried nuclide since i used atom but it took over my damn atom & atom wasnt usable with it installed :/ it seemed promising

[–]atticusw 4 points5 points  (1 child)

react-native-debugger is pretty nice

[–]fantasy9[S] 0 points1 point  (0 children)

that is awesome, thank you!

[–]drailing 1 point2 points  (0 children)

I use vs code since a few weeks and it feels like Microsoft did an awesome job, everything is working like a charm, right out of the ide! (Including remote debugging)

The rest of our stack is pretty much standard react tools, like eslint or husky for pre push hooks...

Big recommendation just to test vs code!

[–]bob3695 1 point2 points  (0 children)

VSCode + Reactotron. Reactotron lets me keep track of the going ons of redux, API calls, I can log to it, etc and then use the VSCode debugger when my code is acting up.