EMULSIF-565: Upgrade Emulsify UI Kit to Emulsify Core 4.x#181
Open
robherba wants to merge 5 commits into
Open
Conversation
❌ Deploy Preview for emulsify-ui-kit failed.
|
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
1 participant
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.
Ticket(s):
Summary
This PR migrates the Emulsify UI Kit from the legacy Webpack-based Core 2.x setup to the new Vite-based Core 4 workflow. This upgrade modernizes our build process while preserving the existing UI Kit component structure, token generation, accessibility checks, and Storybook deployment workflows.
Documentation update (required)
If this pull request requires a change to Emulsify documentation, those changes, updates, and/or new information must accompany this pull request.
How to review this pull request
Closing issues
Closes #