fix(cli): rebuild if process.env changes in nuxt.config

[pi0]

Types of changes

• Bug fix (a non-breaking change which fixes an issue)
• New feature (a non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Description

Fixes #8199 using two methods:

• Adding config.env in snapshot for quick diff
• Static analyzes of process.env.* usage in nuxt.config and also include in snapshot

NOTE: Downside is that it may cause rebuilds if runtimeConfig is using process.env directly. Workaround would be using foo: 'FOO' syntax.

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly. (PR: #)
• I have added tests to cover my changes (if not applicable, please state why)
• All new and existing tests are passing.

[codecov-io]

Codecov Report

Merging #8200 into dev will decrease coverage by 0.12%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##              dev    #8200      +/-   ##
==========================================
- Coverage   68.89%   68.76%   -0.13%     
==========================================
  Files          91       91              
  Lines        3851     3858       +7     
  Branches     1049     1050       +1     
==========================================
  Hits         2653     2653              
- Misses        973      979       +6     
- Partials      225      226       +1     

Flag	Coverage Δ
#unittests	68.76% <0.00%> (-0.13%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
packages/cli/src/utils/generate.js	0.00% <0.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5842a64...683d272. Read the comment docs.

[LordGaav]

I'm running into the downside you mention:

NOTE: Downside is that it may cause rebuilds if runtimeConfig is using process.env directly. Workaround would be using foo: 'FOO' syntax.

What does "foo: 'FOO' syntax." mean? My nuxt.config.js uses a syntax like such:

publicRuntimeConfig: {
  fooUrl: process.env.FOO_URL || "aSaneDefault",
}

[pi0]

#8955 should fix this in next release to don't rebuild on env changes