Skip to content
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

Stop using skimdb #2

Open
zeke opened this issue Mar 15, 2017 · 4 comments
Open

Stop using skimdb #2

zeke opened this issue Mar 15, 2017 · 4 comments

Comments

@zeke
Copy link
Member

zeke commented Mar 15, 2017

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

@rootAvish
Copy link

Hey @zeke, does this mean the data that this package downloads has not been updated after September?

@zeke
Copy link
Member Author

zeke commented Jan 10, 2018

@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.

@bananabr
Copy link

Hi @zeke,

I don't think you guys ever replaced skimdb right?
Can one still use this package somehow?

Thanks

@zeke
Copy link
Member Author

zeke commented Apr 18, 2022

Yeah this package is unmaintained. It would need to be updated to use the replicate.npmjs.com endpoint.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants