David Sherret

Thanks! Just a fetch then find and replace. It’s pretty hacked together 😅

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

Poster for SquiggleConf 2025, September 18-19 Boston JSR: Designing Package Registry Module Resolution David Sherret, Deno Developer; creator of ts-morph, dprint-ts-ast-viewer

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

They recently landed these methods to ReadableStream that haven't standardized yet: github.com/whatwg/strea... (I want those methods too, but it's not standard)

Yeah, essentially just `node.text += "?bytes"`. I'm pretty sure it's going to break when TS does some refactorings, but I'll deal with fixing that in the future.

We use TS via the API so we can resolve specifiers based on their location. That said, once resolved, TS will cache the lookups keyed by specifier and node resolution mode only (github.com/microsoft/Ty...). To work around this, we trick TS into thinking each import attribute is a unique specifier.

Type checking text and bytes imports is now working.

We're probably going to do it later to improve node compatibility, but JS loaders are not so great because it creates a decent amount of extra complexity, is slower, and is not as portable or standard.

Couple things: github.com/whatwg/html/... github.com/tc39/proposa...

Also, probably waiting on github.com/tc39/proposa...

Importing a module as bytes and text with a dynamic import.

Yup.

Importing a file as text and bytes with an import attribute.

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

Oof that's terrible. Sorry to hear!

I skip stairs going down. I've wondered when and how I'll find out I can no longer do that.

bsky.app/profile/dshe...

It's very untested and probably won't work in many scenarios, but it's a start. Bugs can be reported here: github.com/denoland/rol...

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

Terminal output showing a JSR specifier being bundled to a single file then executed. > ../rolldown/target/debug/rolldown_deno.exe jsr:@david/dax@0.43 Bundle jsr:@david/dax@0.43 Writing: dax.bundle.js Writing: dax.bundle.js.map > deno Deno 2.3.5 exit using ctrl+d, ctrl+c, or close() REPL is running with all permissions allowed. To specify permissions, run `deno repl` with allow flags. > import $ from "./dax.bundle.js" undefined > await $`echo 'Hello there!' && echo 'This is from a bundled copy.'` Hello there! This is from a bundled copy. CommandResult { code: 0 }

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.

That sucks! Sorry to hear that :(

This is crazy and I'm sorry to hear. I hope you'll find a way to continue contributing to the ecosystem.

Nice. Thanks!

I've only found rust-lang.github.io/rust-clippy/... which seems to only error when there's a single variant left and not multiple.

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.

In the past I did something similar for dprint here... basically if there's a graph then it's almost always useful to have an easy way to visualize it: x.com/DavidSherret...

Deno's npm resolution uses a one directional graph and maintains a reverse path through the graph for where it's currently resolving (shown as the red line).

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

I think there needs to be something more restrictive that allows for doing isolated work in parallel while having native and js (non-parallel) targets. I was thinking about this earlier and did a bit of work exploring. The problem is use cases are small.

YouTube video by Rust Nation UK Microsoft is Getting Rusty: A Review of Successes and Challenges - Mark Russinovich

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

Also, this was C# WinForms. While there I created a development only ctrl+i tool for inspecting/modifying controls at runtime that I was quite proud.