This repository has been archived by the owner on Aug 23, 2018. It is now read-only.
DependedUpon endpoint consistently returns 404 #361
Comments
Haroenv
referenced
this issue
in algolia/npm-search
Jun 27, 2018
(will fail since dependedUpon is 💔) https://github.com/npm/registry/issues/361
Haroenv
referenced
this issue
in algolia/npm-search
Jun 27, 2018
npm is currently serving us 404 for it (see https://github.com/npm/registry/issues/361) Removing this is the only solution for now. This will cut down the amount of logs we're doing, and will also make CI green again. We can revert this commit at a later date when the issue is fixed on npm's side.
Haroenv
referenced
this issue
in algolia/npm-search
Jun 27, 2018
* chore(dependents): remove the data fetching npm is currently serving us 404 for it (see https://github.com/npm/registry/issues/361) Removing this is the only solution for now. This will cut down the amount of logs we're doing, and will also make CI green again. We can revert this commit at a later date when the issue is fixed on npm's side. * fake only by adding 0 in all cases, not removing the keys
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
As said in #231, there's no official API to list package dependents, I use the
https://registry.npmjs.org/-/_view/dependedUponendpoint to get the dependents of a single package.Apart from the fact that it would be nice to be able to do an arbitrary batch of dependents (less requests for you too), it seems like I'm getting 404 for any call to that URL, since at least 4 days ago
You can see this too even with the
npm-depend-uponpackage using that same endpoint:https://runkit.com/embed/kjyf601bcai1
The text was updated successfully, but these errors were encountered: