fix(nuxt): remove backwards-compatible runtimeConfig proxy #20340
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
π Linked issue
resolves an issue reported in #20056
β Type of change
π Description
The compatibility proxy we were wrapping runtime config within was in fact causing a memory leak. We had already diarised to remove this compatibility layer in v3.5, and we'll go ahead with this solution at that point unless we can come up with a good backwards compatible solution before that point.
π Checklist