![]() I wouldn't say I'm "happy" with the developer experience now, but at least I have a bit fewer primal screams per hour. ![]() I had been following docs and hitting Cmd-R, but nothing ever happened, and then I was like "Why do I have like 25 gigs of iOS sim screen recordings on my hard drive?" and the eventual answer was that Cmd-R has been commandeered by Apple to mean "Start/Stop Screen Recording". I'm gonna look like a dumbass for this one but. And even then I'd just hop in the nvim boat again With it you can debug redux, react components, profile etc.Īlso, it's gonna take much more than react native to convince me to go back to vscode. The only thing i can suggest since you didn't mention using it is flipper. C++ linking errors are far easier to understand than a single "0 is not a function" with no reference to a line or file. It sort of works (for js related stuff) although it's still very very buggy.ĭon't even get me started on how difficult to read and how useless some react native errors are. We're lucky that jetbrains added support for hermes debugging, otherwise we couldn't even do that. Currently i have to write ts/js in intellij, then i have to switch to android studio to write java/c++. Not to talk about the impossibility to have one goddamn IDE to write both typescript, java and c++. (luckily there's rnx-kit that solves the problem). I spent a shitton of time figuring out how to link a local package i was creating for my app only to discover about this issue that is almost as old as react native itself. I use intellij instead of webstorm since they're the same thing basically. Help me Obi Wan Kenobi of RN, you're my only hope!.How do you get work done effectively? Specifically in the sense of rapid debug cycles.I use VSCode and everything just works for me." (I tried VSCode a year or two ago, and hated it - it seemed like I spent more time configuring plugins for basic functionality than I ever did writing code.)Īm I missing something fundamental here? Is it really this bad? Should I switch to VSCode? Should I give up on debuggers and just use console.logs? My other coworker says, "I couldn't tell ya. Not how I wanna do things, but you do you. One of my coworkers uses WebStorm and essentially said to me, "I don't know what you're complaining about, it works fine for me, but I don't use the debugger, I just use console.logs." Fine. God forbid the changes I'm making involve imports, because then, if there's a problem, the app only half-launches and then shunts me over to a inscrutable stack trace that references the transpiled/bundled source file, so it's damn near impossible to figure out where the actual problem is in the original JS/TS source. This feels ridiculous! How do people get work done like this? If I'm not changing the native code, why does it rebuild the native app every cycle? My debug cycle time is probably ~6 minutes total with this app. I'm just gonna put it out there: This seems like a very convoluted debugging setup. Then the native/shell app phones home to Metro, and that takes another 90sec or so.While this is happening, there are warnings/errors all over the place about how X can't talk to Y, but I've learned to "just wait longer" and they'll go away.Several minutes later, the xcodebuild operation completes, and installs the app onto the sim.It launches Chrome as a second debugger for some reason.There's a third tab, that may (or may not) eventually become the JS debugger. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |