Migrating to React Router v7 and Tailwind v4
Estimated reading time: 2 minutes
After a long time, I finally migrated my Remix application to React Router v7 and Tailwind v4. Here is a list of changes I made.
React Router v7
Explicit routes declaration
In React Router v7, you need to explicitly declare your routes.
That allows me to reorganize my folder structure and not be forced to use file base routing convention.
Route type generation
React Router v7 now generates the route type for you. Don't use anymore LoaderFunction, ActionFunction, etc.
Tailwind v4
No config file
Tailwind v4 now css file only. No config file.
React 19
I upgraded to React 19. It brings a lot of new features and improvements.
Next improvements
This upgrade is a first step. I will continue to improve the template and the codebase.
- [ ] Use static site generation (evalable with react-router v7)
- [ ] Add page transition
- [ ] Imporve performance for search engine
Conclusion
I'm happy with the changes I made. I think it's a good thing to migrate to React Router v7 and Tailwind v4.
If you have any questions, please feel free to ask me or open an issue on the repository.