fix: time till browser action dropdown appears #430
Merged
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.
factor-bundle
pulls common dependencies out from our page scripts to minimise download size of the extension.This is a good thing since we don't want to include multiple versions of large dependencies such as IPFS (for example).
However, it introduces the overhead that every page using the common bundle has to read and parse it, even if some of the dependencies aren't used.
For the browser action, the only "significant" shared dependency is
choo
, which is only 4kb. The browser action is reading a ~4mb JS file just for a single dependency. This is what is causing the short delay in opening the dropdown.I've taken the browser action script out of the factor bundle and built it separately, meaning that we have a duplicate
choo
, but I think it's worth the 4kb hit for the performance improvement.Try it out, it is 🐎 💨