fix(cli): don't use absolute path of .cache/nuxt as transpilation pattern

[danielroe]

closes #7774

If static.cacheDir isn't set, this won't add the fully resolved cache directory but instead just .cache/nuxt as a transpilation pattern.

Type of change

• 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

Resolves #7774

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-commenter]

Codecov Report

Merging #7775 into dev will decrease coverage by 0.01%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##              dev    #7775      +/-   ##
==========================================
- Coverage   68.85%   68.83%   -0.02%     
==========================================
  Files          90       90              
  Lines        3824     3825       +1     
  Branches     1034     1035       +1     
==========================================
  Hits         2633     2633              
  Misses        968      968              
- Partials      223      224       +1     

Flag	Coverage Δ
#unittests	68.83% <0.00%> (-0.02%)	⬇️

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 c2c6923...899951f. Read the comment docs.

[pi0]

If absolute path is problematic, shall we ensure it is always relative pattern or remove static.cacheDir support at all or add a warning for full path?

[danielroe]

If absolute path is problematic, shall we ensure it is always relative pattern or remove static.cacheDir support at all or add a warning for full path?

@pi0 I don't think a relative path will work either (e.g. with a leading ./) because it's being tested against the file pattern. I think let's remove support for adding transpile for custom staticPath, and leave it (with warning) for the person who uses the custom path.

One approach: 4a3ba0d