-
Notifications
You must be signed in to change notification settings - Fork 867
Install Errors #1330
Comments
Gulp version is stuck at 3.9. You need to explicitly say "gulp": "gulpjs/gulp#4.0" |
Thanks for the reply mattbag! When I leave package.json, line 42 as : "gulp": "gulp": "gulpjs/gulp#4.0", I get the following error with a hung Terminal ...
Also can you help me understand Gulp in this Foundaton/node.js context a bit more. The documentation here on Git and at https://foundationpress.olefredrik.com/posts/tutorials/foundationpress-for-beginners makes no mention of installing/reinstalling Gulp or how to update any part of it. Can you or anyone else provide Terminal commands for this? For now, I'll continuing reading about Gulp and try to figure this out. Should reinstalling node.js rebuild node-sass? I've tried several times now, but no luck. I've also tried, npm rebuild node-sass with no apparent effect. |
Can you add/show you package dependencies here? |
"This project requires Node.js v4.x.x to v6.11.x to be installed on your machine. Please be aware that you might encounter problems with the installation if you are using the most current Node version (bleeding edge) with all the latest features." |
Yep. I run it on 8 and now 10, it's just a matter of updating the right pkgs |
I thought I had more updates, but only gulp-sass on this one. |
Thanks mattbag! I'm using node.js v10:13.0, which is the lesser of the two pkg options offered at nodejs.org, so not the bleeding edge version. After adding your list of devDependancies to the package.json file, the npm install still stalled ...
So, once again, I used your devDependancies above but edited "gulp": "gulpjs/gulp#4.0" to "gulp": "^4.0" and this time npm install runs with the following results, which seem better than I started with yesterday--still lots of errors but I seem to get a successful build at the end. I've never done this before so I'm still not sure if the theme is ready to use. I'll have to test it tomorrow.
But thanks again, mattbag! I think I'm beginning to understand the idea of devDependencies array. I'll start Googling this subject and see if I can find more updated packages for node 10.13 |
Hi FlatspinZA, thanks for the tip! I did read that about the project requiring Node.js v4.x.x to v6.11.x earlier, but the link above that to nodejs.org only offers 10.13.0 or 11.1.0, so I took the lesser. The site seems to have some earlier versions but they don't come in the installer packages, so I haven't been able to figure out how to install 6.11 |
Hi @lenrooney, here you go: https://nodejs.org/download/release/v6.11.5/ |
Hi @dgobnto, thanks for that! I wish the instructions had provided this node.js link to begin with. I gave up a few days ago and installed JointsWP instead. It installed with node 10.13 without any problems and, so far, seems to deploy all the Foundation features. It was a work around because I really wanted to try FoundationPress--it seems like the best supported option--but I had to get on with a project at hand. I might circle back to FoundationPress later on. Thanks again, everyone, for all the help! |
Hi All,
I'm a complete Foundation/FoundationPress, node, sass noob, but it looks great and I want to get started. So I come here and follow the Quickstart Guide. I've been at it for many, many, hours now, trying it over and over again, going through all the similar Issues listed here, but still no luck. At first, the install would just fail and freeze up the Terminal, but then I discovered the package.json, line 42: "gulp": "^4.0" fix that seemed to get the installer to run fully, but reports a failed build with numerous errors. I have no clue what to try next at this point and I'm hoping someone out there can help me make sense of what's going on and what steps I can take to get FoundationPress working correctly on my Mac. Thanks!
How can this bug be reproduced?
What did you expect to happen?
An error free install
What happened instead?
Please List the Following:
node_modules/foundation-sites/package.json
) :6.4.3The text was updated successfully, but these errors were encountered: