Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(clerk-js): Lazily load VirtualBodyRootPortal #3519

Merged
merged 2 commits into from
Jun 5, 2024

Conversation

panteliselef
Copy link
Member

@panteliselef panteliselef commented Jun 5, 2024

Description

With the introduction of GoogleOneTap in clerk-js@5.4.0 the bundle for clerk-js.browser.js was increased from 69KB to 166KB. This PR fixes that.

Checklist

  • npm test runs as expected.
  • npm run build runs as expected.
  • (If applicable) JSDoc comments have been added or updated for any package exports
  • (If applicable) Documentation has been updated

Type of change

  • 🐛 Bug fix
  • 🌟 New feature
  • 🔨 Breaking change
  • 📖 Refactoring / dependency upgrade / documentation
  • other:

@panteliselef panteliselef self-assigned this Jun 5, 2024
Copy link

changeset-bot bot commented Jun 5, 2024

🦋 Changeset detected

Latest commit: 5835bd0

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 3 packages
Name Type
@clerk/clerk-js Patch
@clerk/chrome-extension Patch
@clerk/clerk-expo Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@panteliselef panteliselef changed the title chore(clerk-js): Lazily load VirtualBodyRootPortal chore(clerk-js): Lazily load VirtualBodyRootPortal Jun 5, 2024
@panteliselef panteliselef requested a review from a team June 5, 2024 16:24
@panteliselef panteliselef enabled auto-merge (squash) June 5, 2024 16:31
@panteliselef panteliselef merged commit c054dcb into main Jun 5, 2024
13 checks passed
@panteliselef panteliselef deleted the elef/fix-bundle-size branch June 5, 2024 16:33
Copy link
Contributor

@dimkl dimkl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤔 I think we had bundlewatch enabled with a hard limit of around 70KB. I think we should add a check to avoid raising the size of the clerk browser without being noticed.

@panteliselef
Copy link
Member Author

AFAIK we will investigate why bundlewatch is not running and we will re introduce it soon in another PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants