Skip to content
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

tailwind v4 upgrade, drop postcss #279

Merged
merged 1 commit into from
Feb 2, 2025
Merged

tailwind v4 upgrade, drop postcss #279

merged 1 commit into from
Feb 2, 2025

Conversation

bgentry
Copy link
Contributor

@bgentry bgentry commented Feb 1, 2025

Mostly followed the upgrade guide and let its tool do most of the work.

I dropped eslint-plugin-tailwindcss because it may be awhile before it supports v4: francoismassart/eslint-plugin-tailwindcss#325

Also drop eslint-plugin-tailwindcss because it may be awhile before it
supports v4:

francoismassart/eslint-plugin-tailwindcss#325
@bgentry bgentry requested a review from brandur February 1, 2025 23:09
@bgentry bgentry enabled auto-merge (squash) February 1, 2025 23:14
@bgentry
Copy link
Contributor Author

bgentry commented Feb 2, 2025

@brandur since you approved #281 I'm assuming you're good with this one too. It's 95% from an automated upgrade script anyway.

@bgentry bgentry disabled auto-merge February 2, 2025 03:19
@bgentry bgentry merged commit 89bc79d into master Feb 2, 2025
13 checks passed
@bgentry bgentry deleted the bg-tailwind-upgrade branch February 2, 2025 03:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant