search

ipfs-shipyard / npm-on-ipfs

:package: Install npm modules through IPFS!
MIT License
467 stars 40 forks source link

`ipfs-npm update-registry-index` taking days on first run #93

Open agentofuser opened 5 years ago

agentofuser commented 5 years ago

I'm trying to get started with ipfs-npm, but I left ipfs-npm update-registry-index running since yesterday and so far it has downloaded less than 60 MB. Is this happening to anyone else or just me?

Is there an alternative source I can download from?

Btw, as someone who wants to see ipfs grow, I think publishing https://github.com/ipfs/blog/pull/215 before making sure the first experience is fast and pleasant might do more harm than good.

momack2 commented 5 years ago

@achingbrain @andrew - any ideas what might be going on here? Sounds like a pretty rough first-time-experience... what we can do to avoid these sorts of pain points ASAP?

agentofuser commented 5 years ago

I still haven't been able to get past ~150 MB 😅 Please let me know if there's anything I can do to help track this down, I can take the time to run commands, debugger, whatever.

achingbrain commented 5 years ago

I'm putting a fix together for this. The problem is that the MFS cp command assumes too much of the DAG is in the local repo when doing this sort of operation.

FWIW ipfs-npm update-registry-index is not necessary to start using ipfs-npm, all you should need to do is run ipfs-npm install in your project and away you go.

momack2 commented 5 years ago

Feedback request - is there docs to change in the readme to make it clear when and when not to run ‘update-registry-index’?

andrew commented 5 years ago

@momack2 PR to move the docs for that command out of the readme: https://github.com/ipfs-shipyard/npm-on-ipfs/pull/97

leonardge commented 4 years ago

ipfs-npm update-registry-index is taking me ages as well. Will be nice if there is progress bar. Also @agentofuser how did you know that is has only download 60MB?