Thanks for the vanilla-extract recommendation, I'll be using this! In my case, tailwind was useful for providing a handy set of vocabularies for simple and common stylings. But once customizations start to pile on, we're back into SCSS. Using 2 systems at once meant additionally gluing them with the postcss toolchain, so effectively we have 3 preprocessors running for every style refresh. Looking in at TypeScript... - Source: Hacker News / over 1 year ago

I spent some time doing this ~3 years ago, so I don't know about now, but to my knowledge it was the only language where you could really use one language for everything: no HTML (via hiccup), no CSS (via garden), clojure/clojurescript everywhere, and no shell (via babashka). Source: almost 2 years ago

I have a silly react project that I’m working on that I made using create-react-app. By default, these kinds of projects build and run using react-scripts which uses webpack under the hood for building projects. Vite is generally known to be faster than Webpack ⚡ so I was curious about how to swap them. - Source: dev.to / 2 days ago

We wanted to change the bundler to vite for two main reasons:. - Source: dev.to / about 1 year ago

You can see all create-vite templates for other libraries. You can also learn more about vite in its documentation website. - Source: dev.to / 7 days ago

After we have installed the Node environment, we can use Vite to install. Because the use of Vite has a higher version of Node.js requirements, so I recommend that you install a relatively new Node.js. Currently I use the version for v18.15.0. - Source: dev.to / 8 days ago

Import { defineConfig } from 'vite' Import riot from 'rollup-plugin-riot' Export default defineConfig({ root : process.cwd() + '/client', plugins : [riot()], build: { minify : 'esbuild', /** https://vitejs.dev/config/build-options.html#build-minify */ target : 'esnext' /** https://vitejs.dev/config/build-options.html#build-target */ } }). - Source: dev.to / 10 days ago