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
{{ message }}
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.
It now returns empty data with a 200 OK code, which is unsettling, to be honest. If the route is deprecated, is there a new one I can use?
I had to go diving into various git repositories and StackOverflow questions before I found this url, so I recognise it's probably an internal-use-only route or something, and I'd like to do it the proper way.
The text was updated successfully, but these errors were encountered:
The workaround for me is to use _view/byKeyword, and then hit npm once for every package that is returned (which in my case is over 300), which is really something I want to avoid doing as I'd prefer to just make a single call to npm.
Attempting to access this route used to return a JSON string that showed a list of newly published packages as of
startkey
:https://registry.npmjs.com/-/_list/index/modified?startkey=1439480888643
It now returns empty data with a
200 OK
code, which is unsettling, to be honest. If the route is deprecated, is there a new one I can use?I had to go diving into various git repositories and StackOverflow questions before I found this url, so I recognise it's probably an internal-use-only route or something, and I'd like to do it the proper way.
The text was updated successfully, but these errors were encountered: