ESRI : Failed to parse source map

Question

I am getting this error in the Google chrome developer console.

Failed to parse SourceMap: http://localhost:15132/Scripts/_External/igniteui/css/themes/infragistics/infragistics.theme.css.map

How do I fix it?

Solution 1

Chrome recently added support for source maps in the developer tools. If you go under settings on the chrome developer toolbar you can see the following two options:

If you disable those two options, and refresh the browser, it should no longer ask for source maps.

These settings can be found here:

Solution 2

While the chosen answer is a good answer to hide the error, it doesn't make the error go away, it's just that you can't see it in the inspector. The other way would be to download the missing map file and put it in the assets/lib directory. So, for example, I was missing angular-route.min.js.map file and I went here https://code.angularjs.org/1.5.3/ (to the correct version of angular) and downloaded the missing file. The error didn't disappear right away, possibly because of caching, but once I went to the actual file in the browser it worked. http://sitename.localhost/assets/lib/angular-route.min.js.map. Now the inspector no longer displays the error even with source maps enabled.

Solution 3

Source code of CSS/JS we usually minified/compress. Now if we want to debug those minified files then we have to add following line at the end of minified file

/*# sourceMappingURL=bootstrap.min.css.map */

This tells compiler where is source file actually mapped.

In the case of JS its make sense
but in the case of CSS, its actually debugging of SCSS.

To Remove Warning: remove /*# sourceMappingURL=bootstrap.min.css.map */ from the end of minified file, .

Solution 4

Further to just simply turning off Source Maps in Chrome - I've done a little digging and found that using Web Essentials to create the source maps seems to be the issue.

For whatever reason, if I use an external compiler (Koala) I can successfully create working source maps in Chrome (no errors). Whereas if I use Web Essentials, the source maps fail to parse.

Hope this helps someone.

Solution 5

I had the same problem because .htaccess has incorrect settings:

RewriteEngine on
RewriteRule !.(js|gif|jpg|png|css)$ index.php

I solved this by modifying the file:

RewriteEngine on
RewriteRule !.(js|gif|jpg|png|css|eot|svg|ttf|woff|woff2|map)$ index.php

View more solutions

Comments

[jtheis]

Have you found any word from the Web Essentials team on this? I think we are having the same problem.

[Vicky]

Unfortunately I can't find anything about it - i'm in the process of inquiring!

[Steropes]

While source maps are great for working with minified javascript files, this error message appears and prevents normal debugging even when you don't need/want to use source maps. You're right that adding a source map would fix the issue, but if you don't have them, you'll want to disable this option to allow normal debugging.

[Willie Cheng]

Please check this URLit will be useful to lift your content quality up

[robstarbuck]

Thanks willie, I have read the guidelines. Did you feel there was something wrong with my answer?

[Ryan]

This was helpful to me because I was trying to set up Backendless.min.js and was seeing Failed to parse SourceMap in the Chrome console. When I switched to using the uncompressed Backendless.js (without the .min), I didn't get the error. I guess maybe source maps don't make sense when using minified javascript? I guess I could try to set up my local dev environment to use uncompressed JS + source maps and have only the production environment use compressed JS.

[ProblemsOfSumit]

what a stupid "feature". It should just load sourcemaps when they're available.

[Steropes]

Two sections up from this screenshot under Appearance is the Theme option. I've chosen the Dark theme.

[Turbo]

I need the source maps, but there is one map that isn't available for me. Lurking on Meteor forums indicates that Chrome has become pickier about content (certain names or unexpected format). I just have to ignore this error.

[demisx]

I don't think this is the answer. Hiding an error is not 'fixing' it, really. You need to figure out why you have a file referencing a non-existent source map file in the first place and then try to fix that.

[Quentin S.]

A Web Essentials-related fix can be found here: Google Chrome “Failed parsing SourceMap” : css.map (Web Essential)

[James Poulose]

Just a word of caution - if you disable those settings, be aware that your network tab will NOT show any traffic activity unless you hit F5 (on the n/w tab)

[Vasilii Suricov]

what is this? Apache? Is it webserver or just plugin?

[Donald Duck]

It took me a while to find where those settings were. Here is a screenshot showing where they are: i.stack.imgur.com/JQcnN.png. Maybe you should add that to your answer so that it's easier for people to find the settings.

[Taranis]

That was very helpful. Thank you, the problem was indeed from Adblock Plus.

[Steropes]

@DonaldDuck I've added it, per request!

[Hello World]

What about CSS source map??

[Goku]

This solution worked for me. Although I must say, I never saw this warning happen until I deleted and edited some default files within a react app. So maybe, I accidently deleted something integral to the setup. I'll check for warnings before I edit my next react app.

[Youssri Abo Elseod]

of course this solution not familiar with users , we can't request from user adjust advanced siting like this

[Inês Barata Feio Borges]

What happens if we disable source maps