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
It appears as though the service from which the site was getting package metadata (npms.io) is no longer being maintained.
I suggest making the calls against registry.npmjs.org, though this will require reworking some of the fields that were expected to be coming out of the "metadata" object.
Calls to registry.npmjs.org can be made as follows https://registry.npmjs.org/${name}/latest to retrieve the latest data on a package.
The text was updated successfully, but these errors were encountered:
Hi @greg-harrison, sorry for the late response here. There are a few features that npms.io give that the npm registry did not (at least before). Would you be able to perhaps submit a PR with the suggested changes?
It appears as though the service from which the site was getting package metadata (npms.io) is no longer being maintained.
I suggest making the calls against registry.npmjs.org, though this will require reworking some of the fields that were expected to be coming out of the "metadata" object.
Calls to registry.npmjs.org can be made as follows
https://registry.npmjs.org/${name}/latest
to retrieve the latest data on a package.The text was updated successfully, but these errors were encountered: