Debugging with generator-ng2-webpack projects

[cmelion]

"I found it challenging to debug this because the default "npm start" script generated a build with webpack that was fairly opaque. I do not believe source maps were turned on in the generated build, and so it was difficult to debug the built JavaScript to see what might be wrong. " - Jake

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/33406773-debugging-with-generator-ng2-webpack-projects?utm_campaign=plugin&utm_content=tracker%2F32095848&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F32095848&utm_medium=issues&utm_source=github).

[cmelion]

generator-ng2-webpack projects use webpack's devserver and sourcemaps are generated for both script and css. A good explanation of the process can be found at http://stackoverflow.com/a/33422697

[cmelion]

[jbeard4]

I will review the link. Thank you.

[cmelion]

Can you confirm if https://github.com/cmelion/generator-ng2-webpack/issues/28 fixes the browser open issue on Linux?

On Thu, Apr 28, 2016 at 7:37 PM, Jacob Beard [email protected] wrote:

I will review the link. Thank you.

— You are receiving this because you modified the open/close state. Reply to this email directly or view it on GitHub https://github.com/cmelion/generator-ng2-webpack/issues/27#issuecomment-215593455

[cmelion]

reopening due to related issue https://github.com/cmelion/generator-ng2-webpack/issues/32

Also it's unclear how to debug unit tests using a docker based workflow