You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've found the issue, there was a background task that wasn't running regularly enough, since the number of records has exploded since I first implemented it.
I've ran it manually for all dependents of neostandard so it should be listing them all now, and I'm going to work on improving the rate of updating dependent records.
My
neostandard
npm package still is not showing any dependents, despite being about 3 months old now https://packages.ecosyste.ms/registries/npmjs.org/packages/neostandardEg. GitHub shows dependents, and I know there are such (especially
fastify/fastify
): https://github.com/neostandard/neostandard/network/dependents?dependent_type=PACKAGEAlso, despite claiming to be synced 3 days ago, it claims that latest release of neostandard was 3 months ago, but there has been plenty of releases since: https://www.npmjs.com/package/neostandard?activeTab=versions
Maybe related: My personal superset of neostandard has seen a reduced number of current dependents as I have gone through and published new versions of the modules depending on it (maybe because they target a pre-release?) https://packages.ecosyste.ms/registries/npmjs.org/packages/@voxpelli%2Feslint-config/dependent_packages
Almost all "past dependents” of
@voxpellii/eslint-config
are still dependents, such as eg. https://packages.ecosyste.ms/registries/npmjs.org/packages/peowly(Transferred from a way too big social media message)
The text was updated successfully, but these errors were encountered: