fix(nuxt): use portal to sync nitro/nuxt runtimeConfig + routeRules#27596
fix(nuxt): use portal to sync nitro/nuxt runtimeConfig + routeRules#27596
Conversation
|
|
pi0
left a comment
There was a problem hiding this comment.
Nice idea!
(re untyped, i was thinking of portal support since early versions but not sure how repeated this pattern is and honestly I'm not investing much on it nowadays)
|
Hey @danielroe, you pointed me to this issue from here, but I still see the errors when I build with Should I report this in
|
|
@toniengelhardt Would you open an issue with a reproduction on nuxt/nuxt? |
I tried to make a reproduction and realized that the error is actually caused by I'll open an issue there 🙏🏽 Update: |

🔗 Linked issue
resolves #27589
📚 Description
As a result of the refactor to runtimeConfig in #27117, it was possible to 'detach' these values if overwriting
nuxt.options.runtimeConfig.This PR first prevents overwriting
nitrooption (forcingObject.assign) and then also configuresruntimeConfigandrouteRulesso they will always be kept in sync.We might consider porting to
untyped.