Track WebSocket route generations - #97030
Draft
DavidIlie wants to merge 1 commit into
Draft
Conversation
Contributor
Stats from current PR🔴 1 regression
📊 All Metrics📖 Metrics GlossaryDev Server Metrics:
Build Metrics:
Change Thresholds:
⚡ Dev Server
📦 Dev Server (Webpack) (Legacy)📦 Dev Server (Webpack)
⚡ Production Builds
📦 Production Builds (Webpack) (Legacy)📦 Production Builds (Webpack)
📦 Bundle SizesBundle Sizes⚡ TurbopackClient Main Bundles
Server Middleware
Build DetailsBuild Manifests
Build Cache
📦 WebpackClient Main Bundles
Polyfills
Pages
Server Edge SSR
Middleware
Build DetailsBuild Manifests
Build Cache
🔄 Shared (bundler-independent)Runtimes
📝 Changed Files (23 files)Files with changes:
View diffsapp-page-exp..ntime.dev.jsDiff too large to display app-page-exp..time.prod.jsDiff too large to display app-page-tur..ntime.dev.jsDiff too large to display app-page-tur..time.prod.jsDiff too large to display app-page-tur..ntime.dev.jsDiff too large to display app-page-tur..time.prod.jsDiff too large to display app-page.runtime.dev.jsDiff too large to display app-page.runtime.prod.jsDiff too large to display app-route-ex..ntime.dev.jsDiff too large to display app-route-ex..time.prod.jsDiff too large to display app-route-tu..ntime.dev.jsDiff too large to display app-route-tu..time.prod.jsDiff too large to display app-route-tu..ntime.dev.jsDiff too large to display app-route-tu..time.prod.jsDiff too large to display app-route.runtime.dev.jsDiff too large to display app-route.ru..time.prod.jsDiff too large to display pages-api.ru..time.prod.jsDiff too large to display pages.runtime.prod.jsDiff too large to display server.runtime.prod.jsDiff too large to display use-cache-pr..ntime.dev.jsDiff too large to display use-cache-pr..ntime.dev.jsDiff too large to display use-cache-pr..ntime.dev.jsDiff too large to display use-cache-pr..ntime.dev.jsDiff too large to display 📎 Tarball URLCommit: 3ded837 |
Contributor
Tests PassedCommit: 3ded837 |
DavidIlie
force-pushed
the
codex/websocket-route-generations
branch
from
August 10, 2026 11:34
603a1c0 to
8294207
Compare
DavidIlie
force-pushed
the
codex/websocket-route-generations
branch
from
August 10, 2026 11:40
8294207 to
8d49269
Compare
DavidIlie
force-pushed
the
codex/websocket-route-generations
branch
3 times, most recently
from
August 10, 2026 14:41
cfbf724 to
d079893
Compare
DavidIlie
force-pushed
the
codex/websocket-route-generations
branch
from
August 10, 2026 16:29
d079893 to
a6b7792
Compare
DavidIlie
force-pushed
the
codex/websocket-route-generations
branch
from
August 10, 2026 16:54
a6b7792 to
3ded837
Compare
This comment has been minimized.
This comment has been minimized.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What?
Track active WebSocket connections and in-flight upgrade leases by emitted App Route bundle identity.
Why?
HMR must distinguish an old route generation from the generation replacing it. Otherwise a newly accepted connection can be captured by the previous generation's drain, or an unrelated route can be disconnected unnecessarily.
How?
This PR is stacked on #97029. The Turbopack and Webpack consumers are added by the final PR.
Verification
pnpm exec jest --runInBand packages/next/src/server/websocket-connection-registry.test.ts