> I also think there is a benefit to a team using the same editor for a project. I'd love to be wrong, though, and see an example (blog post, youtube, whatever) of Sublime working for TypeScript development with all/most of what VS Code offers out of the box (even if it involves some configuration steps). So, maybe I'm doing it wrong, or maybe it doesn't work. I mean it didn't highlight errors in TypeScript as a typed them, and 'go to definition' didn't jump to the correct definition, but rather offered me a list of every place in the project where a symbol with that name was defined (including the correct one, but also several incorrect ones).) restarted Sublime Text 4 (just in case) use that to install Package → LSP-typescript However, since we are in the thread I googled it with, and then followed the top blog post results, which involved: Not really trying to criticize it just noticing that it doesn't work out of the box, and I personally have never had the time to fiddle with it to see if it can be made to work. I'd be happy to find that I'm wrong about that, though.Ĭool.

There was a lot I liked about Sublime back in the day, but I felt like it just failed to keep up with the basic-level state of the art for a code editor. But are you saying these features can now be made to work in Sublime (perhaps with some configuration, or something)? To me, these basic features are table stakes for an editor in 2022, and should hopefully 'just work' if you open a TypeScript file. Unfortunately, while it did offer to autocomplete the titleId property, that property is from a completely unrelated class to Hoge that isn't imported in the current file (but I can see in the hover popup where it Sublime is getting the definition), and also that property is a string, but Sublime lets me go ahead and assign a number to the property without flagging it as an error. I just fired up Sublime Text 4 and opened a vanilla Angular project to try the TypeScript support. It's interesting you mention LSP support, because that is basically why I stopped using it - the as-you-type auto-completion, error/warning highlighting, and doc/reminder/hint functionality was sorely lacking (compared to leading non-native editors like VS Code / Jetbrains). I bought Sublime Text through v3 but didn't really use it anymore, so declined to buy v4 (so far).

Best text editor for mac os x