Skip to content
This repository has been archived by the owner on Sep 25, 2020. It is now read-only.

Error: Failed to parse SourceMap in Chrome console #97

Open
toptalo opened this issue Jun 30, 2016 · 0 comments
Open

Error: Failed to parse SourceMap in Chrome console #97

toptalo opened this issue Jun 30, 2016 · 0 comments

Comments

@toptalo
Copy link

toptalo commented Jun 30, 2016

Get an error: "Failed to parse SourceMap" in Chrome console if option sourcesContent set to true

Run grunt-postcss plugin after grunt-sass.
if simple run grunt sass task SourceMap parsed correctly.

Also find this somehow related info in Stack Overflow:
http://stackoverflow.com/questions/36133715/google-chrome-failed-parsing-sourcemap-css-map-web-essential

Problem is that WebEssentials saves files in UTF8 with BOM, but Chrome is not able to open these files as .map files.
As a temporary fix, you can go to your .map file in Visual Studio and save it as a Unicode (UTF-8 without signature) or US-ASCII using

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant