-
Notifications
You must be signed in to change notification settings - Fork 13.9k
refactor(client): replace useReactiveValue with useSyncExternalStore in providers #40446
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
tassoevan
merged 2 commits into
refactor/auth-provider-login-token-helper
from
refactor/sdk-status-loggingin-providers
May 13, 2026
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file was deleted.
Oops, something went wrong.
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Stale
cachedStatusbetween module load and first subscribe can leave the status bar wedged.cachedStatusis computed once at module-evaluation time (Line 136), and the SDK'connection'listener is only installed when the first component subscribes (ensureStatusBridge, Lines 140-149). Any'connection'transition that fires in the window between module load and the first subscribe is dropped — no listener yet, andcachedStatusis never refreshed.getStatusSnapshotthen keeps handing React the stale snapshot, and becauseuseSyncExternalStore's post-subscribe re-check also callsgetStatusSnapshot(still stale), no re-render is scheduled. On a stable connection that produces no further'connection'emits, theConnectionStatusBarcan stay stuck on the initial value (e.g.connecting). The previousTracker.autorunpath re-read on every invalidation, so this is a new regression.Refresh the cache when the bridge is installed so the first subscriber sees current state:
🛠️ Proposed fix
const ensureStatusBridge = (): void => { if (statusBridgeStarted) return; statusBridgeStarted = true; getDdpSdk().connection.on('connection', () => { const next = computeStatus(); if (isStatusEqual(cachedStatus, next)) return; cachedStatus = next; statusListeners.forEach((cb) => cb()); }); + cachedStatus = computeStatus(); };🤖 Prompt for AI Agents