-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
feat: Update to Tailwind v4 #7669
base: main
Are you sure you want to change the base?
Conversation
66d7f3f
to
57bcefe
Compare
1 similar comment
1 similar comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
will try the running example in a bit, generally looks good though
.circleci/config.yml
Outdated
filters: | ||
branches: | ||
only: main | ||
# filters: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
revert
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
waiting for it to be approved first 😄
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah, this is more of a reminder since I always worry I'll forget
@@ -0,0 +1,19 @@ | |||
diff --git a/dist/transformer.d.ts b/dist/transformer.d.ts |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
how long is this going to be around? will other users need to do the same patch?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
until heroui-inc/tailwind-variants#239 is fixed.
@@ -135,6 +136,7 @@ async function build() { | |||
fs.copySync(path.join(__dirname, '..', 'starters'), path.join(dir, 'starters')); | |||
fs.copySync(path.join(__dirname, '..', '.yarn', 'releases'), path.join(dir, '.yarn', 'releases')); | |||
fs.copySync(path.join(__dirname, '..', '.yarn', 'plugins'), path.join(dir, '.yarn', 'plugins')); | |||
fs.copySync(path.join(__dirname, '..', '.yarn', 'patches'), path.join(dir, '.yarn', 'patches')); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
could probably do what we do for buildBranchAPI and just copy everything in .yarn
instead of picking and choosing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did not find anything new, lgtm
hmm, seems that |
Closes #7661, closes #6127, closes #7263, closes #5800, closes #5642
This updates the
tailwindcss-react-aria-components
plugin, the docs homepage and examples, the Tailwind starter kit, and example apps to Tailwind v4.The plugin will need to be released as a major version bump. 1.x will work with Tailwind v3, and 2.x will work with Tailwind v4. This is because Tailwind made some internal changes that we needed to account for:
:merge()
selector is no longer supported.group
andpeer
variants as Tailwind will automatically generate these for all variants.hoverOnlyWhenSupported
option was removed and is now the default.One additional challenge is that variants added by our plugin are no longer ordered in the same way. Unfortunately that means variants like
disabled:
will no longer override other variants unless you stack them. Not sure if there is a way around this.