You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to update the Parcel version in my extension Rango. Parcel versions up to 2.8.3 work fine but starting with 2.9.0 the bundle produced doesn't work when packaged in a Safari extension. The bundles produced for Firefox and Chrome work fine, though.
If I remove the variable tZ and replace the return statement with return e that problem goes away. The same happens if I run parcel with the flag --no-optimize.
But then I get another error:
Error: Could not resolve bundle with id jkYZu
Searching in the bundle for that identifier this is the only place it appears:
david-tejada
changed the title
Parcel v2.9.0 - v2.12.0 produce invalid bundle when packaged in a Safari extension
Parcel v2.9.0 - v2.12.0 with SWC minifier produce invalid bundle when packaged in a Safari extension
Oct 5, 2024
🐛 bug report
I am trying to update the Parcel version in my extension Rango. Parcel versions up to 2.8.3 work fine but starting with 2.9.0 the bundle produced doesn't work when packaged in a Safari extension. The bundles produced for Firefox and Chrome work fine, though.
🎛 Configuration (.babelrc, package.json, cli command)
.parcelrc
package.json
tsconfig.json
🤔 Expected Behavior
The produced bundle should work for creating a Safari extension.
😯 Current Behavior
There seems to be two problems here:
The first error I get is:
The error happens at this point in the bundle:
That variable is used here:
If I remove the variable
tZ
and replace the return statement withreturn e
that problem goes away. The same happens if I run parcel with the flag--no-optimize
.But then I get another error:
Searching in the bundle for that identifier this is the only place it appears:
Maybe this is related to #9972, although this error also happens when running with
--no-scope-hoist
.💁 Possible Solution
While writing this issue I realized that the problem goes away if I use
@parcel/optimizer-terser
as suggested here.The text was updated successfully, but these errors were encountered: