I mean... Most typescript projects use prettier and eslint to enforce coding standards... They're not mutually exclusive at all. But like the other commenter I don't see how you can achieve type safety with eslint and prettier...
My bad, I failed to state the scope of which I published this post.
The post was created bearing in mind small projects.
I completely agree that using eslint and prettier for enforcing coding standards is a common practice in TypeScript projects.
However, my point in the hot take was that for small projects, using eslint and prettier with the right configuration can offer a certain level of type safety.
Of course, they can't completely replace TypeScript in terms of type safety, but they can help catch some errors and improve the overall quality of the code. It's all about finding the right balance and using the tools that work best for your specific project and team.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I mean... Most typescript projects use prettier and eslint to enforce coding standards... They're not mutually exclusive at all. But like the other commenter I don't see how you can achieve type safety with eslint and prettier...
My bad, I failed to state the scope of which I published this post.
The post was created bearing in mind small projects.
I completely agree that using eslint and prettier for enforcing coding standards is a common practice in TypeScript projects.
However, my point in the hot take was that for small projects, using eslint and prettier with the right configuration can offer a certain level of type safety.
Of course, they can't completely replace TypeScript in terms of type safety, but they can help catch some errors and improve the overall quality of the code. It's all about finding the right balance and using the tools that work best for your specific project and team.