-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
refactor: popper package #3583
refactor: popper package #3583
Conversation
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/chakra-ui/chakra-ui/3zgmZFBQN1gAJhsNAmGjhrBpRWF9 |
🦋 Changeset detectedLatest commit: 47e3d79 The changes in this PR will be included in the next version bump. This PR includes changesets to release 57 packages
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 |
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 47e3d79:
|
Remove generic string type in system and styled-system which conflicts with the generated textStyles type
… config This config is only consumed by extractPropertyPath, which we don't use for layerStyles or textStyles theme generation
Closes #3433 #2481 #3385 #3089 #3384 #3440
📝 Description
This PR refactors the internal popper package to:
usePopper
and let popper.js write the styles internal. I found this is more reliable and works consistently.lite
version of popper.js to get a smaller bundle sizepopperGenerator
which gives us an agnostic base for all popper implementations across React and Vue.⛳️ Current behavior (updates)
There seem to be a lot of inconsistencies or issues with the placement of components and there were some hacks we had but didn't work well.
🚀 New behavior
Allows popper.js to handle all style computation and remove internal state. This is consistent and more reliable
💣 Is this a breaking change (Yes/No):
No, as
usePopper
is an internal API📝 Additional Information