`Error: request for 'node:process' is not in cache`
Open
Nobody has claimed this yet.
loaders
stale
- Dominant language
- JavaScript
- Stars
- 122k
- Forks
- 37.3k
- Avg merge
- 4d 2h
- Merged PRs (30d)
- 283
Description
Node crashes with strange error.
Version
v20.11.1
Platform
Mac Os
Subsystem
node:process
What steps will reproduce the bug?
git clone https://github.com/coderaiser/cloudcmd
cd cloudcmd && git checkout feature/esm && npm i && npm test
How often does it reproduce? Is there a required condition?
Always
What is the expected behavior? Why is that the expected behavior?
Expected behavior: no crash
What do you see instead?
Additional information
No response
Contributor guide
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
Reproduce the crash by cloning cloudcmd, checking out feature/esm, installing dependencies, and running npm test on macOS with Node.js v20.11.1. Start by tracing the failure reported for the node:process subsystem; done means the same test command completes without the cache error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100