My Tragic TSLint Experience

Photo by Fotis Fotopoulos on Unsplash

I recently ran into one of the most devastating experiences of my whole programing career, the discovery that TsLint, my faithful friend and companion, was being retired.

But what enraged me was not its retirement, TSlint being replaced by the illustrious ESlint for typescript, but the fact that the entire universe seems woefully unaware. When was somebody going to let me know that it was being depreciated? The website doesn’t say so, Angular still ships with it, and 2553 other NPM projects are dependent on it.

Palantir’s efforts to unite linting packages, as describes on their blog, is noble. But there’s a significant lack of information to transfer from TSLint to ESlint, save an auto translator from a TSlint config file to ESlint that didn’t seem to work for me.

Regardless of the warnings from TSLint, I will continue using the linter that in my heart, is the best available for typescript.

Passionate about building cool shit. First-year undergrad student studying EECS and Business @ UC Berkeley MET Software developer at Carline.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store