Merged
Conversation
f7fc236 to
827e5f2
Compare
7e55219 to
cb6a0f6
Compare
9bb8ae4 to
41c0449
Compare
RobinMalfait
reviewed
Sep 2, 2025
| tailwindPackageName: 'tailwindcss-v4', | ||
| }) | ||
|
|
||
| expect(result).toEqual('<div class="group peer unknown-class container p-0"></div>') |
Member
There was a problem hiding this comment.
Shouldn't unknown-class exist before group and peer? 🤔
Because while group and peer don't exist, they are still more known than unknown classes.
I don't know if we test this already, but named group and peers should be in a similar position.
Contributor
Author
There was a problem hiding this comment.
In v4 we don't sort group and peer though
RobinMalfait
approved these changes
Sep 2, 2025
Member
RobinMalfait
left a comment
There was a problem hiding this comment.
Looking good (after you resolve the changelog conflict)
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
2 participants
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.
Breaking Change
We now fall back to v4 by default
Earlier versions of this plugin loaded a bundled version Tailwind CSS v3.x if no local install was found. This behavior remained even when you had configured the
tailwindStylesheetoption.We'll now intelligently load either v4 or v3 based on some rules which are outlined (approximately) below:
tailwindStylesheettailwindConfigtailwindStylesheettailwindConfigtailwindStylesheettailwindConfigNotably, you can always force v4 by providing a
tailwindStylesheetoption — regardless of your local Tailwind CSS version. The same goes for v3.x and an explicittailwindConfigoption. If both are provided a warning is printed and the stylesheet takes precedence (and thus v4 is loaded).If you do not provide a
tailwindStylesheetwhen running v4 this plugin will use the default theme. You must provide this option if you customize your theme, variants, utilities, plugins, etc… otherwise some classes may sort incorrectly.This bundles Tailwind CSS v4, it's relevant stylesheets, and intercepts their loading so users of the CDN or Standalone CLI can properly sort these without needing a local install through NPM.
This is a breaking change. We will still, however, search for a
tailwind.config.js(or similar) in this scenario and load a bundled version of v3 if we find one. Specifying a stylesheet will force the plugin to load a bundled version of v4 if no local install exists.Fixes #364