Skip to content

Conversation

@emmadesilva
Copy link
Member

@emmadesilva emmadesilva commented Apr 21, 2025

See https://tailwindcss.com/docs/upgrade-guide#using-the-upgrade-tool

All existing projects should run:

$ npx @tailwindcss/upgrade

We now use https://tailwindcss.com/blog/tailwindcss-v4#first-party-vite-plugin. As a side effect, we needed to switch to the ESM extension for the Vite configuration https://vite.dev/guide/troubleshooting.html#this-package-is-esm-only

@emmadesilva emmadesilva added the run-visual-tests Internal label to trigger Browserstack visual testing label Apr 21, 2025
@emmadesilva emmadesilva changed the base branch from master to 2.x-dev April 21, 2025 16:55
@codecov
Copy link

codecov bot commented Apr 21, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (4b63f4d) to head (3b90e57).
Report is 9 commits behind head on 2.x-dev.

Additional details and impacted files
@@             Coverage Diff             @@
##             2.x-dev     #2146   +/-   ##
===========================================
  Coverage     100.00%   100.00%           
  Complexity      1976      1976           
===========================================
  Files            199       199           
  Lines           5282      5282           
===========================================
  Hits            5282      5282           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@emmadesilva emmadesilva merged commit 08cf5c2 into 2.x-dev Apr 21, 2025
20 checks passed
@emmadesilva emmadesilva deleted the tailwind-4 branch April 21, 2025 19:58
@github-actions github-actions bot removed the run-visual-tests Internal label to trigger Browserstack visual testing label Apr 21, 2025
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.

2 participants