Typescript (the compiler), documentation, etc. as a language is pretty darn good. It could have more production ready examples, tutorials, and paths (I'd recommend a look at Microsoft's ASP.net Core tutorials which cover production-level material).

But as I said the problem is Typescript inherits the whole mess of bundlers like Webpack and Gulp because they are REQUIRED to make any of it work in production. Ideally Typescript would own the entire bundler step - the closest example would be .NET owning the LINQ and Identity tools/libraries to make the .NET experience so much better.

dealing with different JS environments, getting imports right, importing Vanilla js.

ie. if i am building an electron app, we have atleast 4 different JS environments (UI thread, background thread, web worker, nodejs worker, nodejs-fork, test-runner environment) that all have different levels of compatibility with different JS standards.

importing and exporting libraries in mixed mode is the worst thing about JS, bar none. The amount of obscur errors one needs to deal to get a debug-source-code-stepable pipeline up and running astounding.