Adds a new list reporter

[luislobo]

Adds a new list reporter, with a more streamlined output.
Lets you do | grep critical (for example), as it prints everything in one line.

Please check the TODO comment to see if it's valid

I also have a change for npm that I'm about to send after this one, so that npm audit has a --list parameter

Adresses #7

[evilpacket]

@luislobo I haven't had a chance to test this out, do you happen to have a screenshot of the output (I swear I've seen one someplace and thought it was here but now it's not so I'm confused) :)

[luislobo]

yeah sure! It was on a tweet in response to @zkat tweet about audit.

[luislobo]

@zkat suggested changing it as --parseable making it output the result like npm install --parseable, I think that both use cases are valid, the --list one and the --parseable one. If you agree, I can add also parseable

npm install --parseable outputs something like this:

add	abbrev	1.1.1	node_modules/fsevents/node_modules/abbrev		
add	ansi-regex	2.1.1	node_modules/fsevents/node_modules/ansi-regex		
add	aproba	1.2.0	node_modules/fsevents/node_modules/aproba		
add	balanced-match	1.0.0	node_modules/fsevents/node_modules/balanced-match		
add	chownr	1.0.1	node_modules/fsevents/node_modules/chownr		
add	code-point-at	1.1.0	node_modules/fsevents/node_modules/code-point-at		
add	concat-map	0.0.1	node_modules/fsevents/node_modules/concat-map		
add	brace-expansion	1.1.11	node_modules/fsevents/node_modules/brace-expansion		
add	console-control-strings	1.1.0	node_modules/fsevents/node_modules/console-control-strings		
add	core-util-is	1.0.2	node_modules/fsevents/node_modules/core-util-is		

[luislobo]

@zkat may I ask why it was closed?

[zkat]

oh. I guess this happened because of renaming the default branch to latest.

[zkat]

fixed :)

[luislobo]

Awesome 😍

[zkat]

I'm gonna /cc @iarna and @evilpacket on this to get their perspective on the --list view. I'm neutral on it and would still like a --parseable reporter (and I still think --list could be replaced with a fairly readable version of --parseable).

[evilpacket]

My initial concern about the screenshot above is terminal width requirements and trying to keep output , but I'm pro a greppable report, which could probably meet both requirements with a --parsable style report.

[luislobo]

I could make a --parseable version with colors, as I've seen that colors can be enabled/disabled too. We could add a param for --no-color if there is a need (didn't check yet how disabling the colors works internally)

I'm fine with getting rid of the --list option.

One question though, it's a funcional one. Can you check the PR, there is a TODO/TOCHECK here: https://github.com/npm/npm-audit-report/pull/10/files#diff-a06ff6c66ce9794c6a36389e432a5266R117

[iarna]

npm cli side, parseable output should never have colors (it is solely intended for consumption by tooling and should not require additional flags).

[iarna]

Before this can land tests will need to be passing (currently this is failing our linter)

[luislobo]

Replaced this PR with #21, closing this one.

New one has --parseable, has no colors, passes lint and enhanced tests.