Update to ESLint

[Azkali]

TSLint -> ESLint

Issue Description

As TSLint is in deprecation state you should port this repo to ESLint.

Possible resolution

Using the npm package tslint-to-eslint-config you should be able to easily port your config to ESLint, I can make a PR if you wish !

[GerkinDev]

I tested the package you mention, and it does not support all options of tslint. Moreover, beware, it tends to forget to append plugins.

OK for a PR, but make a different file for eslint & do not move the tslint config. While eslint for typescript is not in a better state, both should coexist.

[Azkali]

Will do so !

[Azkali]

Or maybe I can create a new branch for ESLint ( + TSLint rules not supported by ESLint ).

I find this better than polluting the main branch ( user could want TSLint only ) and also ESLint can have his own version ( package.json )

[GerkinDev]

I don't see the problem with 2 config files at root level. This would pollute with a single file, and otherwise, it would drastically complexify versioning & releases for such a simple repo...

[Azkali]

Alright, I will follow your lead then !