Break the sourceMappingURL string to avoid confusing Chrome.

[kring]

We recently started seeing "Failed to load SourceMap" problems loading in our app in Chrome 51. I eventually tracked it down to this line in style-loader's addStyles.js:

css += "\n/*# sourceMappingURL=data:application/json;base64," + btoa(unescape(encodeURIComponent(JSON.stringify(sourceMap)))) + " */";

I suspect that Chrome is incorrectly interpreting this as an actual sourcemap reference. In any case, breaking up the sourceMappingURL solved the problem for us, so I hope you might consider merging this simple workaround!

For what it's worth, the problem does not occur in Chrome Canary, but that's not expected to hit stable until September or October.

[michael-ciniawsky]

Related #181

[michael-ciniawsky]

@kring Current direction seems to be solving this in source-map-loader itself, please join discussion in #181

[ekulabuhov]

Filed against Chrome 51. It seems to be fixed now since version 52 (according to dvdzkwsk/react-redux-starter-kit#858 (comment)). Probably can be closed?

[michael-ciniawsky]

Closed in favour of #181 or direct fix in source-map-loader also proposed in #181