Migrate to ESLint

[kitsonk]

The TypeScript team announced a couple months ago that they were focusing internally on migrating to ESLint from tslint and then earlier this week tslint mentioned that they were deprecating tslint and joining forces with ESLint.

Therefore I think it only makes sense we migrate to ESLint. It would also be a good point to re-evaluate our linting rules and ensure that we extend our rules based on ignoring anything that Prettier handles (currently there are a couple conflicts between Prettier and tslint we have to add ignore comments for).

[ry]

Do you have a link to that announcement ?

[kitsonk]

@ry https://medium.com/palantir/tslint-in-2019-1a144c2317a9

[ry]

Thanks. Yes I'm all for this.

[kitsonk]

cc/ @JamesHenry

Any thoughts on migration approach appreciated.

[j-f1]

Check out our docs on equivalents for TSLint rules for some guidance.

[kitsonk]

@j-f1 any good standard configs you can recommend. I am not totally a fan of our current rules.

[j-f1]

We’ve got a recommended config (plugin:@typescript-eslint/recommended, rules are marked with a ✔️ here) for TypeScript-specific linting, and for general JS support, Airbnb or the default eslint:recommended config are common options. I strongly recommend Prettier for linting formatting, and using eslint-plugin-prettier to disable any formatting rules in the other configs.

[balupton]

Perhaps https://discuss.bevry.me/t/how-bevry-automates-maintenance-of-its-prolific-open-source-portfolio/693?u=balupton and https://github.com/bevry/eslint-config-bevry would be useful as it detects the needs of the project and adapts the linting accordingly

[ry]

This was completed in #1905

[romainPrignon]

Hello :)
Is there any doc about eslint-typescript integration ?
I search on https://deno.land/manual.html and https://deno.land/manual.html and https://deno.land/style_guide.html but I found nothing :(

[JustFly1984]

Eslint plugin deno, and VSCode extension could be amazing!