I started getting this I think when I upgraded to use the latest beta of Meteor 1.3. Has anyone else seen this?
It’s hard to do anything… because my browser console is overwhelmed with these messages.
I just started noticing the same thing, still on v1.2.1 – in fact, the only thing I’ve upgraded recently is Kadira. Wondering if that’s causing it…
Kadira… specifically which package?
meteorhacks:kadira@2.28.1
hm, I’m not using it. Here’s exactly what I’m using, on METEOR@1.3-beta.11
accounts-base@1.2.3-beta.11
accounts-password@1.1.5-beta.11
allow-deny@1.0.1-beta.11
audit-argument-checks@1.0.4
autoupdate@1.2.5-beta.11
babel-compiler@6.4.0-beta.11
babel-runtime@0.1.5-beta.11
base64@1.0.5-beta.11
binary-heap@1.0.5-beta.11
blaze@2.1.4-beta.11
blaze-html-templates@1.0.1
blaze-tools@1.0.5-beta.11
boilerplate-generator@1.0.5-beta.11
caching-compiler@1.0.1-beta.11
caching-html-compiler@1.0.3-beta.11
callback-hook@1.0.5-beta.11
check@1.1.1-beta.11
coffeescript@1.0.12-beta.11
cosmos:browserify@0.9.3
ddp@1.2.2
ddp-client@1.2.2-beta.11
ddp-common@1.2.2
ddp-rate-limiter@1.0.1-beta.11
ddp-server@1.2.3-beta.11
deps@1.0.9
diff-sequence@1.0.2-beta.11
ecmascript@0.4.0-beta.11
ecmascript-runtime@0.2.7-beta.11
ejson@1.0.8-beta.11
email@1.0.9-beta.11
es5-shim@4.3.2-beta.11
fastclick@1.0.8-beta.11
fortawesome:fontawesome@4.5.0
geojson-utils@1.0.5-beta.11
hot-code-push@1.0.1-beta.11
html-tools@1.0.6-beta.11
htmljs@1.0.6-beta.11
http@1.1.2-beta.11
id-map@1.0.4
jagi:astronomy@1.2.10
jagi:astronomy-slug-behavior@1.3.0
jagi:astronomy-timestamp-behavior@1.1.0
jagi:astronomy-validators@1.1.2
jagi:reactive-map@2.0.0
jquery@1.11.5-beta.11
kadira:flow-router@2.10.0
launch-screen@1.0.6-beta.11
livedata@1.0.15
localstorage@1.0.6-beta.11
logging@1.0.9-beta.11
meteor@1.1.11-beta.11
meteor-base@1.0.1
meteor-env-dev@0.0.1-beta.11
meteor-env-prod@0.0.1-beta.11
minifier-css@1.1.8-beta.11
minifier-js@1.1.8-beta.11
minimongo@1.0.11-beta.11
mobile-experience@1.0.1
mobile-status-bar@1.0.8-beta.11
modules@0.5.0-beta.11
modules-runtime@0.5.0-beta.11
mongo@1.1.4-beta.11
mongo-id@1.0.1
npm-bcrypt@0.7.8_2
npm-mongo@1.4.40-beta.11
observe-sequence@1.0.8-beta.11
ordered-dict@1.0.4
percolate:find-from-publication@0.1.0
promise@0.5.2-beta.11
random@1.0.6-beta.11
rate-limit@1.0.1-beta.11
reactive-dict@1.1.4-beta.11
reactive-var@1.0.6
reload@1.1.5-beta.11
retry@1.0.4
reywood:publish-composite@1.4.2
routepolicy@1.0.7-beta.11
service-configuration@1.0.6-beta.11
session@1.1.2-beta.11
sha@1.0.4
spacebars@1.0.8-beta.11
spacebars-compiler@1.0.8-beta.11
srp@1.0.5-beta.11
standard-minifier-css@1.0.3-beta.11
standard-minifier-js@1.0.3-beta.11
templating@1.1.6-beta.11
templating-tools@1.0.1-beta.11
tracker@1.0.10-beta.11
ui@1.0.8
underscore@1.0.5-beta.11
url@1.0.6-beta.11
webapp@1.2.5-beta.11
webapp-hashing@1.0.6-beta.11
here’s me right now
accounts-password@1.1.4
accounts-ui@1.1.6
blaze-html-templates@1.0.1
ecmascript@0.1.6*
es5-shim@4.1.14
hammer:hammer@2.0.4_2
jquery@1.11.4
meteor-base@1.0.1
meteorhacks:kadira@2.28.1
meteorhacks:kadira-profiler@1.2.1
meteorhacks:zones@1.6.0
mizzao:autocomplete@0.5.1
mobile-experience@1.0.1
mongo@1.1.3
react@0.14.3*
reactrouter:react-router@1.0.3
session@1.1.1
standard-minifiers@1.0.2
tracker@1.0.9
Don’t think it’s Meteor.
Doesn’t happen in Firebug, for example.
I think it’s specifically a Chrome Devtools thing.
There’s this link where something about this is going on.
https://www.google.it/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&uact=8&ved=0ahUKEwjXt76woJXLAhXE7Q4KHWMpBOEQFgglMAA&url=https%3A%2F%2Fgroups.google.com%2Fa%2Fchromium.org%2Fforum%2F%23!topic%2Fchromium-reviews%2FqKtfNbb7TWI&usg=AFQjCNHoZ3IHFPImQ-uy8pIFmI-cAuKzWw&bvm=bv.115339255,d.bGQ
Same thing here, using Chrome Canary.
3 Likes
This randomly appeared in a project of mine today. Any news on this,?
I also saw something like this (still in 1.2)
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
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?
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
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*
Chrome Update to 50.0.2661.102 (64-bit) fix the problem for me
I updated Chrome (not Canary) to 51.0.2704.84 (64-bit) this morning and am also getting the error.
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
I also am getting the error after updating to 51.0.2704.84
1 Like
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
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)