Google Chrome “Failed parsing SourceMap” : css.map (Web Essential) #1994

Open
aukgit opened this Issue Mar 22, 2016 · 4 comments

Projects

None yet

3 participants

@aukgit
aukgit commented Mar 22, 2016

Stackoverflow problem

Visual Studio 2013 UP5 + Web Essential's (v. 2.6.36) generated css.map files are invalid in "Google Chrome", however it is valid in "Firefox". Due to this it became impossible to debug less files in google chrome.

failed to parse sourcemap

Currently, I am using Web Essential 2.6.36 (+ Visual Studio 2013 Up5). I can disable the source map from google chrome's developer's setting. Which will remove those errors, however still we cannot debug less files and change the style. Which is a terrible problem.

@hbopuri
hbopuri commented Jun 1, 2016 edited

Is there a fix for this problem? I tried the answer from SO, but it didn't work for me.

@hbopuri
hbopuri commented Jun 1, 2016

@aukgit Sorry for the typo. I meant fix. Updated my comment.

@aukgit
aukgit commented Jun 1, 2016

No not yet.

@natect
natect commented Dec 14, 2016

Any word on this yet? Saving the css.map file as UTF-8 without signature fixes the source map file not being parsed by Chrome (Version 55.0.2883.87 m). Firefox parses the source map file just fine without the encoding workaround.
http://stackoverflow.com/questions/36133715/google-chrome-failed-parsing-sourcemap-css-map-web-essential

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment