GregoryCannon / GregoryCannon/StackRabbit
NPM I and Start NPM
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 462
- Forks
- 50
- PR merge metrics
- No merged PRs in 30d
Description
Hi all!
After reading the issues others have had with StackRabbit NPM, downgrading Node to 20, letting it install all its dependencies, etc., I cannot get this thing to start.
It goes through several lines of GYP, then when it gets to "module.cpp", things go haywire.
All LUA scripts are in the proper folders. luaScripts (pre-created folder for FCEUX) as well as created LUA folder, per the guide.
Errors in Admin CMD are pasted, as are the errors where it says it's "not ok".
Also attaching the logfile from the command processor.
PC: W11H x64, Core i7 11700k, 64gb RAM, 4060 8GB GPU. Node.js 20.20.0 LTS; Python3.
If any other info is needed please request and I'll be happy to provide. :)
Thank you!
2026-05-06T02_42_21_795Z-debug-0.log
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 with the attached npm debug log and the module.cpp build failure, then reproduce the install/start sequence on Windows 11 with Node.js 20.20.0 and Python 3. Check the NPM and native-module setup before considering the Lua folders. Done means dependencies install without the GYP/module.cpp errors and StackRabbit starts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, lua, node.js, python
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100