Getting the same issue here as @Stvad. Seems like web extension production build is not robust (it works well in parcel watch dev mode)?

I followed the changes from @Kjoep and simply added this to package.json and my production build seems to work.

"@parcel/bundler-default": {
  "minBundles": 10000000,
  "minBundleSize": 3000,
  "maxParallelRequests": 20
}

Command: parcel build manifest.json --no-content-hash

Without no content hash, I get this error: Error: Cannot read properties of undefined (reading 'hashReferences')

Thanks, I’ve reproduced the issue and am working on fixing it now.

Individual files have to be smaller than 4MB when publishing Firefox extensions:

• https://discourse.mozilla.org/t/bug-with-uploading-large-files-in-addon/85407
• https://discourse.mozilla.org/t/firefox-web-extension-background-script-to-bundle-or-not-to-bundle/82805

I haven’t been able to properly look at this. For now we should probably just document the issue and add the code-splitting removal fix into the docs.

@101arrowz Thank you for replying, great, that’s something!

Can you please share here for now how to remove code-splitting?

@101arrowz here’s my reproduction: https://github.com/lukaw3d/reproduce-parcel-webextension-codesplitting-broken

• uses parcel@2.6.0 and @parcel/config-webextension@2.6.0
• manifest v2 with two entry points: background.ts and popup.html
• both entry points import something large (lodash)
• users browserslist to target an old browser (Chrome 60)

background page throws Cannot find module when initializing

To be fair, the codesplitting does not seem very important for webextensions, as they are loaded locally, not over the network. It might be acceptable to automatically turn the feature off.

I’d say PREFERABLE

I have the same problem (at least it looks like it) and did some digging. Turns out the WebExtensionPackager is not compatile wit the code-splitting feature. If bundles get split off, it does not add the split-off bundles to the manifest. From what it looks like it only does a naive find-and-replace.

I have a simple workaround here: https://github.com/Kjoep/parcel/tree/prevent_losing_webextension_deps (use it for config-webextension). This turns off the code-splitting for web extensions.

@101arrowz I’m using Parcel 2.7.0 and below config doesn’t work for me:

    "@parcel/bundler-default": {
        "minBundles": 10000000,
        "minBundleSize": 3000,
        "maxParallelRequests": 20
    }

I still get only 1 file: manifest-firefox.js #8404

This comment seems to work: https://github.com/parcel-bundler/parcel/issues/8071#issuecomment-1133549719

To be fair, the codesplitting does not seem very important for webextensions, as they are loaded locally, not over the network. It might be acceptable to automatically turn the feature off.

Manifest v3 with --no-scope-hoist is an interesting case, as in it content script is broken, but background is fine, and content script is failing to import ../options/options-storage module, which is what background script fails to import in the other broken cases 🤔