We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
http://blog.npmjs.org/post/157615772423/deprecating-the-all-registry-endpoint
In six months, on September 1 2017, we plan to shut down the servers that back the GET /-/all endpoint of registry.npmjs.org.
This package will need to be updated to use a different technique for collecting package data at install time, probably using package-stream.
Thanks to @rmg for pointing this out in https://github.com/npm/registry/issues/136
The text was updated successfully, but these errors were encountered:
Hey @zeke, does this mean the data that this package downloads has not been updated after September?
Sorry, something went wrong.
@rootAvish that's correct. You may want to take a look at https://github.com/nice-registry/package-stream to easily download all the package data.
Hi @zeke,
I don't think you guys ever replaced skimdb right? Can one still use this package somehow?
Thanks
Yeah this package is unmaintained. It would need to be updated to use the replicate.npmjs.com endpoint.
replicate.npmjs.com
No branches or pull requests
http://blog.npmjs.org/post/157615772423/deprecating-the-all-registry-endpoint
This package will need to be updated to use a different technique for collecting package data at install time, probably using package-stream.
Thanks to @rmg for pointing this out in https://github.com/npm/registry/issues/136
The text was updated successfully, but these errors were encountered: