4 ms·
Joined a team that maintains a pretty popular TS library recently. The repo was using Biome. It was unanimously disliked by the team. Linting was broken for mos
by DGCA 1y ago
Joined a team that maintains a pretty popular TS library recently. The repo was using Biome. It was unanimously disliked by the team. Linting was broken for most people and in CI. I replaced it with Prettier + ESLint, everyone was into it, and we realized we had a bunch of issues that weren't getting reported due to it not working in CI.
- sureIy 1y agoWhat do you mean by "linting was broken"? I seriously doubt this statement without context.
- DGCA 1y agoI didn't set up Biome and can't tell you why it wasn't working, but people on the team couldn't get the VSCode extension to show lint errors in their editor (Cursor, primarily). I misspoke about there being a CI issue. It was more like disagreeing with their defaults, e.g. `useHookAtTopLevel` and `noUnusedVars` are off by default. `useHookAtTopLevel` is especially confusing since other React hook rules are on, and `eslint-plugin-react-hooks` defaults its analogue to "error". But yeah, no linting in the editor was kinda bonkers.