Failed to parse SourceMap (issue with Meteor 1.3?)

help
9

This randomly appeared in a project of mine today. Any news on this,?

10

I also saw something like this (still in 1.2)

11

Are you using Chrome Canary? It seems to be a Chrome issue, and it may not be a high priority for the Chrome team to fix this. So I would advise you be sure you’re using the beta or stable chrome release:

1 Like
12

I am having this issue all of sudden too in Chrome.
Version 49.0.2623.87 (64-bit)

Failed to parse SourceMap: http://localhost:5000/app.css.map

Anyone figure out a fix or exactly what’s up here?

13

yup. same here. after update to 1.3 and returning to 1.2.1

Failed to parse SourceMap: http://localhost:3000/de/export/error-stack-parser.min.js.map
14

This is still happening on the latest version of Meteor 1.3.2.4.

Failed to parse SourceMap: http://localhost:3000/5900bf1a492856b07ec0a28815a97a76e290cf7c.map

I have this import in my main.scss:

@import "{}/node_modules/bootstrap-sass/assets/stylesheets/_bootstrap.scss";

When I remove this import, the error goes away. Here’s what the map has when there’s the error:

{“version”:3,“sources”:[“meteor://💻app/node_modules/bootstrap-sass/assets/stylesheets/_bootstrap.scss”,“meteor://💻app/node_modules/bootstrap-sass/assets/stylesheets/bootstrap/_normalize.scss”,"meteor://💻app/packages/meteortoys_toykit/style/toykit. *snip*

15

Chrome Update to 50.0.2661.102 (64-bit) fix the problem for me

16

I updated Chrome (not Canary) to 51.0.2704.84 (64-bit) this morning and am also getting the error.

17

I had this error appear when I named a React component <Status /> - after changing the name of the component and its related filenames and folders, the error disappeared. Looks like there are certain words that Chrome doesn’t like in your file structure.

Hope this helps.

1 Like
18

I also am getting the error after updating to 51.0.2704.84

1 Like
19

I have fixed this issue by renaming all template files to camel case. - in template file name was causing issue with Chrome 51 in my case.

1 Like
20

I didn’t notice this error happening until i started operating on the non-default port (4000 in my case), but I’m not sure that has anything to do with it. I was on 1.3.2.4 without issues for a long time. I’m on 1.3.3 now and still happens. Perhaps a chrome update triggered it. On Chrome Version 51.0.2704.103 (64-bit)

21

This solves the problem.

2 Likes
22

To follow up, I needed to restart chrome to see the effects. (Just putting it out there, as most settings changes on chrome don’t require a restart).

24

This fixed the issue for me.

25

I’m getting this issue using Mantra and METEOR@1.3.4.1. When I don’t have things in /import it works fine. But once I move my /client to /imports/client I start getting the error.

26

Removing all minified js files resolved the problem for me

27

Hi, thanks, it solves my problem by installing Canary version of chrome. Now the source map works fine and I can debug on chrome happily :slight_smile:

28

Upgrading to Chrome 52.0.2743.82 cleared the issue up for me

29

Thanks, it fixed the issue for me.

1 Like