Deno is making it easier to move from Node to Deno in various ways lately, but it has its own philosophy (use web standards, don't adopt ideas/technologies from

Deno is making it easier to move from Node to Deno in various ways lately, but it has its own philosophy (use web standards, don't adopt ideas/technologies from the past that turned out to suck, etc) so I don't think they are aiming to be able to replace Node for every use case with no changes to your code. With TypeScript 5.0, though, it has become a lot easier to have a large monorepo full of TypeScript code that works with Node programs, Deno programs, and web apps / code that runs in the browser. We still use Node a lot at work, but Deno is getting more use as it is generally a better experience. But that's not really a function of it getting "closer" to Node; for the things I care about, Deno is typically somewhat different to Node, but better. (Haven't used Bun yet myself; it's still a bit too new for me, and not yet cross-platform.)