Add keyframes as utilities instead of base#2108
Merged
adamwathan merged 1 commit intomasterfrom Aug 2, 2020
Merged
Conversation
workashutosh
pushed a commit
to workashutosh/tailwindcss
that referenced
this pull request
Apr 3, 2025
Follow up to tailwindlabs#2107. Please note there are still instances in of `px` usage in the v4-alpha and v4 blog posts, wasn't sure whether those should be changed too, or preserved for prosperity.
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
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.
This PR updates the animation plugin to add the keyframes rules to the "utilities" layer rather than the "base" layer. Sounds a little bit weird until you realize that doing it any other way means you need
@tailwind basein your CSS for animations to work, which feels wrong. You should be able to use our animations using just the "utilities" layer.Fixes #2103.