npm info foo@range --json does not show same data as without --json

[ljharb]

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?

npm info graceful-fs@* version: produces a list of version numbers and the version string.
npm info graceful-fs@* version --json: produces only the first found version string.

The same applies to npm info graceful-fs@* deprecated, and probably many other fields.

How can the CLI team reproduce the problem?

Run npm info graceful-fs@* version with and without --json.

supporting information:

• npm -v prints: 3.10.3
• node -v prints: 6.5.0
• npm config get registry prints: https://registry.npmjs.org/
• Windows, OS X, or Linux?: OS X
• Network issues: None
• Container: N/A

[legodude17]

I can confirm that this does happen. I am pretty sure the docs say that --json is still in development.

[ljharb]

Hmm, now I can't reproduce "produces only the first found" in npm 2, 3, 4, or 5.

I'm definitely still not getting actual JSON; just uncolored normal output - so this should stay open.

[ljharb]

(ping, in case npmbot decides to annihilate my issue)

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

[ljharb]

sigh. This issue should definitely still be open.

[ljharb]

Thank you! Would you mind labelling it so it can stay open longer?

[ljharb]

(ping, to avoid npmbot carnage)

[ljharb]

(ping again)