Deno 2.8

orf

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

eskori

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

cf100clunk

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...

vmsp

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`.

turadg

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.

mohsen1

> 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.

survirtual

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.

dan_rock_wilson

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.

Curosinono

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

ale

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.

IshKebab

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

XCSme

Is anyone here using Deno in production?

just123

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

KuhlMensch

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.

garganzol

Deno rules, I write some tiny and mid-size web services using it. Works like a Swiss clock, the project ideology is well aligned with the Unix sprit. In my personal opinion, Deno authors are a bit humble. For example, when grateful users offer donations to the project, the authors politely decline them. I understand why, but at the same time it may create unneeded monetary pressures on the project in the long run. What can work reasonably well is a shut-up-and-take-my-money monthly subscription for users depending on the project long-term success.

notnullorvoid

A lot of these changes seem geared toward adopting Node/NPM default DX. To the point where Deno DX (or what it was previously) now comes second. The worst of the changes is "lib.node included by default", if I'm writing Deno or web code I absolutely don't want node types included by default. Those types were a pain to deal with even in Node projects, resulting in multiple tsconfigs to avoid those types polluting platform agnostic or web code. If Deno continues this trajectory then there is less and less reason to use it over Node.

danborn26

The continuous performance improvements in Deno are really impressive. Node compatibility getting better with every release makes the transition a lot easier for existing projects.

danielcasper

I literally just discovered Deno today. I wish there was Deno for Python / WASM path was really mature. Maybe I'm missing something here, but trying to secure both a Python runtime and JS runtime for AI.

rutierut

As someone who has used Deno on multiple hobby projects, I’m convinced Deno is where the JS ecosystem should be heading. Professionally though, it’s complicated recommending it outside of specific and mostly tightly scoped use-cases. At some point the project just changes direction because of business reasons and you need node.

syrusakbary

It's great to see that since the release of Edge.js [1], they started to take Node.js compatibility more seriously (they went from ~40% to about 75% in just 2 months, so either coincidental or not this is clearly a step on the right direction). Good work to everyone on the Deno team! [1] https://edgejs.org/