Always emit keyframes registered in addUtilities

[thecrypticace]

Fixes #14732

cc @philipp-spiess this look like an okay fix?

[adamwathan]

Wonder if all we actually need to do is revert this one line change?

https://github.com/tailwindlabs/tailwindcss/pull/14672/files#diff-5558c180ba5a080e430ff267430cee62a03a9deedf65a6e8fb5d7c685813c88f

Do @keyframes added this way even need to be registered with the theme at all or should we just add them as static CSS rules? The latter sounds more right to me without getting too deep into it.

[philipp-spiess]

Ahhh... of course. 🤕 We should probably add a test in the plugin-api spec for this that only uses addBase in a plugin and ensures the keyframe is emitted?

I’m with @adamwathan here in that this feels like it should go directly in the CSS. This way we can also keep the core layer pristine.

[thecrypticace]

Ah yeah directly inserting into the AST seems more reasonable. I'll make that change. Ditto w/ addBase + tests

[philipp-spiess]

Merge activity

• Oct 22, 12:07 PM EDT: The merge label 'merge-queue' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Oct 22, 12:08 PM EDT: A user added this pull request to the Graphite merge queue.
• Oct 22, 12:09 PM EDT: The Graphite merge queue couldn't merge this PR because it had conflicts with the trunk branch.
• Oct 22, 12:28 PM EDT: The merge label 'merge-queue' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Oct 22, 12:33 PM EDT: A user added this pull request to the Graphite merge queue.
• Oct 22, 12:39 PM EDT: A user merged this pull request with the Graphite merge queue.