3 ms·
If you're gonna rant about the JS ecosystem at least get it right. You can set up a Vite + React + Tailwind setup with two commands npm create vite npm i
by b_e_n_t_o_n 1y ago
If you're gonna rant about the JS ecosystem at least get it right. You can set up a Vite + React + Tailwind setup with two commands
npm create vite
npm i @tailwindcss/vite tailwindcss
If you want automatic code formatting and linting install biome, that's one more command.
You don't need to think about React Refresh or babel or typescript, it's all handled by vite. I've never even seen a .babelrc file. And why does the author add husky?
Like, if you want to criticize JS fine, but chose valid criticisms. This just sounds like the author hasn't actually used modern js.
- jonhohle 1y agoThose two commands required earlier commands to install node and npm.
- b_e_n_t_o_n 1y agoNPM comes with Node. And obviously you need to install node, just like you need to install Ruby....
- marksomnian 1y agoAnd `rails new` required me to install Ruby and Rails. I'm not sure what the point you're making is.
- hu3 1y agoWhat about the backend? Rails covers that, your solution doesn't. I guess I should draw the rest of the owl.
- b_e_n_t_o_n 1y agoMy point is that you don't need half of the things the author thinks you need for a JS frontend with Vite, TS, React, and Tailwind....
- tills13 1y agoUse NextJS, then. I think everyone in this thread and the author of the post is intentionally choosing sub-optimal setups for the side they don't like.