Debugging not working well in Webpack Branch

[masaanli]

Please provide us with the following information:

1. OS? Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)
   Windows 10
2. Versions. Please run ng --version. If there's nothing outputted, please run
   in a Terminal: node --version and paste the result here:
   Beta 10 (webpack / master branch)
3. Repro steps. Was this an app that wasn't created using the CLI? What change did you

   do on your code? etc.

4. The log given by the failure. Normally this include a stack trace and some

   more information.

5. Mention any other details that might be useful.

---

Thanks! We'll be in touch soon.

The debugging isnt working anymore in firefox, chrome or edge.

When I put a breakpoint nothing happens.
When I put a debugger command, it's debugging at strange lines. not where I put the debugger command.

[sirajc]

Some issue on Chrome dev tools side, AFAIK

[masaanli]

@sirajc It's also not working in Firefox for me.
It isn't very easy to work with now hehe;)
With beta 10 from NPM (SystemJS) It was working previous week ;)

[intellix]

I've noticed this actually. If I place a breakpoint inside a mapped TS file, the breakpoint will move up the file about 10-20 lines above and obviously not work. It seems the maps aren't quite correctly generated

[jmc265]

I believe this is a Typescript-mapping problem only. Mapping onto Javascript files (e.g. node dependencies) work fine.

[sirajc]

@TheLarkInn Can you have a look please

[iamyojimbo]

I have also noticed that console errors point to lines far from where the actual error occurred

[masaanli]

Tried to update to the latest Angular CLI Beta 11 Webpack, (NPM) but not worked.

[Namek]

Actually, for me it's sometimes not working properly even before upgrading to webpack (using PhpStorm)

[masaanli]

@Namek Do you mean the Webpack Branch or just the Masterbranch where Webpack is inside?

[masaanli]

I just looked again at this issue and to be more specific; I'm having the same problem on Firefox and Internet Explorer.

@TheLarkInn got some progress on this one?

[Namek]

Yesterday I didn't even touch anything related to webpack in this project. Maybe my webstorm is broken.

[abner]

Actually the problem is being caused by the sourcemap-istanbul-instrumenter-loader which was setup to always instruments the typescript app code in the webpack-build-test.js. Would be better to have a task specific for coverage where the instrumentation would take place. The test tasks will run without instrumentation so we could debug it.

[TheLarkInn]

We did just cut a new release on the webpack tag this morning with improved coverage settings. Would you mind just double checking if mappings work on prod and dev.

[masaanli]

@TheLarkInn going to check it today!