News for hackers. Stuff that matters.
Re:Debugging Node.js in Production by novaleaf on Friday December 04, 2015 @12:52PM (#10677829)
Re:Debugging Node.js in Production by mgr86 on Friday December 04, 2015 @12:53PM (#10677836)
I am using those.
Re:Debugging Node.js in Production by novaleaf on Friday December 04, 2015 @01:22PM (#10678029)
i use that + sourcemaps, and it seems pretty easy to debug.

using Chrome + React Dev Extensions

setting up sourcemaps to work properly is quite a pain though, most the browserify tooling via gulp or grunt does a pretty poor job of it.

Re:Debugging Node.js in Production by cozuya on Friday December 04, 2015 @02:30PM (#10678501)
Actually gulp has many great ways to work with sourcemaps, browserify, and babel. Google it and you should find a gist. I'm using through2.
Re:Debugging Node.js in Production by novaleaf on Saturday December 05, 2015 @11:22AM (#10682300)
I'm using typescript, which may impact my success, but really I don't get proper sourcemappings if I use uglify/browserify, or even the sourcemaps plugin.

I only get proper sourcemaps if I use the tsify plugin + setting browserify debug=true. adding anything else causes sourcemaps to go out-of sync. That's OK though, as I get good sourcemaps in development and can live without it when in production.