Repository navigation
fix(clerk-js,react): finish a failed load from a reload only outside a standard browser - #10597
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
🦋 Changeset detectedLatest commit: f7828f6 The changes in this PR will be included in the next version bump. This PR includes changesets to release 0 packagesWhen changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the
 |
Remove the changeset for the internal allowEmptyBody option, which users can't set, and the empty one from #10597. The clerk-js patch still comes from the load recovery changeset.
Description
Stacked on #10461.
__internal_reloadInitialResourcesnow finishes a failedload()only outside a standard browser. A standard browser load does more setup after its fetches, like the captcha heartbeat and FAPI-initiated redirects, so a web instance would have reportedreadywithout it. Only@clerk/expocalls the method today, but web apps get new clerk-js without upgrading.In
@clerk/react,loadHeadlessClerkhandles the rejection with.then(onLoaded, onRejected)instead of aloadFailedflag.replayWhenLoadIsFinishedsubscribes with{ notify: true }, which replaces theclerk.loadedcheck. Every clerk-js that emitsstatussupportsnotify.The changeset is empty because #10461's changesets already cover this.
Checklist
clerk-jssrc/core(1175 passed) and@clerk/react(502 passed).pnpm buildruns as expected.Type of change