Ask HN: Why is Emacs-lsp TypeScript integration so far behind VSCode?

I've been an emacs user since college with my first foray into common lisp, and over the years, I've exclusively worked with a souped up .emacs config based on prelude for Python, Rust, and Clojure.

However, I've found it really hard to set up emacs-lsp with Typescript to even remotely match what VSCode offers.

For instance,

- Auto linting

- Auto import of mentioned modules

- A reasonable auto-complete across modules

- A mechanism to see code definition in different sections of a monorepo

(I've messed around with tide, emacs-lsp config, a lot [1]).

Is this an issue with emacs? Or with free contributor times vs paid microsoft engineers? Is anyone using emacs with lsp for typescript and has pointers to a .emacs config?

[1] https://github.com/viksit/prelude/blob/master/init.el