Daniel Roe

feat: add runtime schema versioning support

1

This is an initial stab at runtime schema versioning support, for comment.

versioned schema

3

Users may have schema keys that are only relevant for certain versions of the schema. We can produce one set of type declarations that allows users to specify the schema...

fully resolved paths are getting embedded in docs/defaults

3

* 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

Expose more type helper functions

2

e.g. `genFunctionType`

inferred function type is wrong

1

For example, [@nuxt/kit](https://unpkg.com/browse/@nuxt/[email protected]/dist/index.d.ts): ```js globals: { id: () => any, nuxt: () => any, context: () => any, pluginPrefix: () => any, readyCallback: () => any, loadedCallback: () => any,...

add support for function overloads (?)

1

e.g.: ```ts /** * @param path - The value provided */ export function someFunction (path: string): string /** * @param factory - sample start * @param subpath - sub value...

For consistency with Node readable stream implementation, `destroy()` should likely return `this` - see https://nodejs.org/api/stream.html#readabledestroyerror and https://nodejs.org/api/stream.html#writabledestroyerror **Context**: https://github.com/DefinitelyTyped/DefinitelyTyped/pull/57473

refactor: use jest test environment

10

I'd be happy to refactor the way this module is invoked to use the [Jest custom environment feature](https://jestjs.io/docs/en/next/configuration#testenvironment-string), which I think would be a more intuitive way of setting up...

chiefly NuxtLink

It would be really convenient if we could mock a filesystem and inject files into it through the test utils. E.g. if my module reads in a config from a...