WARN rollback Rolling back node-pre-gyp@0.12.0 failed
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 271
- Avg merge
- 23h 40m
- Merged PRs (30d)
- 2
Description
Hello? Guys
Can you give me any info about warning when I use "npm i" command:
npm WARN rollback Rolling back node-pre-gyp@0.12.0 failed (this is probably harmless): EPERM: operation not permitted, scandir '...\node_modules\fsevents\node_modules'
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 warning with npm i on the affected Windows setup, focusing on the rollback of node-pre-gyp@0.12.0 and the EPERM scandir error under fsevents. Determine whether the warning is caused by node-pre-gyp or a dependency, then document or validate a fix that prevents the warning or clearly confirms it is harmless.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100