parcel: @parcel/cache: EPERM: operation not permitted, rename
š bug report
I get an error when using the latest @nightly that I donāt get using the @next.
Strangely Parcel goes ahead and builds anyway so Iām not quite sure what this is about. Both files mentioned in the error exist, so it maybe fails to rename and copies instead?
It isnāt 100% repeatable - exactly once it succeeded without the error - race condition?
š Configuration (.babelrc, package.json, cli command)
rm -rf .parcel-cache/* dist/* && parcel build --no-source-maps *.html src/**/*.html
š¤ Expected Behavior
No error.
šÆ Current Behavior
@parcel/cache: EPERM: operation not permitted, rename 'E:codewebreaction-web.parcel-cache4b8ca9278422d5f7bdd56853b2d8203c.v8.26532.0.1' -> 'E:codewebreaction-web.parcel-cache4b8ca9278422d5f7bdd56853b2d8203c.v8'
Error: EPERM: operation not permitted, rename 'E:\code\web\reaction-web\.parcel-cache\4b\8ca9278422d5f7bdd56853b2d8203c.v8.26532.0.1' -> 'E:\code\web\reaction-web\.parcel-cache\4b\8ca9278422d5f7bdd56853b2d8203c.v8'
š Your Environment
| Software | Version(s) |
|---|---|
| Parcel | 2.0.0-nightly.370 |
| Node | 14.4.0 |
| npm | 6.14.5 |
| Operating System | Windows 10 |
Running the command in git-bash hosted inside vs-code.
Iām afraid Iām not quite sure what to include to help debug this one without copying across my entire project. Let me know if you want anything specific or something testing.
About this issue
- Original URL
- State: open
- Created 4 years ago
- Reactions: 8
- Comments: 37 (5 by maintainers)
Commits related to this issue
- Downgrade parcel See https://github.com/parcel-bundler/parcel/issues/5036#issuecomment-706249105 — committed to alpha-tango-kilo/Siphon by alpha-tango-kilo 3 years ago
Reverting back to
nightly-286fixes the problem. I constantly tried to update to newer nightlies, but286was the last one that is still working fine for my project.Sorry for the late response. I can indeed reproduce it with https://github.com/parcel-bundler/parcel/issues/5036#issuecomment-815808270
I want to mention that I get this error even though I build with
--no-cache:parcel build src/index.html --no-cache --no-scope-hoist --no-source-mapsThis is still a problem. Iām on Win 10, too. āparcelā: ā^2.0.0-rc.0ā, Running āstartā: āparcel --no-cacheā, which is ignored it seems It seems like the cache gets locked when the server is running so it canāt write to it or change names. If I stop the server, delete the cache and then start the server again, it will work for a few saves before throwing the error again.
I have been getting this error ever since I updated Parcel. The old version has over 54 vulnerabilities from moderate to high.
Iām having this error as well, itās annoying. Probably Iām going to change my bundler choiceā¦
@SCLeoX: Other than that itās promoted as āproduction readyā, āgets more frequent updatesā and āis generally betterā? No not really. I guess so.