fix(clerk-react): Initialize isomorphic clerk with useRef#6024
Conversation
Avoid memoizing the singleton, instead use a reference to store it, and then destroy it. If logs are added when creating/getting the singleton and when clearing it, in the previous implementation you will notice that clearing occurs after the initializion causing the singleton to be set to null.
🦋 Changeset detectedLatest commit: 5b87669 The changes in this PR will be included in the next version bump. This PR includes changesets to release 8 packages
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 |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
!snapshot |
|
Hey @panteliselef - the snapshot version command generated the following package versions:
Tip: Use the snippet copy button below to quickly install the required packages. npm i @clerk/agent-toolkit@0.0.40-snapshot.v20250528194123 --save-exact
npm i @clerk/astro@2.8.2-snapshot.v20250528194123 --save-exact
npm i @clerk/backend@1.33.2-snapshot.v20250528194123 --save-exact
npm i @clerk/chrome-extension@2.4.10-snapshot.v20250528194123 --save-exact
npm i @clerk/clerk-js@5.67.5-snapshot.v20250528194123 --save-exact
npm i @clerk/elements@0.23.31-snapshot.v20250528194123 --save-exact
npm i @clerk/clerk-expo@2.11.10-snapshot.v20250528194123 --save-exact
npm i @clerk/expo-passkeys@0.3.8-snapshot.v20250528194123 --save-exact
npm i @clerk/express@1.5.2-snapshot.v20250528194123 --save-exact
npm i @clerk/fastify@2.2.23-snapshot.v20250528194123 --save-exact
npm i @clerk/localizations@3.16.3-snapshot.v20250528194123 --save-exact
npm i @clerk/nextjs@6.20.2-snapshot.v20250528194123 --save-exact
npm i @clerk/nuxt@1.6.9-snapshot.v20250528194123 --save-exact
npm i @clerk/clerk-react@5.31.8-snapshot.v20250528194123 --save-exact
npm i @clerk/react-router@1.4.8-snapshot.v20250528194123 --save-exact
npm i @clerk/remix@4.7.8-snapshot.v20250528194123 --save-exact
npm i @clerk/shared@3.9.5-snapshot.v20250528194123 --save-exact
npm i @clerk/tanstack-react-start@0.15.8-snapshot.v20250528194123 --save-exact
npm i @clerk/testing@1.7.5-snapshot.v20250528194123 --save-exact
npm i @clerk/themes@2.2.48-snapshot.v20250528194123 --save-exact
npm i @clerk/types@4.59.3-snapshot.v20250528194123 --save-exact
npm i @clerk/vue@1.8.6-snapshot.v20250528194123 --save-exact |
@clerk/agent-toolkit
@clerk/astro
@clerk/backend
@clerk/chrome-extension
@clerk/clerk-js
@clerk/dev-cli
@clerk/elements
@clerk/clerk-expo
@clerk/expo-passkeys
@clerk/express
@clerk/fastify
@clerk/localizations
@clerk/nextjs
@clerk/nuxt
@clerk/clerk-react
@clerk/react-router
@clerk/remix
@clerk/shared
@clerk/tanstack-react-start
@clerk/testing
@clerk/themes
@clerk/types
@clerk/upgrade
@clerk/vue
commit: |
3546de1 to
5821b51
Compare
tmilewski
left a comment
There was a problem hiding this comment.
🙃 Added a few suggested changes around console.log
This reverts commit 5821b51.
…finitely-when-remounted-across
Description
Avoid memoizing the singleton, instead use a reference to store it, and then destroy it.
If logs are added when creating/getting the singleton and when clearing it, in the previous implementation you will notice that clearing occurs after the initializion causing the singleton to be set to null.
Unblocks this DSH PR
Checklist
pnpm testruns as expected.pnpm buildruns as expected.Type of change