fix(nuxt,schema): prefer unknown rather than any for signatures

[danielroe]

🔗 Linked issue

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

This PR improves type safety within Nuxt in a number of locations where unspecified types fell back to any:

• RuntimeConfig
• PageMeta
• NuxtApp['payload'] (accessible now from NuxtPayload interface)
• ModuleMeta

It also fixes an issue with how we extended NitroRuntimeConfig.

The reason this is important is that type safety is purely cosmetic when accessing an unknown key. For example, if you rename a key in your runtime configuration, you aren't warned when accessing the old name of that key. If you do not like this behaviour, you can set typescript.strict to false in your nuxt.config - but it is highly recommended to keep strict mode enabled.

👉 Migration

It should not require any updating for end users in the case of RuntimeConfig as we already generate the types for every key we know about (and do not allow arbitrarily extending runtime configuration at runtime).

You can declare the types that are expected like this:

// this can be located in a declaration file (~/some-file.d.ts) or directly in your code base,
// ideally near where you use the augmented type
declare module '#app' {
  interface NuxtPayload {
    yourConfigKey?: number[]
  }
  interface PageMeta {
    myKey?: string
  }
}

// This should not be necessary but it is available should you need it as an escape hatch
declare module 'nuxt/schema' {
  interface RuntimeConfig {
    apiSecret: string
  }
}

// whenever augmenting types it is important that you either have an import or an export
// statement somewhere in the file, or your augmentations will 'overwrite' the original interface
export {}

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[nuxt-studio]

✅ Live Preview ready!

Name	Edit	Preview	Latest Commit
Nuxt Docs	Edit on Studio ↗︎	View Live Preview	e0a14ee

[danielroe]

cc: @pi0