Post

Fun fact about the NPM replication feed. If you just follow the feed to get updates for ever package, you will miss packages because they retroactively insert changes in the *past* of the feed.

I suspect that this happened when NPM transitioned from CouchDB to Postgres. They kept the CouchDB replication feed protocol but it was no longer consistent.

People have been reporting this since 2025 but no official response: github.com/orgs/communi...

github.com`npm replication API` changes and migration guide · community · Discussion #152515Overview As part of our ongoing improvements, we are making changes to our replication API services. This is to ensure availability and performance of our feeds. Moving forward, only a limited set ...

7/10/26, 11:19 pm0 reposts2 likes

So to accurately replicate NPM, it's not enough to follow the 'sequential' feed, you also have to go back later to see if you missed anything. 🫠

Evangeline Rome 🌵🦎🌱🐢🐍🐸 🥦

@evadeva.bsky.social

yooo This is super, super sad. And a very important thing to note for the designs I considered here

github.comWarn packagers about files with multiple identical paths in their package tarballs · Issue #3223 · npmx-dev/npmx.devDescribe the feature Today I discovered and fixed a bug in Bun's package publishing utilities: oven-sh/bun#41291 We know that neither the TAR standard forbids nor does NPM itself reject such archiv...