babel-plugin-macros VS vite

One of the more promising alternatives is twin.macro - a Babel macro that processes Tailwind classes to generate JS objects understandable by various CSS-in-JS libraries. The developer experience (DX) of using it is amazing as you not only get all of Tailwind’s features without much change to your code, but you also get much more flexibility - all that on top of the traditional benefits of CSS-in-JS. Here’s an example code:

For example with Babel you could use babel-plugin-macros to execute this file at compile time and replace the file contents with the result of the computation. So appSettings would only have the configs for the current environment and nothing more and your source wouldn't need to change much.

It does require babel-plugin-macros which should also help with keeping things nice and performant in production. The package is part of a larger initiative im trying to achieve which is to create file-system based routing for all mainstream React and React Native routing packages. I have done everything I can to keep it as boilerplate free as I can. To give an example

MacroError: The macro you imported from "undefined" is being executed outside the context of compilation with babel-plugin-macros. This indicates that you don't have the babel plugin "babel-plugin-macros" configured correctly. Please see the documentation for how to configure babel-plugin-macros properly: https://github.com/kentcdodds/babel-plugin-macros/blob/master/other/docs/user.md

Yes, it also does that. https://github.com/kentcdodds/babel-plugin-macros

babel-plugin-macros

Vite - Fast build tool and development server

The application scaffold was created using the Vite build tool (https://vite.dev/).

vite handles it really well but run via bunx

Frontend Vue with Vite, PrimeVue for components, unDraw for illustrations

I used Spring Initializr to generate the starting point of my Spring Boot application, using their MySQL guide to set up a database in Docker. I also created a React+Vite app to consume the API I plan on creating.

Why are there so many JavaScript build tools? Gulp, Grunt, Webpack, Laravel Mix, Rollup.js, and now Vite. And these are just the ones that I've worked with. Haven't we solved this problem? And why build a new tool? Why not improve existing tools?

Vite Documentation Next.js Documentation React Docs

Vite + React for the frontend

When I first set up my project, I chose TailwindCSS 3.4.17 because it was stable, reliable, and packed with all the utilities I needed to build a sleek, responsive design. Paired with Vite 6.3.2 for its blazing-fast development server and autoprefixer 10.4.21 to handle browser compatibility, my workflow felt smooth and efficient. However, as the web development landscape evolves, so do the tools we rely on. Recently, TailwindCSS 4.1 was released, and after reading through the official announcement , I realized it’s time to take my project to the next level.