You overestimate many of these difficulties. The --compat mode can already run quite a bit of the node ecosystem, including programs like npm. Imports don't ne

You overestimate many of these difficulties. The --compat mode can already run quite a bit of the node ecosystem, including programs like npm. Imports don't need to be written in typescript. They could have manually written type definitions (which is how people using typescript in the node ecosystem already handle this), and packages without type definitions will have the imports typed as `any`. Sure that makes them a bit annoying to handle especially in strict mode, but it entirely possible to use such packages. Deno is actually working on adding the native node API (https://github.com/denoland/deno/pull/13633 https://github.com/denoland/deno/pull/13633), so the website was a bit overoptimistic when saying "Deno will never support Node plugins". However it is possible for some plugins to be incompatible still, for example if they try to use node internals rather than just the API, or if they try to use utilize the libuv event loop, since deno is not libUV based.