-
-
Notifications
You must be signed in to change notification settings - Fork 5.3k
feat(nuxt): warn if user uses reserved runtimeConfig.app
namespace
#31774
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
WalkthroughThe changes update the Nuxt documentation and core functionality. The documentation now states that both keys from Tip ⚡💬 Agentic Chat (Pro Plan, General Availability)
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
⏰ Context from checks skipped due to timeout of 90000ms (4)
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
🧹 Nitpick comments (1)
docs/2.guide/3.going-further/10.runtime-config.md (1)
95-95
: Documentation clarified about client-side runtime config accessibilityThis update correctly explains that both
runtimeConfig.public
andruntimeConfig.app
(used internally by Nuxt) are available on the client-side.Note: There's a minor grammar issue with "On client-side" - it should be "On the client-side" for consistency with the server-side statement on line 97.
-- On client-side, only keys in `runtimeConfig.public` and `runtimeConfig.app` (which is used by Nuxt internally) are available, and the object is both writable and reactive. +- On the client-side, only keys in `runtimeConfig.public` and `runtimeConfig.app` (which is used by Nuxt internally) are available, and the object is both writable and reactive.🧰 Tools
🪛 LanguageTool
[uncategorized] ~95-~95: You might be missing the article “the” here.
Context: ... the client-side and server-side: - On client-side, only keys in `runtimeConfig.publi...(AI_EN_LECTOR_MISSING_DETERMINER_THE)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (3)
docs/1.getting-started/03.configuration.md
(1 hunks)docs/2.guide/3.going-further/10.runtime-config.md
(1 hunks)packages/nuxt/src/core/nuxt.ts
(1 hunks)
🧰 Additional context used
🪛 LanguageTool
docs/2.guide/3.going-further/10.runtime-config.md
[uncategorized] ~95-~95: You might be missing the article “the” here.
Context: ... the client-side and server-side: - On client-side, only keys in `runtimeConfig.publi...
(AI_EN_LECTOR_MISSING_DETERMINER_THE)
⏰ Context from checks skipped due to timeout of 90000ms (20)
- GitHub Check: test-fixtures (windows-latest, built, webpack, default, manifest-on, json, 18)
- GitHub Check: test-fixtures (ubuntu-latest, built, webpack, default, manifest-on, json, 18)
- GitHub Check: test-fixtures (windows-latest, dev, vite, default, manifest-on, json, 18)
- GitHub Check: test-fixtures (ubuntu-latest, built, vite, default, manifest-off, json, 18)
- GitHub Check: test-fixtures (windows-latest, dev, vite, async, manifest-on, json, 18)
- GitHub Check: test-fixtures (ubuntu-latest, built, rspack, default, manifest-on, json, 18)
- GitHub Check: test-fixtures (ubuntu-latest, built, vite, async, manifest-on, js, 18)
- GitHub Check: test-fixtures (ubuntu-latest, built, vite, async, manifest-off, json, 18)
- GitHub Check: test-fixtures (ubuntu-latest, built, vite, default, manifest-on, json, 18)
- GitHub Check: test-fixtures (ubuntu-latest, dev, vite, async, manifest-on, json, 18)
- GitHub Check: test-fixtures (ubuntu-latest, dev, vite, async, manifest-on, js, 18)
- GitHub Check: test-fixtures (ubuntu-latest, built, vite, async, manifest-on, json, 18)
- GitHub Check: test-fixtures (ubuntu-latest, built, rspack, async, manifest-on, json, 18)
- GitHub Check: test-fixtures (ubuntu-latest, dev, vite, async, manifest-off, json, 18)
- GitHub Check: test-fixtures (ubuntu-latest, dev, vite, default, manifest-off, json, 18)
- GitHub Check: typecheck (windows-latest, bundler)
- GitHub Check: release-pr
- GitHub Check: test-benchmark
- GitHub Check: typecheck (ubuntu-latest, bundler)
- GitHub Check: code
🔇 Additional comments (1)
docs/1.getting-started/03.configuration.md (1)
65-65
: Clear documentation update about runtimeConfig.app visibilityThis change accurately documents that both
runtimeConfig.public
andruntimeConfig.app
namespaces are accessible client-side, which improves developer understanding of Nuxt's runtime configuration behavior.
@nuxt/kit
nuxt
@nuxt/rspack-builder
@nuxt/schema
@nuxt/vite-builder
@nuxt/webpack-builder
commit: |
CodSpeed Performance ReportMerging #31774 will not alter performanceComparing Summary
|
🔗 Linked issue
📚 Description
Nuxt uses an internal namespace in
runtimeConfig
which is exposed to the browser.this PR warns + removes user configuration set here, and we also document that this is exposed to the client.