You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Removes the duplicate finishInit() from loadHeadlessClerk and uses the shared replayInterceptedInvocations path instead
Eliminates the manual state emission workaround that was only needed because the headless path had its own initialization logic
Removes the now-unused #initialized field
This addresses @brkalow's feedback to separate "how to get a Clerk instance" (bring your own constructor vs inject scripts) from "what to do after it's loaded" (shared wiring logic).
Before:loadHeadlessClerk had its own finishInit() that duplicated parts of replayInterceptedInvocations but was missing status/queryClientStatus listener replay.
After:loadHeadlessClerk only handles Clerk construction + clerk.load(), then hands off to the shared replayInterceptedInvocations path — same as the browser flow.
Test plan
Verify Expo native sign-in/sign-up flows still work (headless path)
Verify Next.js/React browser flows are unaffected (getEntryChunks path)
Verify chrome-extension with syncHost still works (getEntryChunks path)
…ocations
Remove the duplicate finishInit() from loadHeadlessClerk and use the
shared replayInterceptedInvocations path instead. This ensures both
browser and headless paths share the same post-load wiring logic,
including status/queryClientStatus listener replay that was previously
missing from the headless path.
The manual state emission workaround in finishInit is no longer needed
since replayInterceptedInvocations properly wires up addListener which
handles state propagation through clerk-js.
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
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
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.
Summary
finishInit()fromloadHeadlessClerkand uses the sharedreplayInterceptedInvocationspath instead#initializedfieldThis addresses @brkalow's feedback to separate "how to get a Clerk instance" (bring your own constructor vs inject scripts) from "what to do after it's loaded" (shared wiring logic).
Before:
loadHeadlessClerkhad its ownfinishInit()that duplicated parts ofreplayInterceptedInvocationsbut was missing status/queryClientStatus listener replay.After:
loadHeadlessClerkonly handles Clerk construction +clerk.load(), then hands off to the sharedreplayInterceptedInvocationspath — same as the browser flow.Test plan