Skip to content

Conversation

@jfgrissom
Copy link
Contributor

  • Create new project from react-starter
  • Add package @tailwindcss/vite to dev deps.
  • Review manual upgrade docs
    • confirm postcss.config.js matches docs
    • add new import to vite.config.js
    • confirm directive is set in index.css file.
  • Address theme changes from v3 to v4
    • Remove theme from tailwind.config.js file.
    • Add theme to index.css file.
  • Retain fonts
    • Remove them from tailwind.config.js file.
    • Add them to index.css file.
    • Apply font to html tag.
  • Merge changes back into create-juno/templates/react-starter

@jfgrissom
Copy link
Contributor Author

This only handles this change for the react-starter template.

If this gets merged I'll assume it's what you're looking for and start on the rest.

@peterpeterparker
Copy link
Contributor

Super cool, thanks!
I'll give it a shot and propagate the changes in every templates this week.
I keep the PR open as a reminder 😉

@peterpeterparker
Copy link
Contributor

From what I tested both postcss.config.js and tailwind.config.js can be deleted once the new plugin is added to a project. I'll do so after merge and will update all templates with the changes.

Thanks!

@peterpeterparker peterpeterparker merged commit a91af1f into junobuild:main Feb 14, 2025
4 checks passed
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