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?

Steropes · Accepted Answer · 2020-03-06T20:03:28.550

333

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:

edited Mar 06 '20 at 20:03

answered Mar 17 '16 at 19:09

Steropes

4,600
2
22
26

106

what a stupid "feature". It should just load sourcemaps when they're available. – ProblemsOfSumit Jun 10 '16 at 09:06
9

Two sections up from this screenshot under Appearance is the Theme option. I've chosen the Dark theme. – Steropes Jun 10 '16 at 14:35
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. – Turbo Jul 19 '16 at 18:12
89

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. – demisx Aug 19 '16 at 21:32
4

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) – James Poulose Feb 02 '17 at 20:44
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. – Goku Oct 27 '20 at 17:45
What happens if we disable source maps – Inês Barata Feio Borges Jan 02 '21 at 12:58

score 36 · Answer 2 · answered Apr 15 '16 at 19:40

36

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.

answered Apr 15 '16 at 19:40

Chemist

967
2
15
28

4

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. – Steropes May 03 '16 at 18:41
1

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. – Ryan Jun 05 '16 at 16:26

score 16 · Answer 3 · edited Feb 29 '20 at 11:40

16

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.

edited Feb 29 '20 at 11:40

Donald Duck

8,409
22
75
99

answered Mar 18 '16 at 11:13

Vicky

161
2

3

Have you found any word from the Web Essentials team on this? I think we are having the same problem. – jtheis Mar 18 '16 at 21:21
2

Unfortunately I can't find anything about it - i'm in the process of inquiring! – Vicky Mar 21 '16 at 08:50
1

A Web Essentials-related fix can be found here: [Google Chrome “Failed parsing SourceMap” : css.map (Web Essential)](http://stackoverflow.com/questions/36133715/google-chrome-failed-parsing-sourcemap-css-map-web-essential) – Quentin S. Aug 31 '16 at 12:26

score 16 · Answer 4 · answered Nov 27 '19 at 04:20

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, .

score 8 · Answer 5 · answered Nov 21 '16 at 10:32

8

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

answered Nov 21 '16 at 10:32

Kas Elvirov

7,394
4
40
62

what is this? Apache? Is it webserver or just plugin? – Vasilii Suricov Feb 28 '20 at 14:36

Roger Perez · Answer 6 · 2022-08-18T20:24:41.577

6

For cra/react-scripts 5.0.0 it looks like there is a bug. I had to create a .env file and add the following

GENERATE_SOURCEMAP=false

Note: This is a patch. Once a fix is implemented you will want to remove the line and update to fixed patch version.

Update: react-script 5.0.1 does not fix this issue unfortunately

edited Aug 18 '22 at 20:24

answered Feb 03 '22 at 17:36

Roger Perez

2,807
29
31

Can you explain the downsides of using this solution on the problem? – CrmXao Jan 12 '23 at 18:13

score 4 · Answer 7 · answered Feb 13 '20 at 22:41

4

This may sometimes be caused by Chrome extensions you've installed. For example, AdBlock.

Unfortunately the best solution I could find was to disable the offending extension.

answered Feb 13 '20 at 22:41

Vael Victus

3,966
7
34
55

That was very helpful. Thank you, the problem was indeed from Adblock Plus. – Taranis Mar 06 '20 at 10:32

score 3 · Answer 8 · answered May 18 '16 at 08:41

3

When I had this issue the cause was a relative reference to template files when using the ui.bootstrap.modal module.

templateUrl: 'js/templates/modal.html'

This works from a root domain (www.example.com) but when a path is added (www.example.com/path/) the reference breaks. The answer in my case was simply to making the reference absolute (js/ -> /js/).

templateUrl: '/js/templates/modal.html'

answered May 18 '16 at 08:41

robstarbuck

6,893
2
41
40

Please check this [URL](http://stackoverflow.com/help)it will be useful to lift your content quality up – Willie Cheng May 18 '16 at 09:04
12

Thanks willie, I have read the guidelines. Did you feel there was something wrong with my answer? – robstarbuck May 18 '16 at 10:55

score 2 · Answer 9 · answered Apr 12 '20 at 03:48

2

The error in the Google DevTools are caused Google extensions.

I clicked on my Google icon in the browser
created a guest profile at the bottom of the popup window.
I then pasted my localhost address and voila!!

No more errors in the console.

answered Apr 12 '20 at 03:48

Roland Brenevil Jr

21
1

score 1 · Answer 10 · answered Feb 18 '20 at 14:12

1

Check if you're using some Chrome extension (Night mode or something else). Disable that and see if the 'inject' gone.

answered Feb 18 '20 at 14:12

BolonhaDev

11
1

score 0 · Answer 11 · answered May 30 '20 at 05:15

0

I noticed that problem because of AdBlock Extension, I turned off AdBlock extension the issue got resolve.

answered May 30 '20 at 05:15

Rakshith R Salian

1
1
1

score 0 · Answer 12 · answered Sep 03 '22 at 11:59

0

Issue: Source maps 404

Windows 10 (all updated), Google Version 105.0.5195.102 (Official Build) (64-bit).

Fix was to DISABLE Add Block extension.

answered Sep 03 '22 at 11:59

Ben Reay

1

ESRI : Failed to parse source map

12 Answers12

Linked