fully resolved paths are getting embedded in docs/defaults

[danielroe]

• https://unpkg.com/browse/@nuxt/[email protected]/schema/config.md
• https://unpkg.com/browse/@nuxt/[email protected]/schema/config.d.ts
• https://unpkg.com/browse/@nuxt/[email protected]/schema/config.defaults.json

[pi0]

Hmm, it is expected for untyped to pick defaults unless you have a better idea, we shall detect generate script (with something like an environment variable) and use something like <rootDir> for rootDir or mock resolvers.

[danielroe]

Is it too opinionated simply to detect current absolute path (from process.cwd()) in defaults and replace it with <root>? I can't think of a scenario where we would want that in a schema.

# if run from /Users/me/mylibrary
/Users/me/mylibrary/dist/index.js -> <root>/dist/index.js
/Users/me/otherlibrary/dist/index.js -> /Users/me/otherlibrary/dist/index.js

[pi0]

Is it too opinionated simply to detect current absolute path (from process.cwd()) in defaults and replace it with ?

At least it is not necessarily always cwd() (and <root> being desired replacement) at untyped level.

How about supporting defaults as a function for resolveSchema ?