feat(kit): useNitro() utility

[pi0]

🔗 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)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Taling with @danielroe, it is sometimes required to access nitro instance mainly to access resolved configuration. But it is tricky because nitro is intentionally initialized after all modules to reflect configuration changes by them.

This PR exposes useNitro() to be used within or after ready hook:

Note: Users should not modify the nitro configuration using this instance either. Because we have more than once instance (one is used for prerendering) and also nitro does not reflects configuration changes always after initializing. It is a read-only instance.

import { useNitro } from '@nuxt/kit'
nuxt.hook('ready', () => {
  console.log(useNitro())
})

📝 Checklist

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

[netlify]

✅ Deploy Preview for nuxt3-docs canceled.

Name	Link
🔨 Latest commit	ff5fbc3
🔍 Latest deploy log	https://app.netlify.com/sites/nuxt3-docs/deploys/6323215b8f6e9d000998871d