different formatting between developers causes unnecessary commits and makes it harder to review/track changes through git.
"industry standard" is eslint + prettier, however setting these up is an annoying and tedious process.
new kid on the block is biome.js which combines these tools into 1 chain that requires little config. its really nice. however its not ready for production i think.
no proper monorepo support (? not a big issue for us, i dont think we need different configs per project, exception being frontend)
roadmap says css support is not complete, and also non-react frameworks not yet supported. (also probably ok bc were using react)
https://biomejs.dev/blog/roadmap-2024/
no proper integration with monorepo managers like nx or turborepo. there are workarounds buuutttt that seems like it will cause maintainability issues in the future.
so, i might go back to eslint-prettier, but it will take me a hot minute to set those up properly
why we need this:
"industry standard" is
eslint + prettier, however setting these up is an annoying and tedious process.new kid on the block is
biome.jswhich combines these tools into 1 chain that requires little config. its really nice. however its not ready for production i think.nxorturborepo. there are workarounds buuutttt that seems like it will cause maintainability issues in the future.so, i might go back to eslint-prettier, but it will take me a hot minute to set those up properly