-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
parcel watch error: Expected content key 2d39cdf7c618ab5b to exist #8874
Comments
I'm also experiencing this issue, but it's also on my I've also tried 2.8.2 and same result. When I tried to revert back to the version I was using, 2.7.0, I started getting a new error:
I've yet to find a way around this issue. EDIT: Just now found a way around it. I reverted to 2.7.0 again and found where the error in reverting before was. I hadn't explicitly installed |
Update: I also hadn't explicitly installed |
For me it worked when I deleted the .parcel-cache and dist folders completely in the root directory and did the rebuild. |
delete the .parcel-cache folder, then try running command again, it'll work. |
error: Expected content key de1e4a02ec63c4eb to exist |
This fixed it for me. |
This worked for me |
Same error occurred to me in parcel version - 2.9.3 |
this worked for me |
This worked for me . Thank you |
I just deleted the .parcel-cache and dist folders completely from the root directory and rebuild the applicate, it did worked for me |
this helped me..thanks |
Thanks, I deleted both the dist and cache, and now it works. It accidentally deleted the dist first so you probably won't have to. But thanks for the solution. I haven't worked with a dist before so appreciate your post. |
its working✨ |
Error: Expected content key de1e4a02ec63c4eb to exist Error: Expected content key de1e4a02ec63c4eb to exist |
|
I am getting the same error |
This worked for me too. Thank you |
Deleting .parcel-cache works for me until I change the HTML node structure in any way, then the problem returns. I'm changing elements all the time so this fix isn't really valid for me. Anyone else got this? |
It work for me . |
Yeah,after deleting .parcel-cache folder and run command again .It's working for me |
Nice |
Right, deleting of |
Yep, this did it for me as well! |
Worked for me, using parcel version 2.10.3 |
yes deleting .parcel-cache worked for me |
after closing the server and solved the problem! |
|
This is what I'm experiencing too. I can edit one of my JavaScript files over and over without this error occurring. I can even edit inside a |
delete parcel-cache and dist folder then restart your using npx parcel index.html |
It's been well over a year since this was reported, and there is still no real solution except the half-assed workaround repeatedly mentioned in the previous ~25 useless comments (kudos on that guys /s). |
using "rm -rf .parcel-cache" command to remove the "parcel cache" worked for me |
this worked ! |
@itzmk06 oh wow, what do you know .. the same thing >20 people already said above turned out to be true. /s |
I'm using pacel
I have tried removing
The issue gone.
It works. Looks like there is something wrong with |
Any update? |
🐛 bug report
When running
parcel watch 'packages/*' --no-cache
I'm getting the following errors:Running
parcel build 'packages/*' --no-cache
builds fine with no errors.Downgrading to parcel 2.8.2 didn't fix this, as suggested in #8787
Deleting
.parcel-cache
also didn't work.🎛 Configuration (.babelrc, package.json, cli command)
🤔 Expected Behavior
Running
parcel watch 'packages/*' --no-cache
should build with no errors, just asparcel build 'packages/*' --no-cache
does.😯 Current Behavior
Seeing the errors mentioned above.
💁 Possible Solution
Update: adding the
--no-hmr
parameter toparcel watch
made the errors go away🔦 Context
💻 Code Sample
Here is the repo where I am running into this issue:
https://github.com/reservoirprotocol/reservoir-kit/tree/ted/upgrade-typescript-solution
🌍 Your Environment
The text was updated successfully, but these errors were encountered: