-
Notifications
You must be signed in to change notification settings - Fork 889
Is TSlint deprecated? #4904
Comments
😄 We've still got a couple weeks left! ...but yes, this is a good question. @adidahiya, do you have plans to mark the npm package as deprecated? |
I've been under the impression for months that tslint would soon be no more, because that's precisely what's been stated:
But I'm now super confused given that a beta for tslint 6 was released a month ago. What's the deal? |
Yes, I'm also very confused |
Indeed. Although we'd like everyone to move off of ESLint, there are still many users who rely on it. Version 6 contains some long-asked-for breaking changes to help those users. Our aim is that version 6 will be the last major version; everything after the main release will be either to assist with moving to ESLint or security fixes.
Correct. What is "deprecation"? Is it a big message in the README.md? A technical npm deprecation? Ultimately, people will keep using the package for a long time after either. I see the deprecation as:
Heh... Paying respects. There's not much we can glean from this issue other than waiting for someone from @palantirtech to mark the |
My original intent behind creating this issue was to question this line in the README:
Unless something happens In the next 10 days, this message should either be changed to "TSLint is now deprecated." or "TSLint will be deprecated some time in 2020." |
Have you thought about handing over the responsibility / repository so that it can continue to live driven fully by open source community? |
🤖 Beep boop! 👉 TSLint is deprecated 👈 and you should switch to typescript-eslint! 🤖 🔒 This issue is being locked to prevent further unnecessary discussions. Thank you! 👋 |
The
README.md
says "TSLint will be deprecated some time in 2019." If it is currently deprecated, the readme should be updated to say so. If not, this should probably be updated to say "TSLint will be deprecated some time in 2020.", since 2019 is almost over.The text was updated successfully, but these errors were encountered: