ENOENT: no such file or directory, open
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 46
- Forks
- 9
- Avg merge
- 8h 52m
- Merged PRs (30d)
- 4
Description
My suspicion is that an optimistically versioned sub-dependency has been updated that's causing this type of error when npm install is run:
npm WARN tar ENOENT: no such file or directory, open '/home/guy/source/learn/node_modules/.staging/write-fbead8e4/package.json'
npm WARN tar ENOENT: no such file or directory, open '/home/guy/source/learn/node_modules/.staging/istanbul-api-0b85c24d/package.json'
npm WARN tar ENOENT: no such file or directory, open '/home/guy/source/learn/node_modules/.staging/write-fbead8e4/README.md'
npm WARN tar ENOENT: no such file or directory, open '/home/guy/source/learn/node_modules/.staging/istanbul-api-0b85c24d/CHANGELOG.md'
npm WARN tar ENOENT: no such file or directory, open '/home/guy/source/learn/node_modules/.staging/write-fbead8e4/LICENSE'
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 failure with npm install and inspect the dependency installation output shown in the issue. Identify which dependency update causes the missing files under node_modules/.staging, then verify that npm install completes without the ENOENT warnings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100