In the Deno repo, we have a custom Rust test runner for our tests in order to support file/directory-based tests and improve stability on the CI. I just refactored the code to have a pty reporter that surfaces some useful information. It seems better than having failures whizz by.

Did something fun; used @tinygo.org to shove @mvdan.cc's wonderful gofumpt into @dsherret.bsky.social's amazing dprint formatter via a Wasm plugin. We previously used an "exec" plugin to do this with go tool, but it was slow to run, and worse in parallel (and... Windows 😑). Now it's fast!

The next Deno release will include Node type declarations out of the box.

In his talk at #EuroRust25, @kettmeir.dev shared how the @deno.land project improved error handling by migrating from the anyhow crate to using thiserror and concrete error types – watch it on YouTube now! 🦀 👉 youtu.be/f6eofqicw_s #RustLang #RustConference #EuroRust

Wrote a library this weekend for modifying JSONC files david.deno.dev/posts/jsonc-...

Stuck in an elevator with @snek.dev, @littledivy.com, @bartlomieju.bsky.social, @magurotuna.bsky.social, @dsherret.bsky.social, @kettmeir.dev, and Nathan

🌟 Speaker Spotlight: David Sherret @dsherret.bsky.social will walk us through the JSR package registry: why it exists, how it improves on previous approaches such as HTTPS specifiers, and the design decisions behind its module resolution. Schedule, speakers & more info: squiggleconf.com

Importing bytes and texts: ✅ adds to your module graph ✅ type checking ✅ works with deno bundle and deno compile deno.com/blog/v2.4#im...

Type checking text and bytes imports is now working.

Should have importing files as text and bytes ready for Deno 2.4 -- will be unstable because it hasn't been standardized.

This is now published to JSR as a rolldown plugin: jsr.io/@deno/rolldo...

Got bundling JSR/Deno code with Rolldown working. This is using Rolldown's and Deno's crates respecting Deno's lockfile, config discovery, and resolution. Finally Deno's crates have been refactored enough for this to be feasible (~500 LOC). I'll update with more details later.

I've come across so many bugs caused by using wildcard matches in Rust. Even though it can be verbose, I think it's better to avoid them in most cases so that adding a new enum variant causes compiler errors, forcing you to re-evaluate each match.

It was getting difficult to debug Deno's npm resolution so I wrote a tool to help visualize each step it makes.

My closing keynote from Rust Nation UK last week is now online: "Microsoft is Getting Rusty: A Review of Successes and Challenges"

Neat to see software I used to work on and features I helped implement in Severance.

Lint plugins are now available 🎉

Beware: npm doesn't show non-npm dependencies in the dependencies tab. Check out this package—npm lists it as having zero dependencies, but if you look at the package.json, it definitely has dependencies.

Did some work on the url Rust crate the past two days and got it parsing a 400 character URL more than twice as fast (still have a few PRs not merged).

I feel like making node resolution "just work" leaves the JS ecosystem in a worse place.

@jsr.io is now openly governed — meet its board members and check out its governance charter 👇 deno.com/blog/jsr-ope...

TypeScript <5.7 on left, TypeScript 5.7 on right. Glad this seems to work lol. Anyone have a better solution for dealing with Uint8Array being generic now?

Worked on this slowly over 5 months, but Deno's config discovery and module resolution logic has been extracted out of the CLI and into a re-usable crate (not yet published). Also a few days ago this setup code was hundreds of lines, but now it's only a few.

Wasmbuild is getting simpler thanks to Wasm imports.

Recently I've started using a different approach to pre-allocating strings in Rust.

After many years, we finally have control of the deno package on npm. Thank you, GitHub! Now to get it all wired up and distributing the Deno executable...

So in @deno.land 2.1 you can directly import WASM. That's pretty cool... but they also automatically generate typescript types for the WASM. Pretty wild... here's how they do it: github.com/denoland/den.... Uses this crate: github.com/denoland/was.... @dsherret.bsky.social, you do good work.

It's been a few months so let's bring this up again with an example of what other languages do—unawaited async function call detection is standard in other languages, but missing in TypeScript. So many bugs could be prevented if this were built-in and didn't require separate tooling.

Fixed a performance regression in Deno's shutdown time on Windows. We were accidentally doing a lot of WebGPU stuff on every run.

Demo of Wasm modules in the upcoming Deno release. It has type checking and editor support.

Respecting "type": "commonjs" in a package.json is going to be stabilized in the next Deno minor release next week. When there's a package.json with this, Deno will determine the module kind of ambiguous file extensions (.js, .ts, .jsx, .tsx) by inspecting the contents of the module.

The upcoming patch release of Deno uses 2.3x less memory than Bun running the compiled executable of this example on Windows (70 MB vs 160MB after 60 seconds).

jsonc-parser 0.26 introduces a first-class API for manipulating JSONC files in Rust. david.deno.dev/posts/jsonc-...

📣 Discussion for review! Seeking inputs: we'd like to shift the DefinitelyTyped repo to using a dedicated formatter for formatting (instead of lint rules). This is a proposal for why & how. Post input if you've got it, please! 🤝 https://github.com/DefinitelyTyped/DefinitelyTyped/discussions/65993

I've been working on a build tool for Deno libraries where you specify a TypeScript entrypoint and it outputs a single .js and .d.ts file (using swc) with the dependencies kept external. At the end it runs integration tests on the output. Still lots of work left to do on it though.