4 ms·
Making all this (for example) work nicely together can be tricky: Vite, ESLint, Prettier, Typescript and React, especially if it's full stack with SSR. If you
by dominicrose 3mo ago
Making all this (for example) work nicely together can be tricky: Vite, ESLint, Prettier, Typescript and React, especially if it's full stack with SSR.
If you only focus on the front-end and remove Typescript from the equation it becomes easy enough. We'll have to see if Vite+ helps for the more complex cases.
- Silhouette 3mo agoMaking all this (for example) work nicely together can be tricky: Vite, ESLint, Prettier, Typescript and React, especially if it's full stack with SSR. Although about 98%* of that is because ESLint keeps making breaking changes and getting everything else to work compatibly with ESLint requires 27,573* additional dependencies. Things I work on have been moving over to Biome recently (mostly these are Vue projects rather than React these days) for formatting and linting and it's so much simpler and avoids all the "What ESLint-related package broke our build process this week?" discussions entirely. *Some numbers here may be made up. Or they might not.
- dominicrose 3mo agoLots of breaking changes but I like where they landed, the config file is now clearly an mjs, no longer a hidden file, allows JSX without a plugin. I reckon the best way to upgrade is to generate a new project that has everything configured and copy that and stay close to defaults unless there's a good reason not to.