Supporting TypeScript at runtime is just encouraging more runtime bloat.
npm packages are a mess. It's not uncommon for 95% a package's footprint to be unit tests, documentation, or other crap someone decided to publish, but serve no runtime purpose. On top of that, files are loose on the file system, causing more waste due to slack space.
If you're going to fix the mistakes of node.js, look at what java did right 25 years ago. Support optionally running packages from an archive, and have developers publish their runtime separately from their SDK (source code, etc.).
Biting the hand that feeds IT
