RT @SquiggleConf: 🌟 Speaker Spotlight: David Sherret. @DavidSherret will walk us through the JSR package registry: why it exists, how it im….

RT @deno_land: Importing bytes and texts:.✅ adds to your module graph.✅ type checking.✅ works with deno bundle and deno compile. https://t.….

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.

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

This is now published to JSR as a rolldown plugin:

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 had copilot disabled since the beginning of the year though because it makes running `cargo build` way slower due to it watching the target directory and then fighting with cargo (there's an open bug).

No more dealing with this lol

RT @bentlegen: 👋 Some news! I've started a software company. Headquartered in Toronto. We're building a product to augment devs for the ne….

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:

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.

RT @MiTypeScript: Doom now runs in @typescript types. What a journey this one's been.

RT @jexia_: now uses `deno.json(c)` for module resolving when importing modules from Github, which allows you to im….

Another reminder that the npm client just installs dependencies from anywhere:

I submitted this in a report to npm, but it was closed as being an intentional design decision. Previously I submitted a report about how the dependencies tab showed these dependencies as being npm packages (not remote ones) and I guess the fix was to just not show them at all.

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