vue-ts-tailwind VS typescript-eslint

In one of my previous projects, I fall in love with TailwindCSS. I know that this is a very controversial framework for some, but for me, personally, as a backend developer of 11 years, it was the first time I had a fun time adding styles to the frontend. I even created vue-ts template with it, as a part of another articles' series.

-[](https://results.pre-commit.ci/latest/github/imomaliev/vue-ts/main) - +[](https://results.pre-commit.ci/latest/github/imomaliev/vue-ts-tailwind/main) + -# Vue 3 + Typescript + Vite + Jest +# Vue 3 + Typescript + Vite + Jest + TailwindCSS -This template should help get you started developing with Vue 3 and Typescript in Vite. +This template should help get you started developing with Vue 3, Typescript and TailwindCSS in Vite.

vue-ts-tailwind

Typescript-eslint can assist in this task. This tool helps identify all instances of unsafe any usage. Specifically, all usages of JSON.parse can be found and it can be ensured that the received data's format is checked. More about getting rid of the any type in a codebase can be read in the article Making TypeScript Truly "Strongly Typed".

> Only lint files that have changed? How hard that is?

Quite hard, especially since type-aware rules from e.g. https://typescript-eslint.io/ mean that changing the type of a variable in file A can break your code in file B, even if file B hasn't changed.

The article only touches this: when converting to TypeScript, `any` is useful, but in the end you don't want this type in your codebase - so don't forget to use typescript-eslint [0] and turn on those no-unsafe-* rules which guard against `any` leaking into your code.

[0] https://github.com/typescript-eslint/typescript-eslint

By convention, React components should be named in PascalCase. @typescript-eslint has the config we need, and though we can't specifically target React components, we can target variables (and set some other conventions while we're at it):