However, this is not the case for companies (perhaps due to strict corporate rules about software and software updates). Many companies often use outdated software or surf the web with outdated browsers, which also affects HTML and CSS, in addition to programming languages that have to be interpreted by their respective browsers and are therefore highly dependent.
About a decade ago, nothing was happening in the browser for a long time, which is why Bundler came along with transpiler. Even though you were using a JIT (just-in-time) compiled programming language that could execute properly, you always had to deal with a complex build process to convert source code to actual code that could then be executed and interpreted in the browser (which was the case about a decade ago).
The Rise of TypeScript
Now, ten years later, the world has changed. While those browsers that are not updated are still “alive”, they play a much smaller role today than they did in the past.
This makes bundler unnecessary, at least from a technical point of view. bundler is just one more step in optimizing HTTP requests so that fewer small files can be loaded from the server and only a few large ones can be loaded. At the same time, the build process will gradually become simpler or more irrelevant.
In other words, Microsoft or TypeScript has suddenly gone from a very useful tool to a rather “annoying” thing. In response, Microsoft says they don’t want to be a hindrance; instead, they want to inspire developers.
Also, TypeScript is now a more complex programming language, and Microsoft does not want to integrate all the features of the TypeScript compiler directly into common web browsers. That would be a very complex task that would require the cooperation of Apple, Google, Mozilla and others to integrate a big new standard.