Debugging server side code

[nasushkov]

Hi Thomas,

First of all, thank you for your boilerplate, I played with it for some time and I find it more useful and better structured than more popular ones. Still I don't understand how am I supposed to debug babel-transpired code on a server for this case. Most of the examples that I saw, use gulp to load source maps. Personally, I don't like gulp, and I find it overwhelming to use it only for such a purpose. Can you tell me, is there any better way to do this without gulp?

I also have some suggestions for this boilerplate, but I'd better put them in a separate issue.

Thanx.

[tomatau]

Hey @nasushkov ! Thanks for your compliments!

For debugging server code I tend to use tests mostly.

For units, you can actually run most of the smaller pieces of server code in the browser unit tests npm test and open localhost:9001... there are some server gotchas but a lot still works. Then you can use the browser's development tooling which is really neat.

Other than that it's a case of just logging to the console :S Have you got the DEBUG env configured in your .env file? I find it very useful.

I've experimented with node-inspector for babel before, but it didn't work very smoothly... I think it's quite an unexplored area, especially as the babel ecosystem is moving so quickly!

Feel free to post the suggestions! Sooner the better too... as I'm currently working on documenting as much as possible!

NB: I do have one small refactor I'm working on for the server render so that the asset control is more visible but it's quite small.

[nasushkov]

Yes, I use DEBUG. Still I'd like to use breakpoints and other things that are available in a browser. I'll post my suggestions later today. Thank you.