chore: refactor info package

[rishabh3112]

What kind of change does this PR introduce?
refactor/feature.

• Display all info and remove unnecessary flags

Did you add tests for your changes?
WIP

If relevant, did you update the documentation?
WIP

Summary
Would be adding info package as direct dependency as per roadmap

Does this PR introduce a breaking change?
No

Other information
No

[alexander-akait]

Need improve tests

[webpack-bot]

@rishabh3112 Thanks for your update.

I labeled the Pull Request so reviewers will review it again.

@evilebottnawi Please review the new changes.

[webpack-bot]

Thank you for your pull request! The most important CI builds succeeded, we’ll review the pull request soon.

[alexander-akait]

Can you provide example of current output? I think we should migrate on snapshots in future

[rishabh3112]

Snapshots for testing is a bad idea IMO. On different testing environments (windows, linux, macOS, ...) output would be different on each one of them.

Here is output:

I use WSL and don't have any browser installed over there, so no browsers :)

[alexander-akait]

Snapshots for testing is a bad idea IMO. On different testing environments (windows, linux, macOS, ...) output would be different on each one of them.

No, it is good idea, we should remove/mock platform specific output from snapshot (like do it webpack)

[rishabh3112]

@evilebottnawi System output is very important for info command, and it is system specific IMO. Or am I missing some information here?

[alexander-akait]

Now I have to spar every time what the output looks like, it’s extremely inconvenient and I can skip some regressions, run it locally every time and look very time-consuming, so we need to simplify this

[alexander-akait]

@rishabh3112 I will improve tests in future and you see how it is better, let's avoid it here, just provide example current default output

[rishabh3112]

Here it is #1382 (comment)

[rishabh3112]

@evilebottnawi also should I add the info as direct dependency in this PR itself, or should we release it info first to npm with current changes?

[alexander-akait]

Let's rename npmPackages: to Packages: and globalNpmPackages to Global packages:

@evilebottnawi also should I add the info as direct dependency in this PR itself, or should we release it info first to npm with current changes?

In the next PR

[rishabh3112]

Replaced output:

@evilebottnawi anything else?

[wizardofhogwarts]

LGTM.
I think it should be merged. @evilebottnawi @rishabh3112 @anshumanv

[alexander-akait]

Good job, thanks!

[alexander-akait]

Thanks, feel free to integrate env package into CLI