Add Nitro and Nuxt integration entries#15
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
commit: |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 9a7fc1bf10
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 0e724cba8a
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 50c4dee541
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Refactors runtime config validation around explicit
nuxt-safe-runtime-config/nitroandnuxt-safe-runtime-config/nuxtpackage entries while keeping the root import as the backward-compatible Nuxt module.The Nitro entry now owns build-time validation, runtime validation plugin registration, generated validation artifacts, and the thin Nitro v3/v2 runtime-config import fallback. The Nuxt adapter delegates validation into Nitro, keeps auto-imported
useSafeRuntimeConfig()types, and leaves the existing Shelve integration on the Nuxt/root path only.This also adds Nitro-only fixture coverage, Nuxt build regression coverage for Nitro-owned validation artifacts and build validation failures, and extends the packed-release smoke test with a Nitro consumer that imports
/nitrowithout installing Nuxt. Docs now clarify that generated validation artifact paths are internal implementation details.Need help on this PR? Tag
@codesmithwith what you need.