Skip to content
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

Closed
ghost opened this issue May 5, 2018 · 22 comments
Closed

Vulcan-Starter with errors on Chrome for example-instagram #55

ghost opened this issue May 5, 2018 · 22 comments

Comments

@ghost
Copy link

ghost commented May 5, 2018

Vulcan-Starter example-instagram cannot be loaded and it seem to be caused by runtime error on Chrome as below.

screen shot 2018-05-05 at 11 08 05

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.

screen shot 2018-05-05 at 11 12 40

Hope someone could help with this.

@pozylon
Copy link

pozylon commented May 7, 2018

Same here, could not fix it yet

@ghost
Copy link
Author

ghost commented May 8, 2018

Maybe the team is still looking at it, give them a few more days or I have to switch to use other framework. Sigh.

@SachaG
Copy link
Contributor

SachaG commented May 8, 2018

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:

  • git pull to get the latest changes
  • meteor reset to reset the project
  • delete node_modules and then npm install again to reset node packages.

Let me know if this works!

@pozylon
Copy link

pozylon commented May 8, 2018

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
Meteor 1.6.1
Node v8.11.1
NPM v6

@ghost
Copy link
Author

ghost commented May 8, 2018

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.....

@ghost
Copy link
Author

ghost commented May 8, 2018

I have raised this separately to meteor forum, see how it will go.
https://forums.meteor.com/t/is-it-problem-with-meteor-or-vulcanjs-or-something-else/43568

@SachaG
Copy link
Contributor

SachaG commented May 8, 2018

Are you using the normal install or the 2-repo install?

@pozylon
Copy link

pozylon commented May 8, 2018

@SachaG Normal Install

@pozylon
Copy link

pozylon commented May 8, 2018

I just did some more research on this topic:

  • The errors are browser-independent
  • _this._launchConnection is referenced and this.launchConnection exists in the uncompiled version and cannot be unreferenced, but it seems like the compiled file is somehow corrupt

It could be one of those babel / ecmascript packages:

meteor:ecmascript
meteor:ecmascript-runtime-client
@babel/runtime

Maybe related to https://github.com/meteor/meteor/blob/devel/History.md#v1611-2018-04-02 changes to @babel/runtime

@lc3t35
Copy link

lc3t35 commented May 8, 2018

no error for me OSX 10.12.6, meteor 1.6.1, node v8.9.4, npm 5.6.0, chrome 66.0.3359.139, FF 59.0.2
capture d ecran 2018-05-08 a 11 38 33
2-repo install,

meteor list
accounts-password    1.5.1  Password support for accounts                       
example-instagram    0.0.0+
vulcan:core          1.10.0  Vulcan core package
vulcan:debug         1.10.0  Vulcan debug package
vulcan:i18n-en-us    1.10.0  Vulcan i18n package (en_US)
vulcan:i18n-fr-fr    1.10.0  Vulcan i18n package (fr_FR)
vulcan:ui-bootstrap  1.10.0  Vulcan Bootstrap UI components.

can you downgrade node to v8.9.4 to match meteor's node version ?

@lc3t35
Copy link

lc3t35 commented May 8, 2018

https://forums.meteor.com/t/upgraded-to-1-6-1-1-now-getting-all-kinds-of-console-errors/43462

@AlABarazi
Copy link

Same problem with me on MacOS High Sierra

@SachaG
Copy link
Contributor

SachaG commented May 8, 2018

I've only tested Vulcan with Meteor 1.6.1. Can you try downgrading?

@AlABarazi
Copy link

My current version of Meteor is 1.6.1

@pozylon
Copy link

pozylon commented May 8, 2018

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

@vipinlahoti
Copy link

Thanks @pozylon it solved the issue

@SachaG
Copy link
Contributor

SachaG commented May 8, 2018

Just pushed an update, let me know.

@ghost
Copy link
Author

ghost commented May 9, 2018

Thanks @pozylon and @SachaG , Just need to git pull Vulcan-starter for latest master and it should do the magic without downgrading node or meteor?

@AlABarazi
Copy link

Thanks, the last update solved the problem. Also, the Modal in step 4 is showing now.

@ghost
Copy link
Author

ghost commented May 9, 2018

Hello everyone, with the latest pull the getting-started able to start with only one warning which is fine.

screen shot 2018-05-10 at 12 12 37

But example-instagram still didnt work for me, with the following from the console and blank page show up.

screen shot 2018-05-10 at 12 15 42

Do i need to downgrade the node?

Meteor 1.6.1.1
Node v10.0.0
Npm 5.6.0

or any package missing?

meteor list
accounts-password  1.5.1  Password support for accounts
example-instagram  0.0.0+
vulcan:core        1.10.0  Vulcan core package
vulcan:i18n-en-us  1.10.0  Vulcan i18n package 

@pozylon @SachaG @lc3t35 able to shed some light please?

@lc3t35
Copy link

lc3t35 commented May 9, 2018

when you switch between examples : meteor reset, meteor npm install, meteor --settings settings.json
don't forget to add METEOR_PACKAGE_DIRS before commands if it's a 2 repo install.

@ghost
Copy link
Author

ghost commented May 11, 2018

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

@ghost ghost closed this as completed May 11, 2018
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants