-
Notifications
You must be signed in to change notification settings - Fork 5.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to load Meteor site in Safari/Firefox (Works fine in Chrome/Edge) #7474
Comments
Ok, looks like I have found the source of this error in one of our npm packages that we are using. In the index.js of the package it has a "use strict" at the top of the file and then uses the const keyword in the file after that. It seems that this causes issues with Safari so for now we are reverting back a couple of commits on this npm package to before they introduced this change... Hope that helps anyone else who has this problem... Cheers |
I had one (one!) package where I'd forgotten to add
|
Just had the same issue. Deleted cookies & other data in the browser and it worked again, no idea why. |
For the record, I had a very similar issue after upgrading to Meteor 1.7. Totally blank page, and none of my client code was run. In the Safari debugger, I found out that the error was from browser.js in the npm module 'debug', which was a dependency of 'needle' which was a dependency of 'node-pre-gyp' which was dependency of... 'bcrypt'. It turns out I had installed the bcrypt package to get rid of the message that my server always displayed at startup: Removing bcrypt (and getting that message back) fixed the issue on the legacy browsers! |
Hey all,
We are having a serious production issue with our Meteor 1.3 (and now 1.4) application when trying to access it from Safari or Firefox. The current production version of our application works fine under Meteor 1.2.1 on both Chrome and Safari.
We are now using version 1.4 of Meteor and the following are a sample of the many 'undefined' errors we see in the browser console:
However we don't see any of these issues in Chrome or even Microsoft Edge browser... Any ideas please?
Thanks
Rick
The text was updated successfully, but these errors were encountered: