-
Notifications
You must be signed in to change notification settings - Fork 234
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unmaintained and buggy (especially with ST4) + an alternative #786
Comments
That explains a lot! Thanks for the recommendation for LSP-Typescript! |
Wow, I just found this issue and switched over to LSP-typesript. It's so much better. Finally no more false-positives. |
It definitely would've saved me some time if there was something front and center in the README about this. I was quite confused as to why it wasn't showing up in the Package Control install and after I dug into the versioning I found this issue. |
This package hasn't been properly maintained for a long time and doesn't look like Microsoft wants to put any resources on it apart from occasionally bumping the typescript dependencies and tweaking the syntax.
The current issues known to me (at least when using ST4) are:
Due to providing generally a poor experience for the users, the ST community has decided to restrict availability of this package to ST3 (wbond/package_control_channel#8479) as the quality of this very popular package can heavily influence how people see ST as an editor and think that it is just worse editor than the "competition".
Note that there exists a much better alternative to this package which is the generic https://packagecontrol.io/packages/LSP package in combination with the https://packagecontrol.io/packages/LSP-typescript helper package. It's actively maintained, supports all new functionality of ST4 and is performant so that is the recommended way to go forward.
Assuming that there is not gonna be any effort put into fixing those issues, it would be appreciated if the package also mentioned that it's deprecated for ST4 and maybe suggest the alternative.
The text was updated successfully, but these errors were encountered: