Vulcan-Starter (interactive tutorial) problems
See original GitHub issueHi, It appears there are some issues with the Vulcan-Starter (interactive tutorial).
Vulcan version: 1.12.15
at makeMissingError (modules-runtime.js?hash=d3c3e5d67c95f97a60888bda7373292efad3be5e:232)
at Module.require (modules-runtime.js?hash=d3c3e5d67c95f97a60888bda7373292efad3be5e:251)
at require (modules-runtime.js?hash=d3c3e5d67c95f97a60888bda7373292efad3be5e:268)
at modules.js?hash=7217d936601ef3fa3a7336fdbab34b93ec776bf1:87420
at mingo.js (modules.js?hash=7217d936601ef3fa3a7336fdbab34b93ec776bf1:89692)
at fileEvaluate (modules-runtime.js?hash=d3c3e5d67c95f97a60888bda7373292efad3be5e:346)
at Module.require (modules-runtime.js?hash=d3c3e5d67c95f97a60888bda7373292efad3be5e:248)
at Module.moduleLink [as link] (modules.js?hash=7217d936601ef3fa3a7336fdbab34b93ec776bf1:313)
at mongo_redux.js (mongo_redux.js:1)
at fileEvaluate (modules-runtime.js?hash=d3c3e5d67c95f97a60888bda7373292efad3be5e:346)
vulcan_i18n.js?hash=e2f34edb6ea8d7b900e7279bb473c41d6070dbde:17 Uncaught TypeError: Cannot read property 'Vulcan' of undefined
at vulcan_i18n.js?hash=e2f34edb6ea8d7b900e7279bb473c41d6070dbde:17
at vulcan_i18n.js?hash=e2f34edb6ea8d7b900e7279bb473c41d6070dbde:335
vulcan_users.js?hash=65c9008d2dd75f7b7ddd33b66dfaec88c6a17530:17 Uncaught TypeError: Cannot read property 'Vulcan' of undefined
at vulcan_users.js?hash=65c9008d2dd75f7b7ddd33b66dfaec88c6a17530:17
at vulcan_users.js?hash=65c9008d2dd75f7b7ddd33b66dfaec88c6a17530:2021
vulcan_routing.js?hash=6b10525c42dfc148f110095d93ea00307d151714:17 Uncaught TypeError: Cannot read property 'Vulcan' of undefined
at vulcan_routing.js?hash=6b10525c42dfc148f110095d93ea00307d151714:17
at vulcan_routing.js?hash=6b10525c42dfc148f110095d93ea00307d151714:370
vulcan_email.js?hash=5046af735db44b7dae54542e2297f37f18722c80:17 Uncaught TypeError: Cannot read property 'Vulcan' of undefined
at vulcan_email.js?hash=5046af735db44b7dae54542e2297f37f18722c80:17
at vulcan_email.js?hash=5046af735db44b7dae54542e2297f37f18722c80:86
vulcan_debug.js?hash=1bb482348102995823c066c6bb2d6b3947f0d9ec:17 Uncaught TypeError: Cannot read property 'Vulcan' of undefined
at vulcan_debug.js?hash=1bb482348102995823c066c6bb2d6b3947f0d9ec:17
at vulcan_debug.js?hash=1bb482348102995823c066c6bb2d6b3947f0d9ec:1080
vulcan_core.js?hash=9f6a12c47efeda355b3441872a47d2de5eb7fb5c:17 Uncaught TypeError: Cannot read property 'Vulcan' of undefined
at vulcan_core.js?hash=9f6a12c47efeda355b3441872a47d2de5eb7fb5c:17
at vulcan_core.js?hash=9f6a12c47efeda355b3441872a47d2de5eb7fb5c:5178
vulcan_i18n-en-us.js?hash=6d386d5c63f31daf472389a847fc00a0e8aae39b:17 Uncaught TypeError: Cannot read property 'Vulcan' of undefined
at vulcan_i18n-en-us.js?hash=6d386d5c63f31daf472389a847fc00a0e8aae39b:17
at vulcan_i18n-en-us.js?hash=6d386d5c63f31daf472389a847fc00a0e8aae39b:210
vulcan_forms.js?hash=951a7b9c457cb8e992925fc2394cd3a159f61dbd:17 Uncaught TypeError: Cannot read property 'Vulcan' of undefined
at vulcan_forms.js?hash=951a7b9c457cb8e992925fc2394cd3a159f61dbd:17
at vulcan_forms.js?hash=951a7b9c457cb8e992925fc2394cd3a159f61dbd:3918
vulcan_accounts.js?hash=65a7f6752e032e9be0b3dfed3f3fe7c253e27991:26 Uncaught TypeError: Cannot read property 'Vulcan' of undefined
at vulcan_accounts.js?hash=65a7f6752e032e9be0b3dfed3f3fe7c253e27991:26
at vulcan_accounts.js?hash=65a7f6752e032e9be0b3dfed3f3fe7c253e27991:3038
vulcan_ui-bootstrap.js?hash=ebe510bc5556f9ba2b087cfd8e9014f35c276a5d:17 Uncaught TypeError: Cannot read property 'Vulcan' of undefined
at vulcan_ui-bootstrap.js?hash=ebe510bc5556f9ba2b087cfd8e9014f35c276a5d:17
at vulcan_ui-bootstrap.js?hash=ebe510bc5556f9ba2b087cfd8e9014f35c276a5d:2172
getting-started.js?hash=45a6f81b7688222ae059e1a8dd8a96874b36b269:17 Uncaught TypeError: Cannot read property 'Vulcan' of undefined
at getting-started.js?hash=45a6f81b7688222ae059e1a8dd8a96874b36b269:17
at getting-started.js?hash=45a6f81b7688222ae059e1a8dd8a96874b36b269:2470
global-imports.js?hash=351158ef63888483286028f1e2d032137c5eea34:3 Uncaught TypeError: Cannot read property 'Vulcan' of undefined
at global-imports.js?hash=351158ef63888483286028f1e2d032137c5eea34:3`
1) I getting this console error on a fresh installation of git clone git@github.com:VulcanJS/Vulcan-Starter.git
2) In step 4. Core Components, Click Me link is not working
3) on Step 13. User Accounts: the bottons Sign up and Forgot password dosen’t works
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Components not working · Issue #115 · VulcanJS/Vulcan-Starter
Hi, there. All the pre-defined components are not working (no error message), such as SmartForm and AccountsLoginForm. (Version: 1.12.16)
Read more >Hello. I have a starting button problem?
My error I have is that my Vulcan 800 Classic won't start unless jump the starter solenoid with a screw driver. I did...
Read more >Kawasaki Vulcan S650 No Start! Starter switch problems
The starter button was not working on my vulcan do I took it apart to investigate and got it working again.
Read more >Read Me | Vulcan Docs
Clone the main VulcanJS repo locally (for example, to ~/Vulcan ). Create a new Meteor project or clone the Vulcan starter repo (this...
Read more >Kawasaki Vulcan Problems: 6 Known Issues (Explained)
The Vulcan S model from Kawasaki packs a considerable punch. ... In this article, we'll be going through some of the problems experienced...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Exact same issue as above, however I took a different approach to resolve the issue. I am trying to only support 1 Module manager and trying to keep it npm.
node_modules
directory and thepackage-lock.json
file.npm install
I was having the same issue and @SachaG’s comment resolved it.
To expand a little on the steps in case it’s helpful:
node_modules
folder.ctrl
+c
in your terminal (so the app stops trying to rebuild)yarn
in your terminal (orbrew install yarn
thenyarn
if you don’t have it already)My step 4 was to then run
yarn start
, but what I don’t know is if this needs to be the case going forward (vs. NPM).