CSS urls are broken when using sourcemaps

[filipesilva]

Fixing sourcemaps for global css in #4222 introduced a new bug due to webpack-contrib/css-loader#232.

While --sourcemap is enabled (default for dev) and --extract-css is disabled (default for dev), urls in css can become incorrect. See webpack-contrib/css-loader#232 for more details.

Temporary workaround is to serve with either --no-sourcemap or --extract-css.

[filipesilva]

The note on style-loader might be the real issue here: https://github.com/webpack-contrib/style-loader#recommended-configuration

Note about source maps support and assets referenced with url: when style loader is used with ?sourceMap option, the CSS modules will be generated as Blobs, so relative paths don't work (they would be relative to chrome:blob or chrome:devtools). In order for assets to maintain correct paths setting output.publicPath property of webpack configuration must be set, so that absolute paths are generated.

[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.}