Maybe it was the aws outage today?

For sure, Ive tried to recreate the API calls from the site, but the feed it shows is by latest published now it seems

My use case is here, but my expensive query was a modified version of what is in the readme

github.com/jonchurch/to...

I know @e18e.dev has mirrored some data, what are yall doing to query the ecosystem relationships?

I got most of what I wanted for a specific package, but npm registry data access just doesnt exist anymore and has been lacking for a long time.

This bigquery dataset is still the best way I know to do this, and it still doesnt give me everything I need.

Im asking for a goodwill credit 🤞as I just didnt realize running my simple focused query less than 10 times could spend that

But ultimately there’s no good way to do this research today that Im aware of

I need to process whatever all I signed up for

Aye, what Ive been working on is a change monitor.

Takes a list of packages to watch, alerts when any changes occur at the registry. Maintainers add/rm, version add/rm, dist tag changes, lifecycle scripts change between versions etc

To solve for knowing if any of your pkgs had a sneaky publish

Whats another copy of Robocop into the pile eh?

They prolly dont want you to, but you could always offload dupes to @redlettermedia.com hehe

If you renew your vows, any plans to have a pelican riding a bicycle in the ceremony? 😉

Theyre using ArkJS instead of v8, so likely they want to ensure compat of packages devs want to run in their ecosystem.

The ask is not clear, but an uncharitable take is that they dont want to maintain forks that allow for running under ArkJS, or at least want to smooth adoption via docs per pkg

On their profile, 190 issues opened of the same format recently, with other maintainers scratching their heads

github.com/wshixjrnjr

It looks like an unfortunately planned outreach campaign for a huawei developed open source project

We can’t, we don’t know how to do it 😢

Welp, first casualty.

Some systems are running node with readonly process, so this crashes out.

I used it to get around portability issues that I still dont fully understand with the pnpm global script shim

#!usr/bin/env -S NODE_OPTIONS=foo node

Wasnt working

There’s Duo Duo Orchard where people use loyalty points in the form of “water” to water a farmville esque tree. When it matures, they get a box of fruit shipped to them as a loyalty reward