4 ms·
Prettier -> ESLint -> BiomeJS and back to Prettier. Common standards are ok, but as soon as you want some small modifications, you will come back to prettier.
by progx 1y ago
Prettier -> ESLint -> BiomeJS and back to Prettier.
Common standards are ok, but as soon as you want some small modifications, you will come back to prettier. Performance is not a real problem.
- hombre_fatal 1y agoI think the best .prettierrc file is "{}" (all defaults). Even as someone who will never write a semicolon myself in Javascript (and still won't), I had to admit that nothing is so important that it's worth straying from zero config.
- dmix 1y agoPrettier pretty much tells you to not config it
- tshaddox 1y agoFor Prettier I agree that performance is not generally a problem, especially since you're usually only applying it one file at a time (except in CI, perhaps, although even there it probably only needs to be run on changed files). But I have worked on several projects where ESLint performance is a problem in local development.