3 ms·
Over the past few months, I have migrated numerous projects to Biome and Dprint, and in some cases, back to ESLint and/or Prettier. Projects in plain TypeScript
by exiguus 1y ago
Over the past few months, I have migrated numerous projects to Biome and Dprint, and in some cases, back to ESLint and/or Prettier. Projects in plain TypeScript/JavaScript have worked out quite well. However, as soon as JSX/TSX with React or Angular came into play, we encountered lagging issues with popular plugins and configurations. The number of bugs increased, prompting us to revert to ESLint.
I recall that migrating an entire company style guide from ESLint to Biome was nearly impossible because it relied on many rules from other ESLint plugins. Writing these rules / plugins ourselves was too much effort. Perhaps someone else has experience with this and can share their insights?
I agree that performance is valuable, especially in token-based development where you push directly to the main branch. Having hooks and builds run on your local machine and experiencing a 30-second speed improvement is nice. However, in the case of migrating an entire company style guide, it might be more cost-effective to simply buy new laptops that can run everything faster.
Nevertheless, I have had very positive experiences with plain TypeScript projects. In such cases, I would do it again. Especially when you have to update from ESLint Version 8 to 9, taking a look at Biome might be a good investment of time.