What I Wanted to Do
Listening to the http://replicate.npmjs.com/registry CouchDB stream to process new package versions being published.
What Happened Instead
It appears over the past couple of days tens of thousands of events have been added to the stream and many of them are out of order (based on modified dates) from extremely old packages. For example, here’s a recent event:
These packages are extremely old and haven’t had any changes in years, yet are showing up under new sequence IDs despite the docs appearing to contain no changes from the previous (year’s old) versions. Are there any issues with the replicate stream at the moment that would explain this behavior? Did npm take any bulk operations that would have dumped all of these old packages back into the replicate stream as new events?
Simply listen to the CouchDB replicate stream.