fix: change inline-source-map to source-map for dev and common builds.

[TheLarkInn]

Fixes #1519 where either a chrome or webpack issue is causing inline-source-map and cheap-module-source-map to display inaccurately for development and production mode (in some cases).

[hansl]

LGTM

[masaanli]

Awesome 👍

[TheLarkInn]

Also fixes #1490

[masaanli]

I can confirm that it is fixed, but the build times are now twice as slow at my side :) But still workable. 2 seconds for each change as build time.

[mmrath]

It still does not work I think. simple ng new project is fine but once I add material2 ng serve throws error. If I revert the source-map change then it works. More details at #1490 (comment)

[brendanalexdr]

I am getting this debug/mapping mal-config problem too. The debugging was working fine for a while, but after my app got to a critical mass (like around 20 components) it has started to get wonkie: breakpoints won't hit, or impossible to set breakpoint (off by x number of lines)

angular-cli: 1.0.0-beta.18
node: 6.7.0
os: win32 x64

NPM: 3.10.8
OS: Windows 10 x64
Chrome: 54.0.2840.71 m (64-bit)

[filipesilva]

@nukuuk in beta.18 we have a sourcemap issue, but it will be fixed in beta.19

[brendanalexdr]

@filipesilva installed beta.19, and am still having problems setting breakpoints :(

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}