POC: Use Parcel - #5014
Conversation
704888e to
583b80c
Compare
| { | ||
| "mangle": false, | ||
| "format": { | ||
| "beautify": true, |
There was a problem hiding this comment.
I'm not sure why this isn't being followed, I think it worked in previous Parcel betas. Not fundamental though.
|
Out of curiosity, what are the advantages of using Parcel over Webpack in our case? |
|
No config. We also have a dependency that we can't update because it's broken (size-plugin) |
|
Maybe for Parcel 3 |
|
Latest error: which basically means Parcel is not loading it as a module after transpiling it. |
|
Sounds like you expect that Parcel transpiles plugins automatically/transparently? It doesn't. You have to ensure yourself that |
|
Thanks for the comment! Indeed that's the issue. Maybe as a quick patch (without adding a whole build to this transformer) I can find an const {getFeatures, getFeaturesMeta} = await import("../../build/readme-parser.ts"); |
|
Still blocked by Will pick it up again once that's resolved somehow |
Annual attempt at migrating to Parcel
Blocked by:
Usepackage.json#exportsmap parcel-bundler/parcel#4155Bundles must have unique nameshas no context, like many other errors parcel-bundler/parcel#7255Missing (help wanted)
getFeatureName(import.meta.url)to replace__basefilenameverify-features.tsneeds to be updated to look for CSS features inrefined-github.cssinstead