Add node trace source map handling in dev mode

[kpdecker]

Fixes #2285

[erikras]

This will literally save hours of dev time, as it is currently so non-obvious what line is causing an error. 👍 👍

[timneutkens]

This looks really good, let me give it a few spins before merging 👌

[ptomasroos]

This is brilliant @kpdecker !

[timneutkens]

small typo: genenrate

[kpdecker]

Fixed

[timneutkens]

❤️

[arunoda]

This looks like something really great.
I'll give this a run and merge this.

[timneutkens]

Tried it last night, works 👌

[arunoda]

This is fantastic.
Thanks for the hard work @kpdecker

[arunoda]

I just published 3.2.0 which has this PR.

[dnakov]

This broke browser source maps.
To reproduce, run an example (e.g. with-absolute-imports) with next@3.2.0.
Source maps look like this:

null


// WEBPACK FOOTER //
// ./components/header.js

[kpdecker]

I can't really make sense of that output. What command is it from? What does your nextconfig look like?

[kpdecker]

And what browser?

[dnakov]

Chrome Version 60.0.3112.101 (Official Build) (64-bit) / MacOS 10.12.6 / Node 8.1.2

As I said above, just running the with-absolute-imports example in the repo with next@3.2.0 and looking at the source maps in chrome devtools.
The output is what chrome shows as the source-mapped source for components/header.js

[timneutkens]

I'm thinking this is most likely related to the absolute imports example 🤔 cc @sergiodxa

[dnakov]

I just tried a random example -- with-redux, same result.
Downgraded to next@3.0.6 and the source maps came back.

[KClough]

I'm also experiencing the same issue as @dnakov , I reverted back to next@3.1.0 and no longer see an issue with sourcemaps while debugging.

[kpdecker]

Fixed in #2900.