Closed MattWilcox closed 2 years ago
MattWilcox
commented
3 years ago waaaait, does this require you to pick php8? I never use php8 as I can't deploy on it. Hold on, let me try that again.
Wait no, this would use my local machine's npm and not whatever's bundled in Nitro. Not that then.
mattstein
commented
3 years ago @MattWilcox From your example it looks like that might have been node 14.
Run
npm installwith node 12.19.0 or later. (If you’ve installed nvm runnvm use, thennpm install.)
This is using your local machine’s node/npm, and it should specifically be v12 which is easiest if you can get away with nvm use.
waaaait, does this require you to pick php8? I never use php8 as I can't deploy on it.
You should be able to get away with PHP 7.4 as well.
MattWilcox
commented
3 years ago Sooo, node 14 is not later than node 12? They are considered different things? Ok, will go delve into nvm then I guess, thanks!
God why is modern web dev such a huge cluster of redacted 🙄 Will try that later, but it's midnight now, thanks again!
mattstein
commented
3 years ago Sooo, node 14 is not later than node 12?
Sorry, I see how 14 is more than 12 and should probably clarify v12 at 12.19.0 or later. Let me know if all’s well once you have fresh energy for node adventures.
khalwat
commented
3 years ago You can try this one, too @MattWilcox -- it should "just work": https://github.com/nystudio107/spoke-and-chain
mattstein
commented
2 years ago You ever get this working, @MattWilcox?
MisterMike
commented
2 years ago Upon "npm i" I get a similar error as follows:
npm ERR! code 1
npm ERR! path /Users/mischa/Webcode/spokeandchain/node_modules/sharp
npm ERR! command failed
npm ERR! command sh -c (node install/libvips && node install/dll-copy && prebuild-install) || (node-gyp rebuild && node install/dll-copy)
npm ERR! TOUCH Release/obj.target/libvips-cpp.stamp
npm ERR! CXX(target) Release/obj.target/sharp/src/common.o
npm ERR! info sharp Downloading https://github.com/lovell/sharp-libvips/releases/download/v8.7.4/libvips-8.7.4-darwin-arm64v8.tar.gz
npm ERR! /Users/mischa/Webcode/spokeandchain/node_modules/sharp/install/libvips.js:86
npm ERR! throw new Error(`Status ${response.statusCode}`);
npm ERR! ^
npm ERR!
npm ERR! Error: Status 404
npm ERR! at /Users/mischa/Webcode/spokeandchain/node_modules/sharp/install/libvips.js:86:17
npm ERR! at f (/Users/mischa/Webcode/spokeandchain/node_modules/once/once.js:25:25)
npm ERR! at ClientRequest.<anonymous> (/Users/mischa/Webcode/spokeandchain/node_modules/simple-get/index.js:63:5)
npm ERR! at Object.onceWrapper (node:events:514:26)
npm ERR! at ClientRequest.emit (node:events:394:28)
npm ERR! at HTTPParser.parserOnIncomingClient [as onIncoming] (node:_http_client:621:27)
npm ERR! at HTTPParser.parserOnHeadersComplete (node:_http_common:128:17)
npm ERR! at TLSSocket.socketOnData (node:_http_client:487:22)
npm ERR! at TLSSocket.emit (node:events:394:28)
npm ERR! at addChunk (node:internal/streams/readable:312:12)
npm ERR! gyp info it worked if it ends with ok
npm ERR! gyp info using node-gyp@7.1.2
npm ERR! gyp info using node@16.5.0 | darwin | arm64Something (sharp) depends on libvips 8.7.4 which can't be found. Any chance this could be updated ?
mattstein
commented
2 years ago @MisterMike, are you using node 12?
❯ node --version
v12.19.0
❯ npm --version
6.14.8@mattstein thanks!
using 16.5 on Apple M1
➜ europa node -v
v16.5.0
➜ europa npm -v
7.19.1That’d be it then @MisterMike—you’ll need to use node 12 in this case. (If you’ve got nvm installed, nvm use and you should be all set.)
MisterMike
commented
2 years ago okay - thanks.
...node 12 ist quite slow on Rosetta :-)
nettum
commented
2 years ago Can confirm that I get the same error when npm install tries to build sharp using node 14 or node 16.
Would prefer to not use node 12 much longer as EOL in coming up about 1 month from now https://nodejs.org/en/about/releases/
nfourtythree
commented
2 years ago Hi all
The instructions for getting the development of the Spoke & Chain demo have been updated. We are now including the package-lock.json so as long as you are running node 12+ and npm 6+ you should be able to simply run npm ci to get all dependencies installed and be ready to go.
We certainly understand the point about those versions being outdated and it is something we have in the pipeline to get updated.
Closing this issue, thanks!
nettum
commented
9 months ago Actually still getting this error with node 16. Node 12 did work though.
MisterMike
commented
9 months ago Any plans to upgrade the toolset in order to have it work with the latest node/npm ?
Description
Following the steps as written, got it all installed via Nitro and then hit
npm installwhich output...