feat(cli): introduce next info CLI command

[balazsorban44]

This PR adds a new command to the next CLI.

Running next info will print useful information to the terminal about how/where Next.js is run. This information can be added to the Bug report when opening an issue in the repository.

This makes reporting issues more accurate and doesn't require the user to guess certain details, the command will retrieve it on their behalf.

Example output:

$ npx --no-install next info

    Operating System:
      Platform: linux
      Version: #22-Ubuntu SMP Fri Nov 5 13:21:36 UTC 2021
    Binaries:
      Node: 16.13.0
      npm: 8.1.0
      Yarn: 1.22.17
      pnpm: 6.24.2
    Relevant packages:
      next: 12.0.8-canary.14
      react: 17.0.2
      react-dom: 17.0.2

The idea is based on #32858

Bug

• Related issues linked using fixes #number
• Integration tests added
• Errors have helpful link attached, see contributing.md

Feature

• Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR.
• Related issues linked using fixes #number
• Integration tests added
• Documentation added
• Telemetry added. In case of a feature if it's used or not.
• Errors have helpful link attached, see contributing.md

Documentation / Examples

• Make sure the linting passes by running yarn lint

[mohsen1]

I don't know the rationale for not using envinfo package here. Getting browser information is pretty useful and it is a lot of complexity that envinfo polished over the term of its existence.

If next.js as a project is hesitant to adding more dependencies which is understandable, I think it's important to get browser information automatically too. Finding Chrome's version manually is actually a few steps that some issue filers might skip

[timneutkens]

Could you add a minimal integration test for this new command

[timneutkens]

Looks good!

[ijjk]

Stats from current PR

Default Build (Increase detected ⚠️)

General Overall increase ⚠️

	vercel/next.js canary	vercel/next.js feat/next-cli-info	Change
buildDuration	13.4s	13.5s	⚠️ +19ms
buildDurationCached	3.1s	3.1s	⚠️ +13ms
nodeModulesSize	348 MB	348 MB	⚠️ +4.59 kB

Page Load Tests Overall increase ✓

	vercel/next.js canary	vercel/next.js feat/next-cli-info	Change
/ failed reqs	0	0	✓
/ total time (seconds)	2.687	2.661	-0.03
/ avg req/sec	930.57	939.57	+9
/error-in-render failed reqs	0	0	✓
/error-in-render total time (seconds)	1.152	1.143	-0.01
/error-in-render avg req/sec	2169.33	2187.42	+18.09

Client Bundles (main, webpack, commons)

	vercel/next.js canary	vercel/next.js feat/next-cli-info	Change
450.HASH.js gzip	179 B	179 B	✓
framework-HASH.js gzip	42.2 kB	42.2 kB	✓
main-HASH.js gzip	27.1 kB	27.1 kB	✓
webpack-HASH.js gzip	1.45 kB	1.45 kB	✓
Overall change	70.9 kB	70.9 kB	✓

Legacy Client Bundles (polyfills)

	vercel/next.js canary	vercel/next.js feat/next-cli-info	Change
polyfills-HASH.js gzip	31 kB	31 kB	✓
Overall change	31 kB	31 kB	✓

Client Pages

	vercel/next.js canary	vercel/next.js feat/next-cli-info	Change
_app-HASH.js gzip	1.37 kB	1.37 kB	✓
_error-HASH.js gzip	194 B	194 B	✓
amp-HASH.js gzip	312 B	312 B	✓
css-HASH.js gzip	326 B	326 B	✓
dynamic-HASH.js gzip	2.37 kB	2.37 kB	✓
head-HASH.js gzip	350 B	350 B	✓
hooks-HASH.js gzip	919 B	919 B	✓
image-HASH.js gzip	4.74 kB	4.74 kB	✓
index-HASH.js gzip	263 B	263 B	✓
link-HASH.js gzip	2.13 kB	2.13 kB	✓
routerDirect..HASH.js gzip	321 B	321 B	✓
script-HASH.js gzip	383 B	383 B	✓
withRouter-HASH.js gzip	318 B	318 B	✓
85e02e95b279..7e3.css gzip	107 B	107 B	✓
Overall change	14.1 kB	14.1 kB	✓

Client Build Manifests

	vercel/next.js canary	vercel/next.js feat/next-cli-info	Change
_buildManifest.js gzip	459 B	459 B	✓
Overall change	459 B	459 B	✓

Rendered Page Sizes

	vercel/next.js canary	vercel/next.js feat/next-cli-info	Change
index.html gzip	532 B	532 B	✓
link.html gzip	546 B	546 B	✓
withRouter.html gzip	527 B	527 B	✓
Overall change	1.6 kB	1.6 kB	✓

---

Default Build with SWC (Increase detected ⚠️)

General Overall increase ⚠️

	vercel/next.js canary	vercel/next.js feat/next-cli-info	Change
buildDuration	14.8s	15s	⚠️ +211ms
buildDurationCached	3.1s	3.1s	⚠️ +11ms
nodeModulesSize	348 MB	348 MB	⚠️ +4.59 kB

Page Load Tests Overall increase ✓

	vercel/next.js canary	vercel/next.js feat/next-cli-info	Change
/ failed reqs	0	0	✓
/ total time (seconds)	2.672	2.682	⚠️ +0.01
/ avg req/sec	935.55	932.31	⚠️ -3.24
/error-in-render failed reqs	0	0	✓
/error-in-render total time (seconds)	1.137	1.115	-0.02
/error-in-render avg req/sec	2199.17	2242.16	+42.99

Client Bundles (main, webpack, commons)

	vercel/next.js canary	vercel/next.js feat/next-cli-info	Change
450.HASH.js gzip	179 B	179 B	✓
framework-HASH.js gzip	42.3 kB	42.3 kB	✓
main-HASH.js gzip	27.2 kB	27.2 kB	✓
webpack-HASH.js gzip	1.44 kB	1.44 kB	✓
Overall change	71.1 kB	71.1 kB	✓

Legacy Client Bundles (polyfills)

	vercel/next.js canary	vercel/next.js feat/next-cli-info	Change
polyfills-HASH.js gzip	31 kB	31 kB	✓
Overall change	31 kB	31 kB	✓

Client Pages

	vercel/next.js canary	vercel/next.js feat/next-cli-info	Change
_app-HASH.js gzip	1.35 kB	1.35 kB	✓
_error-HASH.js gzip	180 B	180 B	✓
amp-HASH.js gzip	305 B	305 B	✓
css-HASH.js gzip	321 B	321 B	✓
dynamic-HASH.js gzip	2.36 kB	2.36 kB	✓
head-HASH.js gzip	342 B	342 B	✓
hooks-HASH.js gzip	906 B	906 B	✓
image-HASH.js gzip	4.76 kB	4.76 kB	✓
index-HASH.js gzip	256 B	256 B	✓
link-HASH.js gzip	2.19 kB	2.19 kB	✓
routerDirect..HASH.js gzip	314 B	314 B	✓
script-HASH.js gzip	375 B	375 B	✓
withRouter-HASH.js gzip	309 B	309 B	✓
85e02e95b279..7e3.css gzip	107 B	107 B	✓
Overall change	14.1 kB	14.1 kB	✓

Client Build Manifests

	vercel/next.js canary	vercel/next.js feat/next-cli-info	Change
_buildManifest.js gzip	459 B	459 B	✓
Overall change	459 B	459 B	✓

Rendered Page Sizes

	vercel/next.js canary	vercel/next.js feat/next-cli-info	Change
index.html gzip	531 B	531 B	✓
link.html gzip	543 B	543 B	✓
withRouter.html gzip	525 B	525 B	✓
Overall change	1.6 kB	1.6 kB	✓

Commit: 4a26e7f