Bundle content scripts as IIFEs - #5
Merged
Merged
Conversation
pascalbaljet
marked this pull request as ready for review
July 30, 2026 07:50
This was referenced Jul 31, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Vite emits the multi-entry build-in ES module format, but the manifest loads
content-script.jsandpage-world.jsas classic scripts. Top-level bindings in a classic script land in the scope it runs in, so every minified name in the bundle became a global (var e,var t,var n, etc.). Forpage-world, which runs in the MAIN world, that scope is the inspected page's own.Any page whose scripts declare a colliding top-level
letthen fails to parse, not merely at runtime. On reddit.com, our globalebroke their first inline script with "Identifier 'e' has already been declared", which took out the helper the rest of their inline scripts call, and infinite scroll stopped loading posts entirely.Content scripts now build as separate single-entry IIFE bundles, the same way the service worker is already built, so nothing escapes into the page. The build fails if either bundle stops opening as an IIFE.