fix(devtools): prevent SSR memory leak in DevTools integration #5101
+13
−0
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.
Add SSR guards to DevTools registration functions to prevent memory leaks in server-side environments by checking both
__DEV__andisClient.Fixes #4978
🔎 Overview
This PR fixes a memory leak in SSR environments like Nuxt, where the DevTools registration functions were running on the server-side, causing component references to accumulate in memory across requests. I've tested this fix locally and can confirm it successfully eliminates the need for the NODE_ENV=production workaround as described in #4978.
🤓 Code snippets/examples
✔ Issues affected
closes #4978
PS: I'll create another PR #5102 for the v4 Branch. :)