feature: download progress #1257

Closed
ry opened this Issue Aug 12, 2011 · 13 comments

Comments

Projects
None yet
@ry

ry commented Aug 12, 2011

doesn't need to be fancy - just some indication that it's doing something

@beatgammit

This comment has been minimized.

Show comment Hide comment
@beatgammit

beatgammit Aug 13, 2011

Contributor

I was just about to request the same thing. On slower connections, or with huge dependencies, NPM appears to hang.

Contributor

beatgammit commented Aug 13, 2011

I was just about to request the same thing. On slower connections, or with huge dependencies, NPM appears to hang.

@AvianFlu

This comment has been minimized.

Show comment Hide comment
@AvianFlu

AvianFlu Aug 13, 2011

@beatgammit - npm config set loglevel info can help a little bit with that problem.

In general, +1, and I also want to link https://github.com/substack/node-charm in case anybody wants to get fancy. :)

@beatgammit - npm config set loglevel info can help a little bit with that problem.

In general, +1, and I also want to link https://github.com/substack/node-charm in case anybody wants to get fancy. :)

@thejh

This comment has been minimized.

Show comment Hide comment
@thejh

thejh Aug 17, 2011

Contributor

👍
For this to be optimal, I'd suggest to rewrite the installation stuff to use the on-disk cache with additional dependency and size data to determine all dependencies at startup time. Then npm could display the exact download progress in terms of size and packages.

Unfortunately, I think that I can't do that myself because that part of the npm source is too cryptic for me to understand.

Contributor

thejh commented Aug 17, 2011

👍
For this to be optimal, I'd suggest to rewrite the installation stuff to use the on-disk cache with additional dependency and size data to determine all dependencies at startup time. Then npm could display the exact download progress in terms of size and packages.

Unfortunately, I think that I can't do that myself because that part of the npm source is too cryptic for me to understand.

@Zearin

This comment has been minimized.

Show comment Hide comment
@Zearin

Zearin Aug 29, 2011

+1!!! ☺

Zearin commented Aug 29, 2011

+1!!! ☺

@isaacs

This comment has been minimized.

Show comment Hide comment
@isaacs

isaacs Mar 13, 2012

Member

The log facility should be replaced with a standalone thing to make this happen.

Member

isaacs commented Mar 13, 2012

The log facility should be replaced with a standalone thing to make this happen.

@alFReD-NSH

This comment has been minimized.

Show comment Hide comment
@alFReD-NSH

alFReD-NSH Jul 19, 2012

+1 to this, would be nice if we could have a progress bar, that for every top level module it fills one tile of it.

+1 to this, would be nice if we could have a progress bar, that for every top level module it fills one tile of it.

@Zearin

This comment has been minimized.

Show comment Hide comment
@Zearin

Zearin Sep 9, 2012

+1

Zearin commented Sep 9, 2012

+1

@timoxley

This comment has been minimized.

Show comment Hide comment
@timoxley

timoxley Jan 7, 2014

Member

npm's default verbose logging seems to achieve "some indication that it's doing something" for now. Can we close this?

#4430

Member

timoxley commented Jan 7, 2014

npm's default verbose logging seems to achieve "some indication that it's doing something" for now. Can we close this?

#4430

@alFReD-NSH

This comment has been minimized.

Show comment Hide comment
@alFReD-NSH

alFReD-NSH Jan 7, 2014

You can close this, if you want to open new issue for progress bar :P

You can close this, if you want to open new issue for progress bar :P

@rlidwka

This comment has been minimized.

Show comment Hide comment
@rlidwka

rlidwka Jan 8, 2014

Contributor

Yeah, it's still relevant, although I have no idea how to fix that. Maybe reserve the bottom line of the terminal for the progress bar?

Contributor

rlidwka commented Jan 8, 2014

Yeah, it's still relevant, although I have no idea how to fix that. Maybe reserve the bottom line of the terminal for the progress bar?

@iarna

This comment has been minimized.

Show comment Hide comment
@iarna

iarna Sep 17, 2014

Member

npm has a spinner now, but I want to actually add real progress indicators

Member

iarna commented Sep 17, 2014

npm has a spinner now, but I want to actually add real progress indicators

@iarna iarna added this to the multi-stage install milestone Sep 17, 2014

@asbjornenge

This comment has been minimized.

Show comment Hide comment
@asbjornenge

asbjornenge Sep 23, 2014

Nyan unicorn progress bar ftw! im(h)o
nyan unicorn

Nyan unicorn progress bar ftw! im(h)o
nyan unicorn

@iarna iarna referenced this issue Oct 6, 2014

Closed

WIP multi stage install #6191

29 of 43 tasks complete

@othiym23 othiym23 removed the nice to have label Oct 7, 2014

@iarna iarna referenced this issue Dec 12, 2014

Closed

New npm progress indicator #6911

3 of 5 tasks complete
@iarna

This comment has been minimized.

Show comment Hide comment
@iarna

iarna Dec 12, 2014

Member

This is going to be implemented in #6911. As such, I'm going to close this ticket so that future discussion can happen around the actual implementation.

Member

iarna commented Dec 12, 2014

This is going to be implemented in #6911. As such, I'm going to close this ticket so that future discussion can happen around the actual implementation.

@iarna iarna closed this Dec 12, 2014

@iarna iarna locked and limited conversation to collaborators Jun 24, 2015

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.