fix: runtimeConfig and appConfig changes are not triggering reactivity
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3.3k
- Forks
- 214
- Avg merge
- 13h 22m
- Merged PRs (30d)
- 18
Description
🐛 The bug
It seems that updating the runtimeConfig and the appConfig doesn't have an effect on the reactive values in Nuxt.
🛠️ To reproduce
https://stackblitz.com/edit/github-pptyqfgu?file=app%2Fapp.vue,nuxt.config.ts,app%2Fapp.config.ts
🌈 Expected behavior
Updating values in runtimeConfig or appConfig should result in updates in the corresponding objects in the current Nuxt instance and you should see the changes in your application.
ℹ️ Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked StackBlitz reproduction, especially app/app.vue, nuxt.config.ts, and app/app.config.ts, and verify how runtimeConfig and appConfig updates affect the current Nuxt instance. Trace the relevant reactivity path in the devtools code. Done means changes to both configurations update their corresponding reactive values in the application.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nuxt, typescript
- Domain
- developer-experience
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100