Skip to content

Tailwind 4 migration - with Node 20 - mvp#2641

Open
amazingphilippe wants to merge 5 commits intomainfrom
debt/tailwind4
Open

Tailwind 4 migration - with Node 20 - mvp#2641
amazingphilippe wants to merge 5 commits intomainfrom
debt/tailwind4

Conversation

@amazingphilippe
Copy link
Copy Markdown
Contributor

@amazingphilippe amazingphilippe commented Apr 2, 2026

Summary | Résumé

Upgrading to tailwind 4 and vite

  • the tailwind/vite combo works best with node 20 or above. Node 16 reached end of life in 2023, node 20 is also reaching end of life in April 2026.
  • Vite is ... quick. The compilation is very efficient and takes a fraction of a second. It compiles on save, so you can start the development server and forget about npm run tailwind when writing css and html
  • There are a few things I had to fix after the upgrade:
  • .container is not a utility provided by tailwind by default, but we can create our own.
  • @screen function has been replaced by @variant
  • Linting is more efficient, so I had to fix some invalid utilities in some @apply blocks
  • No more tailwind.config.js!! Its all a css theme, and integrates perfectly with native css properties

Test instructions | Instructions pour tester la modification

  • Locally, npm install
  • Maybe rebuild the container
  • npm run css does the build, but it also runs on make run-dev

@github-actions
Copy link
Copy Markdown

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