What does HackerNews think of typescript-eslint?
:sparkles: Monorepo for all the tooling which enables ESLint to support TypeScript
types can be imported either explicitly via `require()` or via the `@type {import("foo").Bar}`
There are definitely some limitations and caveats, like `Object` being aliased to `any` (I think this is being changed in a new version), but it's still way better than untyped JS, and having typescript integration is nice since our devs are already using typescript in other places.
Can even using things like https://github.com/typescript-eslint/typescript-eslint
Flow is both more advanced and faster than Typescript, but the community isn't as large, so Typescript continues to gain marketshare
https://github.com/typescript-eslint/typescript-eslint
Haven't ran into too many issues within the last 8 months or so. Only in Spring 2019 was it bad IME.
The biggest changer to me was TypeScript and DefinitelyTyped covering pretty much every package I end up trying out.
Hooks save a layer of indentation, and in most components, I don't need all the class stuff. In addition I find it harder to manage renders in classes.
Some design decisions, like overextending use of redux-forms can be a pain to back out of. Maintaining typings for these thing break often in my experience. I'm trying to stay away from redux (the data store) in favor of managing stuff through relay mutations.
Nice little comforts like prettier (code formatter) go a long way.
And apparently tslint is being deprecated in favor of eslint (https://github.com/typescript-eslint/typescript-eslint).
Code splitting via React.lazy / dynamic imports working with minimal effort.
The other thing that has helped is webpack's API becoming more stable, editor extensions getting better. I'm getting consistent linting and completion in vim. Stuff is snapping together.