Adding Prettier to the mix helps too, as ESLint alone is a bit too loose with defaults and takes a lot of tuning to get something that ensures a uniform way of code formatting in multi-dev teams.
Eslint has deprecated formatting rules in one of their latest versions. They recommend using Prettier for the formatting. I like the clear distinction now. I removed the eslint-prettier-config last week 😄
Speaking as someone who had to recently work on a Node (CommonJS) app that didn't use TypeScript: Since I've always been a huge proponent on static typing, I went about applying them using JSDocs, and it help me catch so many potential issues. (Not to mention it allowed for better autocompletion and the like.) While JSDocs can apply a non-enforceable form of static typing, it's also a huge pain in the butt to implement more complex typings -- and even then, it's nowhere near as robust or versatile as TypeScript. Always go with TypeScript!
The way I see it, the more things drawing red squiggly lines on your source code the better... and a good linter is worth a thousand AI "co pilots". :)
It would be great if you could share your .eslintrc or maybe even provide more info like you did in your awesome tsconfig cheat sheet. Love your content!
Adding Prettier to the mix helps too, as ESLint alone is a bit too loose with defaults and takes a lot of tuning to get something that ensures a uniform way of code formatting in multi-dev teams.
Prettier + format on save is a life save honestly
Thank you do much, im zbout to sleep and i added eslint as things to instzll for my project. Now im sure it is a good decision
I will stick with TS
Eslint has deprecated formatting rules in one of their latest versions. They recommend using Prettier for the formatting. I like the clear distinction now. I removed the eslint-prettier-config last week 😄
if you use prettier and eslint together, you should keep eslint-prettier-config. it just disables the eslint rules that conflicts with prettier
TypeScript vs ESLint.
Both. Both are good.
Speaking as someone who had to recently work on a Node (CommonJS) app that didn't use TypeScript: Since I've always been a huge proponent on static typing, I went about applying them using JSDocs, and it help me catch so many potential issues. (Not to mention it allowed for better autocompletion and the like.)
While JSDocs can apply a non-enforceable form of static typing, it's also a huge pain in the butt to implement more complex typings -- and even then, it's nowhere near as robust or versatile as TypeScript.
Always go with TypeScript!
When using ESLint rules that integrates with TypeScript types, how does it affect performance?
I wonder why Dart typechecking / linting is immediate and snappy and TS is slow af
Biomejs + Esbuild = ❤
Biome >>>>>>>> eslint
How to make Typescript faster
Agree
The way I see it, the more things drawing red squiggly lines on your source code the better... and a good linter is worth a thousand AI "co pilots". :)
@matt maybe you can do a video on using eslint as a step in sast analysis?
TS project references help to reduce some of the overhead.
It would be great if you could share your .eslintrc or maybe even provide more info like you did in your awesome tsconfig cheat sheet.
Love your content!