For how we used this in Deno's repo, see this blog post david.deno.dev/posts/gagen/

GitHub - dsherret/gagen: Generate complex GitHub Actions YAML files using a declarative API. Generate complex GitHub Actions YAML files using a declarative API. - dsherret/gagen

I've published a library here that also has tooling around this github.com/dsherret/gagen

I've found maintaining GitHub Actions workflow files is much easier when it's generated from Typescript.

The latest realization is that the output yaml file can act like a lockfile. So I maintain `actions/checkout@v6`, but the generated output gets locked to a hash.

I'm also working on support for plugins distributed on npm and support for using node resolution to resolve plugins. This should help users who have IT/compliance constraints.

For the official process plugins, I was unfortunately using absolute URLs in the plugin manifests, so you'll need to run `dprint config update` to get better reliability for those.

Due to terrible GitHub availability, dprint formatting plugins on plugins.dprint.dev are now served directly instead of redirecting to GH assets.

Additionally, the plugins are now cached indefinitely by the server, which eliminates the risk of a repo disappearing.

Also released new versions of jsonc-morph (github.com/dsherret/jso...) for JavaScript, dprint-plugin-json, and dprint-plugin-jupyter, so those projects include these performance improvements.

Released jsonc-parser 0.32, which allows deserializing via serde to a concrete type. It's also much faster.

Last Monday was my last day at Deno.

It was a privilege to work with such talented colleagues.

The standard library has been my passion for years. I've reviewed all PRs since 2023 and learned a lot from them. Proud to see it often mentioned as one of the best parts of Deno.

My last day at Deno was this week. I really enjoyed maintaining the language server and working with the CLI team, and I'm sure they will keep building great things.

Looking for new work in the space of native-backed JS/TS tooling, or something new!

Yesterday was my last day at Deno.

I'm sad to leave but I'm proud of everything the team and I were able to build. I'm glad I had the opportunity to work with some of the most talented people I've met. I wish them all the best!

I'm actively looking for my next challenge, my DMs are open!

Today is my last day with the Deno team 🦕💖💔

I know they're gonna keep making awesome things.

But now *I* need to make awesome things for someone else! If you're looking for a DevRel with a JS focus and extra sparkle, get in touch!

Marvin is another lovely talented person I had the pleasure to work with who you should try and snag for your company if you can!

There's so many cool things under Deno's hood that we haven't talked about so I'll also take some time to blog or post about them soon.

It's been an incredible privilege to have been paid to spend these last five years working with extremely talented colleagues designing, implementing, and refactoring a large portion of Deno.

Yesterday was my last day at Deno. I'm going to transition from two days a week to full time on a business I cofounded in the auto glass industry. My plan is to increase my contributions to my personal open source projects and keep contributing features/fixes to Deno that I need or want.

John is an absolutely incredible UX design expert. If you are looking for someone who can come up with, implement, and test your UX flows, you should hire him.

Yesterday I updated my bio as I'm no longer with the #1 🦕-themed javascript company. I'm sad to go but excited to see what's next.

I've spent the last few years designing exclusively in code, building agent skills, working on command-line tools, and crafting dev docs experiences.

Hit me up.

Snap him up

Also merged a perf improvement to the sharp pkg's install script. Once released, it will make all pkg managers faster installing Next.js with lifecycle scripts when brew is installed (except Bun because it overrides the maintainer's decision and always skips the install script)

I've wanted this for so long - and @kettmeir.dev has finally implemented it!

View changes in the public API of packages between versions:
- what methods were added, changed (type signature), or removed

In the future we could even indicate if you are about to publish a breaking change

dprint init
dprint config add oxc
dprint config add biome

...along with various other formatters.

dprint's incremental formatter is incredibly fast and happens without needing an opt-in.

You can use both oxc and biome via dprint for faster performance.

The 2/0 is a little strange, but overall it's better.

It's good npmx.dev shows git and https dependencies. I still think it's crazy npmjs.org doesn't.

I didn't want a terminal based solution, so I vibe coded a desktop app to give the status of all my AI sessions regardless of where they're running and I can click to quickly jump to them.

Great to hear! It will be better for the ecosystem in the long term.

Additionally, pnpm 11 will block dependencies from exotic sources (like Git) in subdependencies.

Re config: I'm not sure what it should look like since there's so many variations on what a git dep could be. I'm thinking opt-in for all git deps or opt-in for a specific url git dep because there's so many variations on what the url could be I think.

It would also be hard for security tools to scan because the git/https deps can change.