import {} from "some/package"
And then go back with working autocompletionThey won't do this without consensus in TC39. They shouldn't either; that'd be worse than this niggle.
If I said language foo that isn’t TS but transpiled to JS all the same was considering that syntax, people might have a different opinion.
Between that and some remaining warts from <1.0 mistakes/incorrect assumptions, there's plenty of evidence that it is a good thing that other than its type system TS focuses on following standards rather than trying to lead them.
There's a place for the language "foos" that want to lead and champion new standards. As an ecosystem we all seem to benefit from Typescript not being that language (anymore, mostly not since 1.0 with the few obvious mistakes aside). It's a part of what makes Typescript trustworthy as Production tooling. It's also what helps make Typescript mostly "cheap" and "unextraordinary" in Production build pipelines.
Not a two world reality where the guest language has its own mini-platform and tooling, on top of the actual platform.