-
Notifications
You must be signed in to change notification settings - Fork 88
-
Notifications
You must be signed in to change notification settings - Fork 88
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
Vulcan-Starter with errors on Chrome for example-instagram #55
Comments
Same here, could not fix it yet |
Maybe the team is still looking at it, give them a few more days or I have to switch to use other framework. Sigh. |
I fixed the issue with the missing photos. As for the error messages, it seems to be some kind of Meteor error, I'm not sure it's related to Vulcan directly. I'd suggest doing:
Let me know if this works! |
Hey @SachaG thanks for some hints, I just went through the bulletpoints but it didn't help. And it's not an issue specific with the instagram example, these Uncaught Typerror's come up no matter with what packages you bring up the starter project. I have Node v8.11.1 installed and completely reinstalled Meteor from meteor.com MacOS High Sierra 10.13.4 |
Thanks @SachaG but it sounds like still a blocker. Shall we raise it to https://forums.meteor.com/ for the group to look at? if it is sounds like due to the incompatible between meteor / node / npm? Really love to use this framework but it have to be runnable, before we can code..... |
I have raised this separately to meteor forum, see how it will go. |
Are you using the normal install or the 2-repo install? |
@SachaG Normal Install |
I just did some more research on this topic:
It could be one of those babel / ecmascript packages: meteor:ecmascript Maybe related to https://github.com/meteor/meteor/blob/devel/History.md#v1611-2018-04-02 changes to @babel/runtime |
Same problem with me on MacOS High Sierra |
I've only tested Vulcan with Meteor 1.6.1. Can you try downgrading? |
My current version of Meteor is 1.6.1 |
This will fix the above errors (basically a bump of npm packages + meteor 1.6.1.1 upgrade, i think the one that matters is the babel runtime one): https://gist.github.com/pozylon/2f42567ecdc47ad7cb1e64012d7c5a69 |
Thanks @pozylon it solved the issue |
Just pushed an update, let me know. |
Thanks, the last update solved the problem. Also, the Modal in step 4 is showing now. |
Hello everyone, with the latest pull the getting-started able to start with only one warning which is fine. But example-instagram still didnt work for me, with the following from the console and blank page show up. Do i need to downgrade the node?
or any package missing?
|
when you switch between examples : meteor reset, meteor npm install, meteor --settings settings.json |
Thanks a lot. it all about the node version 10.0.0 is not compatible and all good now once downgraded to Node 8.11.1 and added vulcan:ui-bootstrap to packages file. https://forums.meteor.com/t/is-it-problem-with-meteor-or-vulcanjs-or-something-else/43568/5 |
Vulcan-Starter example-instagram cannot be loaded and it seem to be caused by runtime error on Chrome as below.
With
Meteor 1.6.1
Node v10.0.0
Npm 5.6.0
As the result, the page cannot be loaded properly and picture cannot be loaded as below.
Hope someone could help with this.
The text was updated successfully, but these errors were encountered: