Closed moseke closed 6 years ago
@moseke did you delete node_modules
and run npm install
?
I did @colin-marshall and this is the output:
7ndevw1014:big-toy-1-0-1 me$ npm install
> foundationpress@1.0.1 postinstall /Users/me/Desktop/big-toy-1-0-1
> bower install && gulp build
module.js:529
throw err;
^
Error: Cannot find module 'internal/errors'
at Function.Module._resolveFilename (module.js:527:15)
at Function.Module._load (module.js:476:23)
at Module.require (module.js:568:17)
at require (internal/module.js:11:18)
at evalmachine.<anonymous>:36:16
at Object.<anonymous> (/Users/me/Desktop/big-toy-1-0-1/node_modules/bower/node_modules/graceful-fs/fs.js:11:1)
at Module._compile (module.js:624:30)
at Object.Module._extensions..js (module.js:635:10)
at Module.load (module.js:545:32)
at tryModuleLoad (module.js:508:12)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! foundationpress@1.0.1 postinstall: `bower install && gulp build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the foundationpress@1.0.1 postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/me/.npm/_logs/2017-10-24T22_56_29_616Z-debug.log
7ndevw1014:big-toy-1-0-1 me$
Could be your node version - try using v6.11.x
From Requirements - "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."
@FlatspinZA may be correct. I pulled up an older version of FoundationPress last week and had to revert back to Node 5.5 because that's what I knew it was working on before. @moseke you should find out what Node version the other developer is using, and switch to that version using nvm. Then make sure you do rm -rf node_modules
and npm install
again.
@moseke Any luck after following the advice of @FlatspinZA and @colin-marshall ? To find out what version of node you're using, type node -v
in your terminal.
I had exactly the same problem after having done a clean install of my PC, and trying to get an older version of FoundationPress running.
Since I built my site on Node v4-something, I was getting errors during npm run watch
.
Luckily some clever bugger (in the errors) told be to rebuild SASS to bind it to the newer version of Node (v6.11.x - since I remembered the "bleeding edge" warning).
Not sure how it is on MAC/Linux, but on Windows - npm rebuild node-sass
@FlatspinZA I think you're right and this is directly related to #1148.
@moseke did you try to build the theme in any other way besides the package task? Like npm run start
?
Sorry @colin-marshall and @olefredrik, apparently I only sign in when I'm in trouble so I didn't see your messages.
We were in a time crunch and just rebuilt the theme using a newer version.
As always, thank you for your excellent support and wonderful product. XOXO
No problem @moseke! Closing this out.
Mac OS: 10.12.6 Node: 8.7.0 FP: 2.9 Foundation: 6.2.3
Trying to package an older version of FP that came from another developer.
Error log:
The other devoper can run run NPM commands with no issues. I've tried pulling on different threads here and I just can't resolve this. How would you recommend interpretting and solving this problem?