8 ms·
Deno 2.8
- orf 4mo agoThe release post for v2.8 is not yet published. Check GitHub releases page for the latest release status of Deno.
- deleted 4mo ago[deleted]
- eskori 4mo agoBy 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 https://github.com/denoland/deno/releases/tag/v2.8.0 EDIT: Formatting
- cf100clunk 4mo agoDeno 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-2026-comparison https://www.devtoolreviews.com/reviews/bun-vs-node-vs-deno-2...
- kayson 4mo agoIt's surprising to me that bun is so much faster serving web requests. The article mentions Zig as a factor, but is micromanaging memory really gaining over 2x vs node? Similarly, it seems, though they didnt exactly say, that they're running bun with a warm package cache... What about the others? Do they have caches?
- kloop 4mo ago> The article mentions Zig as a factor, but is micromanaging memory really gaining over 2x vs node? As someone who has optimized by reducing/batching heap allocations, 2x seems within the realm of possibility, depending on the exact circumstances. That being said, iirc, node also has more hooks for things like observability than bun does, which might hurt it here
- infensus 4mo agoBun's http server is basically µWebSockets (C++ library) under the hood. You can also use it in Node via µWebSockets.js, the official bindings.
- vmsp 4mo agoI 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`.
- freedomben 4mo ago> and, soon enough, you'll be able to build your app to a single executable -- including native deps. Whoa, did not know that. That's a killer feature!
- sirsinsalot 4mo agoCode, as a single executable you say?! Whatever will they think of next?
- TingPing 4mo ago> Plus, bought by Anthropic. Who thinks this is a positive?!
- vmsp 4mo agoThat wasn't a value judgment on the acquisition. I was just pointing out that it made the project more sustainable.
- TeriyakiBomb 4mo agoIt really doesn't. You think Anthropic will still be in business in 10 years? If they are, it's not likely they'll be in the same shape.
- Sammi 4mo ago
- turadg 4mo agoThe 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 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.
- WorldMaker 4mo agoYeah, that's my immediate debate in reading this blog post: `deno pack` might be a great replacement to my existing `npm publish` workflow for my open source packages and continue shifting my work to Deno-first/Deno-mostly, but on the flipside, with Node's growing TS support I'm also considering switching to Typescript-only npm packages as a (tiny) message to the ecosystem. Though I'm also happy that JSR exists as that (mostly) cleaner ecosystem.
- Ciantic 4mo agoNode refuses to support TypeScript within node_modules, see https://github.com/nodejs/node/issues/58429 https://github.com/nodejs/node/issues/58429 this means you can't do "Typescript-only npm packages". They made that intentionally at the beginning: > Currently there is consensus that Node.js should NOT run TypeScript files inside `node_modules. It is not supported to avoid package maintainers to release TS only package.
- notnullorvoid 4mo agoIt sounds a lot like DNT (https://github.com/denoland/dnt https://github.com/denoland/dnt) which has existed for a long time, but having it in Deno cli does bring significant visibility.
- ezekg 4mo ago[dead]
- mohsen1 4mo ago> 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.
- afavour 4mo agoI actually lost interest in Deno once it started leaning into NPM. I thought it was a bold and wise idea to make a clean break from the mess of Node and restart with a sensible ecosystem. Absent that... I'm just sticking with Node.
- pjmlp 4mo agoAs someone that works in projects with standard IT tools, not supporting NPM made it a non starter for us. No way it would go through standard build pipelines, or team skills.
- ale 4mo ago"standard" IT tools?
- pjmlp 4mo agoYes, IT from customer, or agency delivery operations, dictates what are the official tools in specific projects, including 3rd party dependencies in internal repos, and CI/CD is cut off from accessing public Internet.
- afavour 4mo agoOh, for sure. But I'm old enough to remember when standard IT tools would have never supported Node in the first place and the idea of JS on the server made everyone scream. You just need to build demand for that support.
- pjmlp 4mo ago
- survirtual 4mo agoI 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 4mo agoDeno: 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.
- paulddraper 4mo agoBun prioritized Node.js compatibility. Deno since adjusted, but Bun gained a lot of market share in the meantime.
- yroc92 4mo agoI use (and like) both. Bun is a drop-in replacement for node. If you don't want to fuss with test config, tsconfig, esmodules, etc., I find that it just works. Deno has a nice standard lib, great CLI support, and I used to love deno deploy but its gotten very clunky these days.
- 3uler 4mo agoBut if you look at the node compliance tests, deno has better compliance now days…
- CharlesW 4mo agoInsanely better, at 76% Node compliance in Deno 2.8. Bun 1.3.14 is at just 40.6% with same compliance test. https://node-test-viewer.deno.dev/ https://node-test-viewer.deno.dev/
- garbagepatch 4mo agoI guess Bun had the better marketing then. I liked how every new feature came with a benchmark against the previous version and node. See this for example: https://xcancel.com/bunjavascript/status/2048228152397459590 https://xcancel.com/bunjavascript/status/2048228152397459590 I'd love to see a site comparing the 3 of them in a similar way.
- Curosinono 4mo agoI don't get it why the hell is TypeScript still not nativly supported in modern browsers?
- tuananh 4mo agoJS promise to never break the web. can't say the same about TS
- bel8 4mo agoJS can't really break the web. It's a trillion+ market. If that ever happens for some exquisite reason, it would be forked in under 2 milliseconds by the browser consortium.
- vmg12 4mo agoLikely because everybody would still strip types, bundle and minify their typescript code anyway.
- brazukadev 4mo agoit is still a DX improvement
- hollowturtle 4mo agoBecause "it doesn't exist". It's just a layer on top of js, it doesn't have its own runtime, and btw what would supporting ts a the browser level mean? If you want to support a static typed language then you could just compile it down to wasm, if you just want to support types and ignore them at runtime there's an overhead price to pay, or should do runtime type checking? And with which tsconfig? Strict or not?
- VerifiedReports 4mo agoAll good questions. But... it would simply eliminate a step and result in a single language. Python supports types and is interpreted, right?
- ale 4mo agoI 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.
- pjmlp 4mo agoIf the JS/TS SDK I get from a SaaS vendor doesn't work on Deno without changes, I am not going to spend one second to make it work.
- IshKebab 4mo agoI don't know why they copied NPM's backwards `npm install/ci` thing. Most people think that `install` does use the lock file.
- XCSme 4mo agoIs anyone here using Deno in production?
- just123 4mo agoI like Deno for the web standards. I think it should be sponsored by the government for it to flourish.
- KuhlMensch 4mo agonpm 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 4mo agoDeno 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.
- steve_adams_86 4mo ago> Works like a Swiss clock It really is such a pleasure. It feels almost like a blend of JS and Go. Fast, flexible, slightly saner package management with more powerful capabilities than other JS/TS alternatives, a better security model, better standard library (so to speak)... And very fast. I love it.
- notnullorvoid 4mo agoA 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.
- garganzol 4mo agoI somewhat agree with you. For example, in Deno v2.8 they've changed the return type of setTimeout and setInterval functions from webstandard-compliant 'number' to opinionated 'NodeJS.Timeout'. Which is a short-sighted change trying to reap immediate short-term implementation-centric benefits in the expense of the future. Pains of churn and breaking API changes are welcoming their new bearers...
- bartlomieju 4mo agoBartek from the Deno team here. Thanks for the feedback. I assure you this is not a short-sighted change. This has been a problem since before Deno 1.0. We resorted to hacks like different set of globals for user code and different for code inside node_modules/ directory. It was a maintenance headache, made global lookups super slow and was really hard to explain to users. While Web "setTimeout" might have been nice in the beginning the fact that it required additional APIs like "Deno.unrefTimer" made it worse than Node's setTimeout.
- bartlomieju 4mo agoBartek from the Deno team here. Thanks for the feedback, I understand your frustration. > 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. Since a few versions ago, Deno now has some of Node.js APIs included by default (eg. process or Buffer). It's really more of a bug fix to make type-checking work properly. While it's not ideal, you can still decide which types you want included by default with `compilerOptions.types`. `["deno.ns", "web"]` should give you what you're looking for.
- danborn26 4mo agoThe 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 4mo agoI 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.
- csjh 4mo agoIt should be pretty mature outside of Wasi. To be fair, there's really nothing that's super mature in terms of Wasi support, except maybe Wasmtime
- rochacon 4mo agoFor Python, `uv` [1] delivers a similar experience. Faster dependencies. Better dependency management with `pyproject.toml`. Just use it with `uv run` or `uvx`. [1] https://github.com/astral-sh/uv https://github.com/astral-sh/uv
- rutierut 4mo agoAs 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 4mo agoIt'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/ https://edgejs.org/
- cptmurphy 4mo agoAre you not tired of self-promotion?
- brendonjohn 4mo agoI’ve loved using deno. Full time for the last three months. Deno replaced a pnpm monorepo I was using.
- danborn26 4mo agoThe steady release cadence for Deno has been impressive to watch. Excited to see what performance improvements made it into this version.
- sombragris 4mo agoMy perspective is that of an user, not a developer. I use Deno since yt-dlp required a JS engine and recommended it. So while I don't use it for development, I have to build it for my system. This software is a beast to build and package. On first compilation, it spent like ~5-6 hours just pulling Rust crates. This time thankfully was significantly reduced once the relevant packages were in cargo caché; only the changed/added ones were picked up. But the second problem is even more annoying. Building Deno happily consumes about ~16-20 GB of precious disk space on space-constrained SSDs. This is too much. I think we should go back to more efficient software, both in object code formats (the product) as well as in the build process. Why would a single JS runtime need 20 GB storage to be built? This is wasteful.
- deleted 4mo ago[deleted]