-
-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Package Metadata URL May be Deprecated #7
Comments
@destroyerofbuilds Would you be willing to open an issue on their issue tracker, per recommendation:
|
@sindresorhus I can do that, but it may be a little longer before I have the time. Though, I did start to go down the rabbit hole when I was wondering if we could just use the However, in attempting to use the same URL generated as part of this project's tests ( Now I'm wondering if they removed the |
Yeah, I can confirm it no longer works. It did use to work though. Ugh... Funnily enough, this works: https://skimdb.npmjs.com/registry/_design/app/_view/byField/?key=%22pageres%22&field=description @othiym23 Was the |
@sindresorhus npm/public-api#6 |
I created #9 to focus on the Leaving this to the scoped packages end-point. |
I've filed npm/public-api#11 to get the discussion moving on the version end-point for scoped packages. |
@sindresorhus In order to solve this, we can maybe just retrieve the latest release (https://registry.npmjs.org/pageres/latest). It's not the entire package so the size is a lot smaller, but allows us to retrieve the field and keep this method. |
@SamVerschueren That doesn't work for scoped packages: https://registry.npmjs.org/@sindresorhus%2Fdf/latest |
The API is absolutely horrible, but I guess we can look forward a public API in 2020 :p |
2020... Someone is having high hopes ;) |
Based on this issue (npm/npm#9164), which was a follow up to pull request #6 , it looks like the
<PACKAGE NAME>/<VERSION>
API end-point is going to be deprecated in the future.The text was updated successfully, but these errors were encountered: