Typescript is a decent language, but severely suffers from the javascript compatibity. On the frontend that does not matter as much because you usually don't deal with critical data persistence, but on the backend it's different.
If what you said was true, Javascript would have already taken over the backend, but it hasn't. There are two reasons why:
1. There are still languages on the backend that are more productive / powerful / mature than typescript.
2. On the frontend side, the hurdle of getting into things is much lower. That's why, on average, folks working on the backend are usually more involved and have a broader exposure the languages.
That being said, there are surely languages, I would love to see replaced by Typescript (for example looking at you, Java). And while it might look like Typescript could do it from someone who uses it for frontend, I'd say it won't happen.
The point of TypeScript is it extends JavaScript in a backwards-compatible way and still compile down to JavaScript which will run in any browser. It cant make the quirks and design mistakes of JavaScript go away, but it can protect the developer against them.
But on the server side there is no compatibility issues, so why not just use a well-designed language in the first place? C#, Python, Go...all of them are much better designed than JavaScript.