TSLint will very soon move to maintenance mode and, starting from January 1st 2020 stop accepting anything except security fixes. This is a documented issue, also explained in their blog post. I believe that JHipster should move from TSLint to ESLint in the similar timeframe.
For sure TypeScript will continue to be developed, and hopefully JHipster and ESLint too. I think that staying stuck with the tool which will be abandoned soon is not an optimal way ahead.
Tasks:
I think we need to wait until https://github.com/mgechev/codelyzer/issues/763 is closed.
We needn't have to wait, as such a migration is kind of easy to do, and works (I've done this migration twice, this wasn't such a big deal).
@jhipster/developers, anyone willing to take. Otherwise, I will spend time over weekend
I think you can take it. Thanks a lot @vishal423 ! So happy to have you in the team :-)
Is that really urgent ? TSLint looks pretty well used today and there are not a clean migration path documented about this.
Also, some codelyzer rules aren't yet implemented in ESLint so we would loose some great lint features on the Angular side.
@wmarques, I believe we can use eslint-plugin-tslint to continue execute tslint specific rules. I have started work on this activity with an angular project and might be able to come up with something in next few days..
@vishal423 typescript-eslint v2 has been released and have breacking changes. Maybe it is better to use the new version now? See https://github.com/typescript-eslint/typescript-eslint/commit/05ba26879dd5a5a0e1159951c8b24dc5e0e5cc4a
@DanielFran, thanks for update. Dependency update is a never ending task.
And do not forget to claim the bug-bounty and close this issue :stuck_out_tongue_winking_eye:
Bounty claimed https://opencollective.com/generator-jhipster/expenses/10350
Just approuved.
Thanks @vishal423 !