perf: use global browser instead of webextension-polyfill #839
Conversation
This file contains 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
github-actions
bot
added
area: content
Extension builds preview
|
){kind=icon}
){kind=icon}
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.
Context
We don't need the polyfill except for async message handlers in background.
Changes proposed in this pull request
Remove polyfilled browser from content scripts and React apps to reduce bundle size, and have less JS in content scripts (as they get injected into each frame in each tab) for better performance.
Keeping it draft until we add more E2E tests.
Zip size went down 20KB only (duplication compresses better in zip). Unzipped size went 2.09MB from to 2.03MB (60KB).