Segfault error when building
Hey @lab, I've had this error for the past 2 days.
I did some digging and it looks like it's because of a dependency in parcel (lmdb). Here is a post that I think is related to the issue https://github.com/parcel-bundler/parcel/issues/7702
I'm unable to run, dev, build or publish. The error seemingly happened out of the blue. Can you provide any help.
I'm running this on an M2 Macbook Air if that helps
GitHub
Parcel 2.3.1, unknown reason segmentation fault on first build on m...
π bug report π Configuration (.babelrc, package.json, cli command) platform: node 17.5.0 aarch64, macos 12.2 apple m1 package.json: { "private": true, "source": "src/index....
5 Replies
The only way this can be debugged IMO, is to remove some package you're importing and see which one's causing the issue
I was just able to fix this and as suspected, it's because of Parcel. I cloned the plasmo repo and built it locally. Then I downgraded all parcel versions to 2.8.3 (from 10 months ago).
After a bit more finnagling with my repo, I was able to get it to build again.
For now, I'll keep developing with my local version of plasmo, but in the future is a fix possible, either through a downgrade of parcel or some other workaround?
This is tricky...
the latest parcel version fixed some issue, and also caused this issue due to the use of the new resolver...
One way to override parcel core is to do this: https://github.com/PlasmoHQ/plasmo/issues/661#issuecomment-1669759831
GitHub
"Could not resolve bundle with id" [BUG] Β· Issue #661 Β· PlasmoHQ/p...
What happened? A bug happened! I've built an extension, and I'm getting this error when running the extension - "Could not resolve bundle with id" Version Latest What OS are you s...
4 months after, but thank you for this fix! I used overrides (i use pnpm) to solve this.
Here are the overrides I had to use