Electron 4 is having ~/.node-gyp cache collisions
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 10.7k
- Forks
- 1.9k
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 5
Description
When rebuilding a module for Electron 4, the compiles began to fail by saying that node_api.h was not found.
It appears that the ~/.node-gyp folder had a 4.0.0 subfolder for node v4. Electron v4 was colliding with that node-4 folder. The solution was to delete the ~/.node-gyp/4.0.0` folder and install again.
Any ideas on how to handle the collision?
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
Start by reproducing the Electron 4 rebuild failure with an existing ~/.node-gyp/4.0.0 directory and compare it with the Node 4 cache described in the report. Trace how node-gyp selects cache directories for these versions. Done means Electron 4 and Node 4 no longer collide and the native module rebuild finds node_api.h without manually deleting the cache.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- electron, node.js
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100