The opposite would have similar constraints.
The only practical way that a script can run on both Deno and Node.js, without pain and without adapting the code, is that if uses plain JavaScript.
Suppose you want to build a portable app to run on both Node.js and Deno:
- In short, standard libraries are not portable, so you'll have to rely on portable external libraries, or modularizing your app so that you can plug in the components. Imagine dealing with that.
- 3rd-party libraries must also be portable. A lot of Deno libraries, if not most, are written in TypeScript.
- For practical reasons you'll have to choose JavaScript over TypeScript. Why impose such restriction if one wants to use TypeScript and get benefits of it? Also the Deno community is very strong with TypeScript.
A system in the real world cannot scale with these restrictions.