Deno: has a basic permission model that is very helpful, written in Rust, and native TypeScript support.

I'm not deep in the webdev / node / Bun ecosystems, I've just been a happy user of Deno for small services for several years. Can someone explain why it sounds like there's such rapid growth of Bun? Is it just being used as a bundler, but not as JS runtime?

Just the permission system alone (though I wish it extended to modules) is so compelling with Deno that I'm perplexed at why someone would transition from node to bun and not node to Deno.

I wonder how Deno's faring.

Node's the stable solution and will be with us forever. You can now use TypeScript with it and, soon enough, you'll be able to build your app to a single executable -- including native deps.

Bun's chaotic but, nonetheless, it's _fast_ and it's taking an interesting approach by including everything in the stdlib. Plus, bought by Anthropic.

Deno had an awesome story with the sandbox and ease of import for third-party dependencies. Sandboxes feel pretty commoditized now and I'm not sure the import mechanism ended up being that much nicer than a `npm add`.

The new *deno pack* command is a nice addition for safe and simple packaging.

For those using Node.js, a similar single command is available with https://www.npmjs.com/package/ts-node-pack

Now that Node.js supports importing .ts modules, more repos can use them without a build step or putting any build artifacts in the checkout.

Deno is a JavaScript and TypeScript runtime, for those who don't recognize the name. Here's a review of Deno 2.6 vs competitors Bun 1.3 and Node.js 25:

https://www.devtoolreviews.com/reviews/bun-vs-node-vs-deno-2...

npm by default: When I tried Deno ~1-2 years ago - I immediately shinned myself on this and decided to wait for more sensible defaults. (I've not followed closely, just the basic story)

And reading the features, I'm impressed! - I spot many commands & features that map to my workflow.

Well done Deno team.

I wrap most node-isms and use deno as the runtime. Works well. If a project is pure typescript I just have deno run it. Extra options for security are great, installation scripts disabled by default, etc.

If you're using node directly, please stop. At a minimum use Bun.

With agentic work, there is little reason to use anything besides Rust and Typescript in any case. Room to disagree but type safety, memory safety, and a large corpus of work is critical. Agents need difficult errors and baked in patterns they navigate it easily. For UI, Typescript makes the most sense just because of the mass of design examples.

Is anyone here using Deno in production?

I think if Deno had held on to their initial values for a little longer the pressure towards node compatibility would have been mended by AI agents, because a lot of the pressure is the result of skill issues: if the only way you know how to set up is using express.js then any subsequent tool or runtime must provide a similar abstraction for a “smooth” transition, regardless of how bad the first solution was in the first place. Nowadays you introduce devs to new tech by delivering your product with a set of skills that in practice have replaced documentation and sometimes can be very good at showing better alternative approaches to whatever you’re building.

By the time I read this, the blog post doesn't exist yet:

> The release post for v2.8 is not yet published.

> Check GitHub releases page for the latest release status of Deno.

The release is here: https://github.com/denoland/deno/releases/tag/v2.8.0

EDIT: Formatting

I like Deno for the web standards. I think it should be sponsored by the government for it to flourish.

The release post for v2.8 is not yet published. Check GitHub releases page for the latest release status of Deno.

I don't get it why the hell is TypeScript still not nativly supported in modern browsers?

> Deno now defaults to npm:

This is an interesting development. npm after all is the de-facto ecosystem and leaning into it makes sense.

I'm wondering how Deno would've been received if it supported npm and package.json from day 1.

I don't know why they copied NPM's backwards `npm install/ci` thing. Most people think that `install` does use the lock file.

[dead]