v4
v4 copied to clipboard
failing to install and build
make: *** [Release/obj.target/lmdb/src/node-lmdb.o] Error 1
gyp ERR! build error
gyp ERR! stack Error: make
failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/Users/shikhargupta/.nvm/versions/node/v20.2.0/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:203:23)
gyp ERR! stack at ChildProcess.emit (node:events:511:28)
gyp ERR! stack at ChildProcess._handle.onexit (node:internal/child_process:293:12)
gyp ERR! System Darwin 22.4.0
gyp ERR! command "/Users/shikhargupta/.nvm/versions/node/v20.2.0/bin/node" "/Users/shikhargupta/.nvm/versions/node/v20.2.0/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /Users/shikhargupta/Desktop/GitHub/chandrikadeb7.github.io/node_modules/lmdb-store
ERROR UNKNOWN No native build was found for platform=darwin arch=arm64 runtime=node abi=115 uv=1 armv=8 libc=glibc node=20.2.0 loaded from: /Users/shikhargupta/Desktop/GitHub/chandrikadeb7.github.io/node_modules/lmdb-store Error: No native build was found for platform=darwin arch=arm64 runtime=node abi=115 uv=1 armv=8 libc=glibc node=20.2.0 loaded from: /Users/shikhargupta/Desktop/GitHub/chandrikadeb7.github.io/node_modules/lmdb-store
Did you solve this issue? If yes, how?
This: npm install --force will resolve your issue.
Steps I took:
- Deleted the cloned project as I have messed a lot of things up.
- Cloned it from github again
- Deleted the yarn.lock file
- Run npm install -g gatsby-cli
- npm install --force
- npm start I was then able to view v4 project in my browser on using http://localhost:8000/
- Installed zip folder to clone repository. (tried github desktop and git clone through terminal but did not work for me)
- delete yarn.lock file
- Run npm install -g gatsby-cli
- npm install --force (ensure that you stable internet connection)
- npm start --> project start on localhost port 8000
@Edamijueda Solutions is Great. Finally able to run this repo, after long thrashing of playing with npm versions and modules. There is a warning, about "Memory Leak", anything to worry about??
@Edamijueda Solutions is Great. Finally able to run this repo, after long thrashing of playing with npm versions and modules. There is a warning, about "Memory Leak", anything to worry about??
I am happy to hear that ur issue was solved. Nothing to worry about. I have been using this for some time now. No code breaking.