'npm show <package> versions' output is useless if package has many versions

[andytompkins]

I'm opening this issue because:

• npm is crashing.
• npm is producing an incorrect install.
• npm is doing something I don't understand.
• Other (see below for feature requests):

What's going wrong?

If I run npm show ember-cli versions (for example), the output starts with the earliest version and the end of the list ends up being truncated like:

which makes it difficult to determine what the latest versions are.
It would make more sense if the list was sorted in the other direction, or if it was at least user selectable. (I know there are workarounds like json output or the glob trick, but this should be easy to use without having to know those.)

How can the CLI team reproduce the problem?

Run npm show ember-cli versions.

supporting information:

• npm -v prints: 3.10.10
• node -v prints: v6.10.2
• npm config get registry prints: (we do have an internal npm enterprise registry but this works the same with the public registry)
• Windows, OS X/macOS, or Linux?: OS X/macOS
• Network issues:
  • Geographic location where npm was run:
  • I use a proxy to connect to the npm registry.
  • I use a proxy to connect to the web.
  • I use a proxy when downloading Git repos.
  • I access the npm registry via a VPN
  • I don't use a proxy, but have limited or unreliable internet access.
• Container:
  • I develop using Vagrant on Windows.
  • I develop using Vagrant on OS X or Linux.
  • I develop / deploy using Docker.
  • I deploy to a PaaS (Triton, Heroku).

[watilde]

Correct me if I'm wrong, I think we should expand it with --long option since there is no way to do that currently.

[npm-robot]

We're closing this issue as it has gone seven days without activity and without being labeled. If we haven't even labeled in issue in seven days then we're unlikely to ever read it.

If you are still experiencing the issue that led to you opening this or this is a feature request you're still interested in then we encourage you to open a new issue. If this was a support issue, you may be better served by joining package.communty and asking your question there.

For more information about our new issue aging policies and why we've instituted them please see our blog post.