Sourcemaps problem in 1.3.3

core
1

I’m getting a “Failed to parse SourceMap” message in Chrome ever since updating to Meteor 1.3.3. Is this a known problem?

6 Likes
2

Not sure but I was getting it too. It seems to have disappeared now though and I don’t know what’s changed.

3

It’s back.

Failed to parse SourceMap: http://localhost:3000/packages/7214728d388f610508afa2a208b6117470822707.map

The first line is:

{"version":3,"sources":["meteor://💻app/packages/geojson-utils/main.js","meteor://💻app/packages/geojson-utils/geojson-utils.js"],"names":
4

Yes, I noticed it too after the meteor update to meteor 1.3.3.

On my Chromium 51: the error message show up
On my Chrome 48: the error message doesn’t show up

5

Same here. Didn’t find where the problem from from :confused:

6

I’ve got the same problem. :frowning:

7

Same here :frowning:

8

getting same error here… :frowning:

9

This error has been reported in the Meteor issues. Those of you experiencing it might want to try to add detail to that report if you know any specifics not reported that could help in narrowing down the cause or duplicating the issue.

1 Like
10

I had to downgrade to previous version of Chrome (found here: http://www.slimjet.com/chrome/google-chrome-old-version.php). Updating Meteor and packages didn’t resolve it.

11

I’ve added this to the github issue above as well…

I think it might be this chrome issue,

https://bugs.chromium.org/p/chromium/issues/detail?id=611328

In hindsight it probably started the other day when I let chrome upgrade to 51 and doesn’t occur in canary.

12

Installing Chrome beta (52) did the trick for me