If you host a local node that will make npm modules available over IPFS, it would be good to have a command that slurps down the current tree of manifests, and resolves all of the CIDs.
This command should be cancellable and it should be able to pick up where it left off.
It'll also probably depend on getting async iterators into js-ipfs other performance of reading the directory that contains the list of packages will be very slow.
If you host a local node that will make npm modules available over IPFS, it would be good to have a command that slurps down the current tree of manifests, and resolves all of the CIDs.
This command should be cancellable and it should be able to pick up where it left off.
It'll also probably depend on getting async iterators into js-ipfs other performance of reading the directory that contains the list of packages will be very slow.