search

madskristensen / WebEssentials2013

Visual Studio extension
http://vswebessentials.com
Other
944 stars 252 forks source link

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

Open aukgit opened 8 years ago

aukgit commented 8 years ago

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 commented 8 years ago

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

hbopuri commented 8 years ago

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

aukgit commented 8 years ago

No not yet.

ghost commented 7 years ago

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