We've been running daily scans across 17 repositories to understand how automations are shaping the GitHub ecosystem: tracking which PRs are AI-driven and how effectively teams are closing them. I cannot thank @graphieros.npmx.social enough for all his contributions.

today is a great day to set up a mirror of your repositories

I've been using @npmx.dev a lot in the past days to handle a bunch of updates on a project with a lot of outdated dependencies. Can't stress enough how good it is, great work to everyone involved 👏

atproto is growing at such a healthy rate lately

We build surrounded by folks that care. About what we do. About why we do it. About how to do it. About others.

what are we even doing?

No HTML Canvas. Just CSS on transformed DOM elements. And it runs at 60 FPS. My brother continues to prove me wrong. In my defense, browser folks have created absolute rendering engine monsters. How is the web rendering pipeline of modern browsers this performant?

Update: SvelteKit has shot up from #10 to #6, with #4 just within reach; @vite.dev has stolen the #2 position from @nuxt.com; @svelte.dev's lead has grown and appears increasingly insurmountable 📈.

Happy Pride Month! Thanks to everyone who, despite everything, keeps working together to build a more welcoming and inclusive web 🌈

happy pride month 🎉

Building this integration has been amazing opportunity to dogfood all APIs we've added into @vitest.dev in past years. It's using features like new Reporter APIs, Vitest plugin hooks, browser commands, CDP, test tags and much more! Vitest is definitely one of the most extensible JS tools out there.

Love has always won and will always win, no matter how much they try to convince us otherwise Happy pride month ❤️

If @vite.dev is going to be third, I'm more than happy to see @svelte.dev and @nuxt.com be the ones at the top of the npm podium. Keep showing the frontend world how fun it can be to do some good old websites, you awesome frameworks 🙌

Finally took the time to donate to two OSS projects I genuinely rely on: @npmx.dev and @e18e.dev. If you've been meaning to do the same for a project you love, there's never a bad time to give back.

If you've published a package using staged publishing before this fix, all that's needed now is to re-publish the same package and @npmx.dev will display the trusted publishing label again 🤝

This is how you play when you care about real adoption. Incremental evolution. Keep as much as possible from the current iteration. Focus on the big wins you offer. Listen and meet devs where they are. There will be time later for other steps. Bullish on TSRX if they keep this pragmatic approach.

Has anyone spotted this new badge in the wild yet on @npmx.dev? It can only be found on a select few packages and leads to something whimsical. But which packages? Obviously it's the ones wi◼️◼️ ◼️◼️◼️ ◼️o◼️◼️ ◼️◼️k◼️◼️.

If you're feeling burned out because your motivation is fading due to today's tech news or your job, join communities like @npmx.dev, @e18e.dev, and other OSS projects to get your drive back. Stay away from AI agents and interact with real people. It's one of the best things that happened to me.

it’s a bit embarrassing to admit, but when people ask me for examples of sites built with nuxt, i often can’t remember 😱 👉 so i am building @nuxt.fyi (still in construction!) it listens to the @bsky.app firehouse for links, then scans them to see if they were built with nuxt

this is always the hardest part

Hungary named someone I know as state secretary for water and climate. Amazing that folks like her are now in charge. Still hard to believe the sea of change that's coming here.

I found the box of font cylinders during spring cleaning. I wonder what stories they helped spread.

if you want to predict the long-term growth of an open source project or open protocol, check the evolution of its ecosystem, not its usage statistics

Take the time and give some flowers to a maintainer today. Send them a gift of a dinner with a loved one. Or reach out to let them know you appreciate what they do and that you're there if they ever need it. Show them the humans on the other side care.

find community, don't let them isolate you

here we go again

forget about npmx, this is the future of package browsing

console.log("happy birthday, @nodejs.org!")

Or optimistic takes on the future of open source and online collaboration

Very excited to share that I work here now! Starting today I'm one of the newest @bsky.app employees. I'm stoked to be exploring the Atmosphere full time! 😎

In @npmx.dev you can now view a package's changelogs currently only package's that use Github to host their releases or changelog.md are supported but support for others are planned

the @e18e.dev npm publishing guide has been updated to recommend the new `npm stage` feature! this guide and the templates it offers are a good way to get setup quickly in a secure way

I'm working alongside @ledeluge.me on PolyCSS: a new CSS 3D engine for the DOM. It uses matrix3d() transforms to render polygon meshes as HTML elements, without WebGL. demo: polycss.com/gallery/?mod... repo: github.com/LayoutitStud...

The pnpm e2e tests now use a "pnpm registry" instead of verdaccio. In the future we'll make pnpm faster with this registry.

make sure you tell your friends you love them

We’ve been working on a new site for Changesets with a lot of new docs! If changesets has been confusing before, hopefully some of these will help, or let us know what else could be improved. Check it out 👉 changesets.dev

good time to be around hungarian rivers

Rolldown is now available as Rust crate and will be published continuously there in addition to npm. crates.io/crates/rolld...

PSA: the safest way to publish an npm package today is staged publish + OIDC + provenance. "But it can't stop every attack." Sure, and seatbelts don't prevent every injury either. We still wear them. Security is layers, not silver bullets.

Made my first contribution to @npmx.dev. What a great community that is 💚

good time to be around hungarian gardens

this is what open source is all about 🤍 > Looking back at this past year, it’s crazy how much has changed. From my very first small PR to becoming a maintainer in multiple projects. I’ve learned that communication is key in Open Source, and when people work together openly, incredible things happen

the replacements.fyi site now lets you drop a package.json into it to see which dependencies can be replaced with native functionality, or more performant choices 🎉

My first blog post. I finally finished it. blog.rman.dev/year-in-open...

This might be what vexes me most of the unforced GitHub Actions minefield. Commenting on PRs is PUBLIC. Any registered account can do it without permissions!! And yet if you want an automation to comment, you’re encouraged to run it as a privileged, dangerous pull_request_target job.

story of my life, every single day: she - could you go help build a walipini at the kids' school on Tuesday morning? me - ya, from 10 am should work she - nice, I'll add you to the parents' list me - cool, what is a walipini?

Uh, this is way more interesting than I expected. If you'd like to get involved and help on the war against the machines, raise your hand. It should be quite a enjoyable project to participate in.

Critical mass is already here — it's just not very evenly distributed.

OSS batsignal. I feel like @danielroe.dev is describing literally all maintainers.