GregoryCannon / GregoryCannon/StackRabbit
Stuck on installation
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 462
- Forks
- 50
- PR merge metrics
- No merged PRs in 30d
Description
Im have tried to get this going, and have been able to debug some of the issues but I am stuck at the following errors:
gyp ERR! build error
gyp ERR! stack Error: C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Current\Bin\MSBuild.exe failed with exit code: 1
gyp ERR! stack at ChildProcess. (C:\Users\maket\node_modules\node-gyp\lib\build.js:219:23)
gyp ERR! stack at ChildProcess.emit (node:events:524:28)
gyp ERR! stack at ChildProcess._handle.onexit (node:internal/child_process:293:12)
gyp ERR! System Windows_NT 10.0.19045
gyp ERR! command "C:\Program Files\nodejs\node.exe" "C:\Users\maket\node_modules\node-gyp\bin\node-gyp.js" "build"
gyp ERR! cwd C:\Users\maket\Desktop\StackRabbit\StackRabbit-master
gyp ERR! node -v v20.19.3
gyp ERR! node-gyp -v v11.2.0
gyp ERR! not ok
It looks to me like the MSBuild.exe is causing this issue and items are not coming together... my kid is 5 and obsessed with Tetris, and the stackrabbit 102Million video in particular. I may have overpromised him here LOL
any quick solves to this? I am running the node.js 20, but this error occurred with 22 as well.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the installation on Windows with Node.js 20 and 22, then inspect the node-gyp output at node_modules/node-gyp/lib/build.js and the MSBuild.exe failure. The issue names no project file or test, so first identify which dependency invokes node-gyp in the StackRabbit checkout. Done means a documented installation path or a narrowed, reproducible cause.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, node.js
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100