-
Notifications
You must be signed in to change notification settings - Fork 402
poc(clerk-js): Initialize client more quickly [POC - DO NOT MERGE] #7139
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
Open
jacekradko
wants to merge
1
commit into
main
Choose a base branch
from
feat/initialize-client-more-quickly
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+6
−0
Open
Changes from all commits
Commits
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 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.
🧩 Analysis chain
Double client update may cause unnecessary re-renders and state churn.
Calling
updateClientat line 2611 with the preliminary client and again at line 2616 with the fetched client will trigger#emit()twice in rapid succession. Each emission notifies all registered listeners, potentially causing double React re-renders and state updates.Additionally, this new bootstrap path lacks error handling and debug logging, making it difficult to diagnose issues in production.
Consider these improvements:
const jwtInCookie = this.#authService?.getSessionCookie(); if (jwtInCookie) { const preliminaryClient = createClientFromJwt(jwtInCookie); - this.updateClient(preliminaryClient); + // Set client without emitting to avoid double render + this.client = preliminaryClient; + if (!this.session) { + const session = this.#options.selectInitialSession + ? this.#options.selectInitialSession(preliminaryClient) + : this.#defaultSession(preliminaryClient); + this.#setAccessors(session); + } }Run the following script to verify how often
updateClienttriggers listener callbacks in the codebase:🏁 Script executed:
Length of output: 7186
🏁 Script executed:
Length of output: 3001
🏁 Script executed:
Length of output: 3001
Double client update will trigger unnecessary listener notifications; add preliminary client without emission.
Confirmed:
updateClient()always callsthis.#emit()(line 2401), which notifies all registered listeners. The code at lines 2611 and 2616 will trigger this twice in sequence, causing React and other framework listeners to update state twice unnecessarily.Additionally, the new bootstrap path lacks error handling and debug logging, making it difficult to diagnose issues in production.
Suggested improvements:
const jwtInCookie = this.#authService?.getSessionCookie(); if (jwtInCookie) { const preliminaryClient = createClientFromJwt(jwtInCookie); - this.updateClient(preliminaryClient); + // Set client directly without emitting to avoid duplicate listener notifications + this.client = preliminaryClient; + if (!this.client) { + const session = this.#options.selectInitialSession + ? this.#options.selectInitialSession(preliminaryClient) + : this.#defaultSession(preliminaryClient); + this.#setAccessors(session); + } }🤖 Prompt for AI Agents