Skip to content

fix(clerk-js): Backport dev browser token being read from stale non-partitioned cookies - #8238

Merged
nikosdouvlis merged 3 commits into
release/core-2from
backport
Apr 5, 2026
Merged

fix(clerk-js): Backport dev browser token being read from stale non-partitioned cookies#8238
nikosdouvlis merged 3 commits into
release/core-2from
backport

Conversation

@tmilewski

@tmilewskitmilewski commented Apr 5, 2026

Copy link
Copy Markdown
Member

Description

Checklist

  • pnpm test runs as expected.
  • pnpm build runs as expected.
  • (If applicable) JSDoc comments have been added or updated for any package exports
  • (If applicable) Documentation has been updated

Type of change

  • 🐛 Bug fix
  • 🌟 New feature
  • 🔨 Breaking change
  • 📖 Refactoring / dependency upgrade / documentation
  • other:

Summary by CodeRabbit

Bug Fixes

  • Fixed developer browser token handling when partitioned cookies are enabled. Tokens are now stored in memory to ensure authentication requests consistently use the current token value instead of stale cached values.

@changeset-bot

changeset-botBot commented Apr 5, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: d6ddaa1

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 3 packages
NameType
@clerk/clerk-jsPatch
@clerk/chrome-extensionPatch
@clerk/clerk-expoPatch

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

@vercel

vercelBot commented Apr 5, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

ProjectDeploymentActionsUpdated (UTC)
clerk-js-sandboxReadyReadyPreview, CommentApr 5, 2026 11:04am

Request Review

@coderabbitai

coderabbitaiBot commented Apr 5, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 2e2a0272-44b2-4f54-ac4f-41f3813652a8

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch backport

Comment @coderabbitai help to get the list of available commands and usage tips.

@tmilewskitmilewski changed the title fix(clerk-js): Backport dbt being read from stale non-partitioned cookiesfix(clerk-js): Backport dev browser token being read from stale non-partitioned cookiesApr 5, 2026
@pkg-pr-new

pkg-pr-newBot commented Apr 5, 2026

Copy link
Copy Markdown

Open in StackBlitz

@clerk/agent-toolkit

npm i https://pkg.pr.new/@clerk/agent-toolkit@8238

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@8238

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@8238

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@8238

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@8238

@clerk/dev-cli

npm i https://pkg.pr.new/@clerk/dev-cli@8238

@clerk/elements

npm i https://pkg.pr.new/@clerk/elements@8238

@clerk/clerk-expo

npm i https://pkg.pr.new/@clerk/clerk-expo@8238

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@8238

@clerk/express

npm i https://pkg.pr.new/@clerk/express@8238

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@8238

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@8238

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@8238

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@8238

@clerk/clerk-react

npm i https://pkg.pr.new/@clerk/clerk-react@8238

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@8238

@clerk/remix

npm i https://pkg.pr.new/@clerk/remix@8238

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@8238

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@8238

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@8238

@clerk/themes

npm i https://pkg.pr.new/@clerk/themes@8238

@clerk/types

npm i https://pkg.pr.new/@clerk/types@8238

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@8238

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@8238

commit: d6ddaa1

@coderabbitaicoderabbitaiBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
integration/tests/dev-browser-partitioned-cookies.test.ts (1)

30-31: Consider defensive handling for undefined publishable key.

The non-null assertion on parsePublishableKey(pk)! could cause a confusing test failure if CLERK_PUBLISHABLE_KEY is not configured. A clearer assertion would improve debuggability.

🔧 Proposed improvement for better error messaging
 const pk = app.env.publicVariables.get('CLERK_PUBLISHABLE_KEY');
- const { frontendApi } = parsePublishableKey(pk)!;+ const parsed = parsePublishableKey(pk);+ expect(parsed).toBeTruthy();+ const { frontendApi } = parsed!;
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@integration/tests/dev-browser-partitioned-cookies.test.ts` around lines 30 -
31, The test currently uses a non-null assertion on parsePublishableKey(pk)!
which will throw a vague error if CLERK_PUBLISHABLE_KEY is missing; update the
setup to defensively check that pk (from
app.env.publicVariables.get('CLERK_PUBLISHABLE_KEY')) is defined and fail fast
with a clear message (e.g., throw or assert) before calling parsePublishableKey,
and then call parsePublishableKey(pk) without the non-null assertion and extract
frontendApi; reference the symbols pk, app.env.publicVariables.get, and
parsePublishableKey to locate and fix the code.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@integration/tests/dev-browser-partitioned-cookies.test.ts`:
- Around line 30-31: The test currently uses a non-null assertion on
parsePublishableKey(pk)! which will throw a vague error if CLERK_PUBLISHABLE_KEY
is missing; update the setup to defensively check that pk (from
app.env.publicVariables.get('CLERK_PUBLISHABLE_KEY')) is defined and fail fast
with a clear message (e.g., throw or assert) before calling parsePublishableKey,
and then call parsePublishableKey(pk) without the non-null assertion and extract
frontendApi; reference the symbols pk, app.env.publicVariables.get, and
parsePublishableKey to locate and fix the code.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 13c25e43-228d-4c06-a30a-0fef91334e71

📥 Commits

Reviewing files that changed from the base of the PR and between c19a60a and f4c47f5.

📒 Files selected for processing (3)
  • .changeset/plain-lines-kneel.md
  • integration/tests/dev-browser-partitioned-cookies.test.ts
  • packages/clerk-js/src/core/auth/devBrowser.ts

networkidle never settles on clerk-js pages because of
SessionCookiePoller, telemetry, and captcha network activity.
No other integration test uses networkidle.
@nikosdouvlis
nikosdouvlis merged commit 78269fc into release/core-2Apr 5, 2026
44 checks passed
@nikosdouvlis
nikosdouvlis deleted the backport branch April 5, 2026 11:45
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@tmilewski@nikosdouvlis
, 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all
 blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
fix(clerk-js): Backport dev browser token being read from stale non-partitioned cookies by tmilewski · Pull Request #8238 · clerk/javascript · GitHub
Skip to content

fix(clerk-js): Backport dev browser token being read from stale non-partitioned cookies - #8238

Merged
nikosdouvlis merged 3 commits into
release/core-2from
backport
Apr 5, 2026
Merged

fix(clerk-js): Backport dev browser token being read from stale non-partitioned cookies#8238
nikosdouvlis merged 3 commits into
release/core-2from
backport

Conversation

@tmilewski

@tmilewskitmilewski commented Apr 5, 2026

Copy link
Copy Markdown
Member

Description

Checklist

  • pnpm test runs as expected.
  • pnpm build runs as expected.
  • (If applicable) JSDoc comments have been added or updated for any package exports
  • (If applicable) Documentation has been updated

Type of change

  • 🐛 Bug fix
  • 🌟 New feature
  • 🔨 Breaking change
  • 📖 Refactoring / dependency upgrade / documentation
  • other:

Summary by CodeRabbit

Bug Fixes

  • Fixed developer browser token handling when partitioned cookies are enabled. Tokens are now stored in memory to ensure authentication requests consistently use the current token value instead of stale cached values.

@changeset-bot

changeset-botBot commented Apr 5, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: d6ddaa1

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 3 packages
NameType
@clerk/clerk-jsPatch
@clerk/chrome-extensionPatch
@clerk/clerk-expoPatch

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

@vercel

vercelBot commented Apr 5, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

ProjectDeploymentActionsUpdated (UTC)
clerk-js-sandboxReadyReadyPreview, CommentApr 5, 2026 11:04am

Request Review

@coderabbitai

coderabbitaiBot commented Apr 5, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 2e2a0272-44b2-4f54-ac4f-41f3813652a8

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch backport

Comment @coderabbitai help to get the list of available commands and usage tips.

@tmilewskitmilewski changed the title fix(clerk-js): Backport dbt being read from stale non-partitioned cookiesfix(clerk-js): Backport dev browser token being read from stale non-partitioned cookiesApr 5, 2026
@pkg-pr-new

pkg-pr-newBot commented Apr 5, 2026

Copy link
Copy Markdown

Open in StackBlitz

@clerk/agent-toolkit

npm i https://pkg.pr.new/@clerk/agent-toolkit@8238

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@8238

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@8238

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@8238

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@8238

@clerk/dev-cli

npm i https://pkg.pr.new/@clerk/dev-cli@8238

@clerk/elements

npm i https://pkg.pr.new/@clerk/elements@8238

@clerk/clerk-expo

npm i https://pkg.pr.new/@clerk/clerk-expo@8238

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@8238

@clerk/express

npm i https://pkg.pr.new/@clerk/express@8238

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@8238

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@8238

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@8238

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@8238

@clerk/clerk-react

npm i https://pkg.pr.new/@clerk/clerk-react@8238

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@8238

@clerk/remix

npm i https://pkg.pr.new/@clerk/remix@8238

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@8238

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@8238

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@8238

@clerk/themes

npm i https://pkg.pr.new/@clerk/themes@8238

@clerk/types

npm i https://pkg.pr.new/@clerk/types@8238

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@8238

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@8238

commit: d6ddaa1

@coderabbitaicoderabbitaiBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
integration/tests/dev-browser-partitioned-cookies.test.ts (1)

30-31: Consider defensive handling for undefined publishable key.

The non-null assertion on parsePublishableKey(pk)! could cause a confusing test failure if CLERK_PUBLISHABLE_KEY is not configured. A clearer assertion would improve debuggability.

🔧 Proposed improvement for better error messaging
 const pk = app.env.publicVariables.get('CLERK_PUBLISHABLE_KEY');
- const { frontendApi } = parsePublishableKey(pk)!;+ const parsed = parsePublishableKey(pk);+ expect(parsed).toBeTruthy();+ const { frontendApi } = parsed!;
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@integration/tests/dev-browser-partitioned-cookies.test.ts` around lines 30 -
31, The test currently uses a non-null assertion on parsePublishableKey(pk)!
which will throw a vague error if CLERK_PUBLISHABLE_KEY is missing; update the
setup to defensively check that pk (from
app.env.publicVariables.get('CLERK_PUBLISHABLE_KEY')) is defined and fail fast
with a clear message (e.g., throw or assert) before calling parsePublishableKey,
and then call parsePublishableKey(pk) without the non-null assertion and extract
frontendApi; reference the symbols pk, app.env.publicVariables.get, and
parsePublishableKey to locate and fix the code.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@integration/tests/dev-browser-partitioned-cookies.test.ts`:
- Around line 30-31: The test currently uses a non-null assertion on
parsePublishableKey(pk)! which will throw a vague error if CLERK_PUBLISHABLE_KEY
is missing; update the setup to defensively check that pk (from
app.env.publicVariables.get('CLERK_PUBLISHABLE_KEY')) is defined and fail fast
with a clear message (e.g., throw or assert) before calling parsePublishableKey,
and then call parsePublishableKey(pk) without the non-null assertion and extract
frontendApi; reference the symbols pk, app.env.publicVariables.get, and
parsePublishableKey to locate and fix the code.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 13c25e43-228d-4c06-a30a-0fef91334e71

📥 Commits

Reviewing files that changed from the base of the PR and between c19a60a and f4c47f5.

📒 Files selected for processing (3)
  • .changeset/plain-lines-kneel.md
  • integration/tests/dev-browser-partitioned-cookies.test.ts
  • packages/clerk-js/src/core/auth/devBrowser.ts

networkidle never settles on clerk-js pages because of
SessionCookiePoller, telemetry, and captcha network activity.
No other integration test uses networkidle.
@nikosdouvlis
nikosdouvlis merged commit 78269fc into release/core-2Apr 5, 2026
44 checks passed
@nikosdouvlis
nikosdouvlis deleted the backport branch April 5, 2026 11:45
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@tmilewski@nikosdouvlis
, 'i'); if (__m === '*' || __re.test(location.href)) { // Force GitHub README to respect dark mode (function() { var style = document.createElement('style'); style.textContent = ' .markdown-body { color-scheme: dark light; } .markdown-body pre { background: #161b22 !important; } .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; } .markdown-body table th, .markdown-body table td { border-color: #30363d !important; } .markdown-body img { background: #0d1117; } .markdown-body blockquote { border-left-color: #8b949e; } .markdown-body hr { border-color: #30363d; } '; document.head.appendChild(style); })(); } } catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' fix(clerk-js): Backport dev browser token being read from stale non-partitioned cookies by tmilewski · Pull Request #8238 · clerk/javascript · GitHub
Skip to content

fix(clerk-js): Backport dev browser token being read from stale non-partitioned cookies - #8238

Merged
nikosdouvlis merged 3 commits into
release/core-2from
backport
Apr 5, 2026
Merged

fix(clerk-js): Backport dev browser token being read from stale non-partitioned cookies#8238
nikosdouvlis merged 3 commits into
release/core-2from
backport

Conversation

@tmilewski

@tmilewskitmilewski commented Apr 5, 2026

Copy link
Copy Markdown
Member

Description

Checklist

  • pnpm test runs as expected.
  • pnpm build runs as expected.
  • (If applicable) JSDoc comments have been added or updated for any package exports
  • (If applicable) Documentation has been updated

Type of change

  • 🐛 Bug fix
  • 🌟 New feature
  • 🔨 Breaking change
  • 📖 Refactoring / dependency upgrade / documentation
  • other:

Summary by CodeRabbit

Bug Fixes

  • Fixed developer browser token handling when partitioned cookies are enabled. Tokens are now stored in memory to ensure authentication requests consistently use the current token value instead of stale cached values.

@changeset-bot

changeset-botBot commented Apr 5, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: d6ddaa1

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 3 packages
NameType
@clerk/clerk-jsPatch
@clerk/chrome-extensionPatch
@clerk/clerk-expoPatch

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

@vercel

vercelBot commented Apr 5, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

ProjectDeploymentActionsUpdated (UTC)
clerk-js-sandboxReadyReadyPreview, CommentApr 5, 2026 11:04am

Request Review

@coderabbitai

coderabbitaiBot commented Apr 5, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 2e2a0272-44b2-4f54-ac4f-41f3813652a8

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch backport

Comment @coderabbitai help to get the list of available commands and usage tips.

@tmilewskitmilewski changed the title fix(clerk-js): Backport dbt being read from stale non-partitioned cookiesfix(clerk-js): Backport dev browser token being read from stale non-partitioned cookiesApr 5, 2026
@pkg-pr-new

pkg-pr-newBot commented Apr 5, 2026

Copy link
Copy Markdown

Open in StackBlitz

@clerk/agent-toolkit

npm i https://pkg.pr.new/@clerk/agent-toolkit@8238

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@8238

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@8238

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@8238

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@8238

@clerk/dev-cli

npm i https://pkg.pr.new/@clerk/dev-cli@8238

@clerk/elements

npm i https://pkg.pr.new/@clerk/elements@8238

@clerk/clerk-expo

npm i https://pkg.pr.new/@clerk/clerk-expo@8238

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@8238

@clerk/express

npm i https://pkg.pr.new/@clerk/express@8238

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@8238

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@8238

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@8238

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@8238

@clerk/clerk-react

npm i https://pkg.pr.new/@clerk/clerk-react@8238

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@8238

@clerk/remix

npm i https://pkg.pr.new/@clerk/remix@8238

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@8238

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@8238

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@8238

@clerk/themes

npm i https://pkg.pr.new/@clerk/themes@8238

@clerk/types

npm i https://pkg.pr.new/@clerk/types@8238

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@8238

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@8238

commit: d6ddaa1

@coderabbitaicoderabbitaiBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
integration/tests/dev-browser-partitioned-cookies.test.ts (1)

30-31: Consider defensive handling for undefined publishable key.

The non-null assertion on parsePublishableKey(pk)! could cause a confusing test failure if CLERK_PUBLISHABLE_KEY is not configured. A clearer assertion would improve debuggability.

🔧 Proposed improvement for better error messaging
 const pk = app.env.publicVariables.get('CLERK_PUBLISHABLE_KEY');
- const { frontendApi } = parsePublishableKey(pk)!;+ const parsed = parsePublishableKey(pk);+ expect(parsed).toBeTruthy();+ const { frontendApi } = parsed!;
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@integration/tests/dev-browser-partitioned-cookies.test.ts` around lines 30 -
31, The test currently uses a non-null assertion on parsePublishableKey(pk)!
which will throw a vague error if CLERK_PUBLISHABLE_KEY is missing; update the
setup to defensively check that pk (from
app.env.publicVariables.get('CLERK_PUBLISHABLE_KEY')) is defined and fail fast
with a clear message (e.g., throw or assert) before calling parsePublishableKey,
and then call parsePublishableKey(pk) without the non-null assertion and extract
frontendApi; reference the symbols pk, app.env.publicVariables.get, and
parsePublishableKey to locate and fix the code.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@integration/tests/dev-browser-partitioned-cookies.test.ts`:
- Around line 30-31: The test currently uses a non-null assertion on
parsePublishableKey(pk)! which will throw a vague error if CLERK_PUBLISHABLE_KEY
is missing; update the setup to defensively check that pk (from
app.env.publicVariables.get('CLERK_PUBLISHABLE_KEY')) is defined and fail fast
with a clear message (e.g., throw or assert) before calling parsePublishableKey,
and then call parsePublishableKey(pk) without the non-null assertion and extract
frontendApi; reference the symbols pk, app.env.publicVariables.get, and
parsePublishableKey to locate and fix the code.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 13c25e43-228d-4c06-a30a-0fef91334e71

📥 Commits

Reviewing files that changed from the base of the PR and between c19a60a and f4c47f5.

📒 Files selected for processing (3)
  • .changeset/plain-lines-kneel.md
  • integration/tests/dev-browser-partitioned-cookies.test.ts
  • packages/clerk-js/src/core/auth/devBrowser.ts

networkidle never settles on clerk-js pages because of
SessionCookiePoller, telemetry, and captcha network activity.
No other integration test uses networkidle.
@nikosdouvlis
nikosdouvlis merged commit 78269fc into release/core-2Apr 5, 2026
44 checks passed
@nikosdouvlis
nikosdouvlis deleted the backport branch April 5, 2026 11:45
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@tmilewski@nikosdouvlis
, 'i'); if (__m === '*' || __re.test(location.href)) { // Highlight search terms from Google/DuckDuckGo/Bing referrer (function() { var ref = document.referrer; var terms = []; if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) { var url = new URL(ref); var q = url.searchParams.get('q') || url.searchParams.get('p'); if (q) { terms = q.split(/\s+/).filter(function(t) { return t.length > 2; }); } } if (terms.length === 0) return; var style = document.createElement('style'); style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }'; document.head.appendChild(style); function highlight(node) { if (node.nodeType === 3) { // text node var text = node.textContent; var found = false; terms.forEach(function(term) { var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi'); if (regex.test(text)) { found = true; var frag = document.createDocumentFragment(); var parts = text.split(regex); parts.forEach(function(part, i) { if (i % 2 === 0) { frag.appendChild(document.createTextNode(part)); } else { var span = document.createElement('span'); span.className = 'userscript-highlight'; span.textContent = part; frag.appendChild(span); } }); node.parentNode.replaceChild(frag, node); } }); } else if (node.nodeType === 1 && node.childNodes) { // element var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT']; if (!skipTags.includes(node.tagName)) { Array.from(node.childNodes).forEach(highlight); } } } highlight(document.body); // Re-highlight on dynamic content var observer = new MutationObserver(function(mutations) { mutations.forEach(function(m) { m.addedNodes.forEach(function(node) { if (node.nodeType === 1 || node.nodeType === 3) highlight(node); }); }); }); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' fix(clerk-js): Backport dev browser token being read from stale non-partitioned cookies by tmilewski · Pull Request #8238 · clerk/javascript · GitHub
Skip to content

fix(clerk-js): Backport dev browser token being read from stale non-partitioned cookies - #8238

Merged
nikosdouvlis merged 3 commits into
release/core-2from
backport
Apr 5, 2026
Merged

fix(clerk-js): Backport dev browser token being read from stale non-partitioned cookies#8238
nikosdouvlis merged 3 commits into
release/core-2from
backport

Conversation

@tmilewski

@tmilewskitmilewski commented Apr 5, 2026

Copy link
Copy Markdown
Member

Description

Checklist

  • pnpm test runs as expected.
  • pnpm build runs as expected.
  • (If applicable) JSDoc comments have been added or updated for any package exports
  • (If applicable) Documentation has been updated

Type of change

  • 🐛 Bug fix
  • 🌟 New feature
  • 🔨 Breaking change
  • 📖 Refactoring / dependency upgrade / documentation
  • other:

Summary by CodeRabbit

Bug Fixes

  • Fixed developer browser token handling when partitioned cookies are enabled. Tokens are now stored in memory to ensure authentication requests consistently use the current token value instead of stale cached values.

@changeset-bot

changeset-botBot commented Apr 5, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: d6ddaa1

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 3 packages
NameType
@clerk/clerk-jsPatch
@clerk/chrome-extensionPatch
@clerk/clerk-expoPatch

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

@vercel

vercelBot commented Apr 5, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

ProjectDeploymentActionsUpdated (UTC)
clerk-js-sandboxReadyReadyPreview, CommentApr 5, 2026 11:04am

Request Review

@coderabbitai

coderabbitaiBot commented Apr 5, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 2e2a0272-44b2-4f54-ac4f-41f3813652a8

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch backport

Comment @coderabbitai help to get the list of available commands and usage tips.

@tmilewskitmilewski changed the title fix(clerk-js): Backport dbt being read from stale non-partitioned cookiesfix(clerk-js): Backport dev browser token being read from stale non-partitioned cookiesApr 5, 2026
@pkg-pr-new

pkg-pr-newBot commented Apr 5, 2026

Copy link
Copy Markdown

Open in StackBlitz

@clerk/agent-toolkit

npm i https://pkg.pr.new/@clerk/agent-toolkit@8238

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@8238

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@8238

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@8238

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@8238

@clerk/dev-cli

npm i https://pkg.pr.new/@clerk/dev-cli@8238

@clerk/elements

npm i https://pkg.pr.new/@clerk/elements@8238

@clerk/clerk-expo

npm i https://pkg.pr.new/@clerk/clerk-expo@8238

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@8238

@clerk/express

npm i https://pkg.pr.new/@clerk/express@8238

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@8238

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@8238

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@8238

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@8238

@clerk/clerk-react

npm i https://pkg.pr.new/@clerk/clerk-react@8238

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@8238

@clerk/remix

npm i https://pkg.pr.new/@clerk/remix@8238

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@8238

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@8238

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@8238

@clerk/themes

npm i https://pkg.pr.new/@clerk/themes@8238

@clerk/types

npm i https://pkg.pr.new/@clerk/types@8238

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@8238

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@8238

commit: d6ddaa1

@coderabbitaicoderabbitaiBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
integration/tests/dev-browser-partitioned-cookies.test.ts (1)

30-31: Consider defensive handling for undefined publishable key.

The non-null assertion on parsePublishableKey(pk)! could cause a confusing test failure if CLERK_PUBLISHABLE_KEY is not configured. A clearer assertion would improve debuggability.

🔧 Proposed improvement for better error messaging
 const pk = app.env.publicVariables.get('CLERK_PUBLISHABLE_KEY');
- const { frontendApi } = parsePublishableKey(pk)!;+ const parsed = parsePublishableKey(pk);+ expect(parsed).toBeTruthy();+ const { frontendApi } = parsed!;
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@integration/tests/dev-browser-partitioned-cookies.test.ts` around lines 30 -
31, The test currently uses a non-null assertion on parsePublishableKey(pk)!
which will throw a vague error if CLERK_PUBLISHABLE_KEY is missing; update the
setup to defensively check that pk (from
app.env.publicVariables.get('CLERK_PUBLISHABLE_KEY')) is defined and fail fast
with a clear message (e.g., throw or assert) before calling parsePublishableKey,
and then call parsePublishableKey(pk) without the non-null assertion and extract
frontendApi; reference the symbols pk, app.env.publicVariables.get, and
parsePublishableKey to locate and fix the code.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@integration/tests/dev-browser-partitioned-cookies.test.ts`:
- Around line 30-31: The test currently uses a non-null assertion on
parsePublishableKey(pk)! which will throw a vague error if CLERK_PUBLISHABLE_KEY
is missing; update the setup to defensively check that pk (from
app.env.publicVariables.get('CLERK_PUBLISHABLE_KEY')) is defined and fail fast
with a clear message (e.g., throw or assert) before calling parsePublishableKey,
and then call parsePublishableKey(pk) without the non-null assertion and extract
frontendApi; reference the symbols pk, app.env.publicVariables.get, and
parsePublishableKey to locate and fix the code.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 13c25e43-228d-4c06-a30a-0fef91334e71

📥 Commits

Reviewing files that changed from the base of the PR and between c19a60a and f4c47f5.

📒 Files selected for processing (3)
  • .changeset/plain-lines-kneel.md
  • integration/tests/dev-browser-partitioned-cookies.test.ts
  • packages/clerk-js/src/core/auth/devBrowser.ts

networkidle never settles on clerk-js pages because of
SessionCookiePoller, telemetry, and captcha network activity.
No other integration test uses networkidle.
@nikosdouvlis
nikosdouvlis merged commit 78269fc into release/core-2Apr 5, 2026
44 checks passed
@nikosdouvlis
nikosdouvlis deleted the backport branch April 5, 2026 11:45
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@tmilewski@nikosdouvlis
, 'i'); if (__m === '*' || __re.test(location.href)) { // Strip utm_, fbclid, gclid, etc. from all links on page (function() { var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content', 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid', 'ref', 'ref_src', 'source', 'medium', 'campaign']; function cleanUrl(url) { try { var u = new URL(url, window.location.origin); var changed = false; trackingParams.forEach(function(p) { if (u.searchParams.has(p)) { u.searchParams.delete(p); changed = true; } }); return changed ? u.toString() : url; } catch (e) { return url; } } function cleanLinks() { document.querySelectorAll('a[href]').forEach(function(a) { var clean = cleanUrl(a.href); if (clean !== a.href) a.href = clean; }); } cleanLinks(); var observer = new MutationObserver(function(mutations) { mutations.forEach(function(m) { m.addedNodes.forEach(function(node) { if (node.nodeType === 1) { if (node.tagName === 'A') cleanLinks(); node.querySelectorAll('a[href]').forEach(function(a) { var clean = cleanUrl(a.href); if (clean !== a.href) a.href = clean; }); } }); }); }); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); } })(); (function(){ try { var __m = "youtube.com"; var __re = new RegExp('^' + "youtube\\.com" + ' fix(clerk-js): Backport dev browser token being read from stale non-partitioned cookies by tmilewski · Pull Request #8238 · clerk/javascript · GitHub
Skip to content

fix(clerk-js): Backport dev browser token being read from stale non-partitioned cookies - #8238

Merged
nikosdouvlis merged 3 commits into
release/core-2from
backport
Apr 5, 2026
Merged

fix(clerk-js): Backport dev browser token being read from stale non-partitioned cookies#8238
nikosdouvlis merged 3 commits into
release/core-2from
backport

Conversation

@tmilewski

@tmilewskitmilewski commented Apr 5, 2026

Copy link
Copy Markdown
Member

Description

Checklist

  • pnpm test runs as expected.
  • pnpm build runs as expected.
  • (If applicable) JSDoc comments have been added or updated for any package exports
  • (If applicable) Documentation has been updated

Type of change

  • 🐛 Bug fix
  • 🌟 New feature
  • 🔨 Breaking change
  • 📖 Refactoring / dependency upgrade / documentation
  • other:

Summary by CodeRabbit

Bug Fixes

  • Fixed developer browser token handling when partitioned cookies are enabled. Tokens are now stored in memory to ensure authentication requests consistently use the current token value instead of stale cached values.

@changeset-bot

changeset-botBot commented Apr 5, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: d6ddaa1

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 3 packages
NameType
@clerk/clerk-jsPatch
@clerk/chrome-extensionPatch
@clerk/clerk-expoPatch

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

@vercel

vercelBot commented Apr 5, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

ProjectDeploymentActionsUpdated (UTC)
clerk-js-sandboxReadyReadyPreview, CommentApr 5, 2026 11:04am

Request Review

@coderabbitai

coderabbitaiBot commented Apr 5, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 2e2a0272-44b2-4f54-ac4f-41f3813652a8

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch backport

Comment @coderabbitai help to get the list of available commands and usage tips.

@tmilewskitmilewski changed the title fix(clerk-js): Backport dbt being read from stale non-partitioned cookiesfix(clerk-js): Backport dev browser token being read from stale non-partitioned cookiesApr 5, 2026
@pkg-pr-new

pkg-pr-newBot commented Apr 5, 2026

Copy link
Copy Markdown

Open in StackBlitz

@clerk/agent-toolkit

npm i https://pkg.pr.new/@clerk/agent-toolkit@8238

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@8238

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@8238

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@8238

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@8238

@clerk/dev-cli

npm i https://pkg.pr.new/@clerk/dev-cli@8238

@clerk/elements

npm i https://pkg.pr.new/@clerk/elements@8238

@clerk/clerk-expo

npm i https://pkg.pr.new/@clerk/clerk-expo@8238

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@8238

@clerk/express

npm i https://pkg.pr.new/@clerk/express@8238

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@8238

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@8238

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@8238

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@8238

@clerk/clerk-react

npm i https://pkg.pr.new/@clerk/clerk-react@8238

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@8238

@clerk/remix

npm i https://pkg.pr.new/@clerk/remix@8238

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@8238

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@8238

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@8238

@clerk/themes

npm i https://pkg.pr.new/@clerk/themes@8238

@clerk/types

npm i https://pkg.pr.new/@clerk/types@8238

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@8238

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@8238

commit: d6ddaa1

@coderabbitaicoderabbitaiBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
integration/tests/dev-browser-partitioned-cookies.test.ts (1)

30-31: Consider defensive handling for undefined publishable key.

The non-null assertion on parsePublishableKey(pk)! could cause a confusing test failure if CLERK_PUBLISHABLE_KEY is not configured. A clearer assertion would improve debuggability.

🔧 Proposed improvement for better error messaging
 const pk = app.env.publicVariables.get('CLERK_PUBLISHABLE_KEY');
- const { frontendApi } = parsePublishableKey(pk)!;+ const parsed = parsePublishableKey(pk);+ expect(parsed).toBeTruthy();+ const { frontendApi } = parsed!;
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@integration/tests/dev-browser-partitioned-cookies.test.ts` around lines 30 -
31, The test currently uses a non-null assertion on parsePublishableKey(pk)!
which will throw a vague error if CLERK_PUBLISHABLE_KEY is missing; update the
setup to defensively check that pk (from
app.env.publicVariables.get('CLERK_PUBLISHABLE_KEY')) is defined and fail fast
with a clear message (e.g., throw or assert) before calling parsePublishableKey,
and then call parsePublishableKey(pk) without the non-null assertion and extract
frontendApi; reference the symbols pk, app.env.publicVariables.get, and
parsePublishableKey to locate and fix the code.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@integration/tests/dev-browser-partitioned-cookies.test.ts`:
- Around line 30-31: The test currently uses a non-null assertion on
parsePublishableKey(pk)! which will throw a vague error if CLERK_PUBLISHABLE_KEY
is missing; update the setup to defensively check that pk (from
app.env.publicVariables.get('CLERK_PUBLISHABLE_KEY')) is defined and fail fast
with a clear message (e.g., throw or assert) before calling parsePublishableKey,
and then call parsePublishableKey(pk) without the non-null assertion and extract
frontendApi; reference the symbols pk, app.env.publicVariables.get, and
parsePublishableKey to locate and fix the code.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 13c25e43-228d-4c06-a30a-0fef91334e71

📥 Commits

Reviewing files that changed from the base of the PR and between c19a60a and f4c47f5.

📒 Files selected for processing (3)
  • .changeset/plain-lines-kneel.md
  • integration/tests/dev-browser-partitioned-cookies.test.ts
  • packages/clerk-js/src/core/auth/devBrowser.ts

networkidle never settles on clerk-js pages because of
SessionCookiePoller, telemetry, and captcha network activity.
No other integration test uses networkidle.
@nikosdouvlis
nikosdouvlis merged commit 78269fc into release/core-2Apr 5, 2026
44 checks passed
@nikosdouvlis
nikosdouvlis deleted the backport branch April 5, 2026 11:45
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@tmilewski@nikosdouvlis
, 'i'); if (__m === '*' || __re.test(location.href)) { // Auto-enable theater mode on YouTube (function() { function tryTheater() { var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]'); if (btn && !btn.classList.contains('activated')) { btn.click(); } } // Try immediately tryTheater(); // Try after navigation (SPA) var lastUrl = location.href; setInterval(function() { if (location.href !== lastUrl) { lastUrl = location.href; setTimeout(tryTheater, 500); } }, 1000); // Also try on player load var observer = new MutationObserver(tryTheater); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' fix(clerk-js): Backport dev browser token being read from stale non-partitioned cookies by tmilewski · Pull Request #8238 · clerk/javascript · GitHub
Skip to content

fix(clerk-js): Backport dev browser token being read from stale non-partitioned cookies - #8238

Merged
nikosdouvlis merged 3 commits into
release/core-2from
backport
Apr 5, 2026
Merged

fix(clerk-js): Backport dev browser token being read from stale non-partitioned cookies#8238
nikosdouvlis merged 3 commits into
release/core-2from
backport

Conversation

@tmilewski

@tmilewskitmilewski commented Apr 5, 2026

Copy link
Copy Markdown
Member

Description

Checklist

  • pnpm test runs as expected.
  • pnpm build runs as expected.
  • (If applicable) JSDoc comments have been added or updated for any package exports
  • (If applicable) Documentation has been updated

Type of change

  • 🐛 Bug fix
  • 🌟 New feature
  • 🔨 Breaking change
  • 📖 Refactoring / dependency upgrade / documentation
  • other:

Summary by CodeRabbit

Bug Fixes

  • Fixed developer browser token handling when partitioned cookies are enabled. Tokens are now stored in memory to ensure authentication requests consistently use the current token value instead of stale cached values.

@changeset-bot

changeset-botBot commented Apr 5, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: d6ddaa1

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 3 packages
NameType
@clerk/clerk-jsPatch
@clerk/chrome-extensionPatch
@clerk/clerk-expoPatch

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

@vercel

vercelBot commented Apr 5, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

ProjectDeploymentActionsUpdated (UTC)
clerk-js-sandboxReadyReadyPreview, CommentApr 5, 2026 11:04am

Request Review

@coderabbitai

coderabbitaiBot commented Apr 5, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 2e2a0272-44b2-4f54-ac4f-41f3813652a8

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch backport

Comment @coderabbitai help to get the list of available commands and usage tips.

@tmilewskitmilewski changed the title fix(clerk-js): Backport dbt being read from stale non-partitioned cookiesfix(clerk-js): Backport dev browser token being read from stale non-partitioned cookiesApr 5, 2026
@pkg-pr-new

pkg-pr-newBot commented Apr 5, 2026

Copy link
Copy Markdown

Open in StackBlitz

@clerk/agent-toolkit

npm i https://pkg.pr.new/@clerk/agent-toolkit@8238

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@8238

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@8238

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@8238

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@8238

@clerk/dev-cli

npm i https://pkg.pr.new/@clerk/dev-cli@8238

@clerk/elements

npm i https://pkg.pr.new/@clerk/elements@8238

@clerk/clerk-expo

npm i https://pkg.pr.new/@clerk/clerk-expo@8238

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@8238

@clerk/express

npm i https://pkg.pr.new/@clerk/express@8238

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@8238

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@8238

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@8238

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@8238

@clerk/clerk-react

npm i https://pkg.pr.new/@clerk/clerk-react@8238

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@8238

@clerk/remix

npm i https://pkg.pr.new/@clerk/remix@8238

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@8238

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@8238

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@8238

@clerk/themes

npm i https://pkg.pr.new/@clerk/themes@8238

@clerk/types

npm i https://pkg.pr.new/@clerk/types@8238

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@8238

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@8238

commit: d6ddaa1

@coderabbitaicoderabbitaiBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
integration/tests/dev-browser-partitioned-cookies.test.ts (1)

30-31: Consider defensive handling for undefined publishable key.

The non-null assertion on parsePublishableKey(pk)! could cause a confusing test failure if CLERK_PUBLISHABLE_KEY is not configured. A clearer assertion would improve debuggability.

🔧 Proposed improvement for better error messaging
 const pk = app.env.publicVariables.get('CLERK_PUBLISHABLE_KEY');
- const { frontendApi } = parsePublishableKey(pk)!;+ const parsed = parsePublishableKey(pk);+ expect(parsed).toBeTruthy();+ const { frontendApi } = parsed!;
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@integration/tests/dev-browser-partitioned-cookies.test.ts` around lines 30 -
31, The test currently uses a non-null assertion on parsePublishableKey(pk)!
which will throw a vague error if CLERK_PUBLISHABLE_KEY is missing; update the
setup to defensively check that pk (from
app.env.publicVariables.get('CLERK_PUBLISHABLE_KEY')) is defined and fail fast
with a clear message (e.g., throw or assert) before calling parsePublishableKey,
and then call parsePublishableKey(pk) without the non-null assertion and extract
frontendApi; reference the symbols pk, app.env.publicVariables.get, and
parsePublishableKey to locate and fix the code.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@integration/tests/dev-browser-partitioned-cookies.test.ts`:
- Around line 30-31: The test currently uses a non-null assertion on
parsePublishableKey(pk)! which will throw a vague error if CLERK_PUBLISHABLE_KEY
is missing; update the setup to defensively check that pk (from
app.env.publicVariables.get('CLERK_PUBLISHABLE_KEY')) is defined and fail fast
with a clear message (e.g., throw or assert) before calling parsePublishableKey,
and then call parsePublishableKey(pk) without the non-null assertion and extract
frontendApi; reference the symbols pk, app.env.publicVariables.get, and
parsePublishableKey to locate and fix the code.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 13c25e43-228d-4c06-a30a-0fef91334e71

📥 Commits

Reviewing files that changed from the base of the PR and between c19a60a and f4c47f5.

📒 Files selected for processing (3)
  • .changeset/plain-lines-kneel.md
  • integration/tests/dev-browser-partitioned-cookies.test.ts
  • packages/clerk-js/src/core/auth/devBrowser.ts

networkidle never settles on clerk-js pages because of
SessionCookiePoller, telemetry, and captcha network activity.
No other integration test uses networkidle.
@nikosdouvlis
nikosdouvlis merged commit 78269fc into release/core-2Apr 5, 2026
44 checks passed
@nikosdouvlis
nikosdouvlis deleted the backport branch April 5, 2026 11:45
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@tmilewski@nikosdouvlis
, 'i'); if (__m === '*' || __re.test(location.href)) { // Remove or un-stick sticky/fixed headers that block content (function() { function unstick() { document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) { if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') { el.style.position = 'static'; el.style.top = 'auto'; el.style.zIndex = 'auto'; } }); } unstick(); var observer = new MutationObserver(unstick); observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] }); })(); } } catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' fix(clerk-js): Backport dev browser token being read from stale non-partitioned cookies by tmilewski · Pull Request #8238 · clerk/javascript · GitHub
Skip to content

fix(clerk-js): Backport dev browser token being read from stale non-partitioned cookies - #8238

Merged
nikosdouvlis merged 3 commits into
release/core-2from
backport
Apr 5, 2026
Merged

fix(clerk-js): Backport dev browser token being read from stale non-partitioned cookies#8238
nikosdouvlis merged 3 commits into
release/core-2from
backport

Conversation

@tmilewski

@tmilewskitmilewski commented Apr 5, 2026

Copy link
Copy Markdown
Member

Description

Checklist

  • pnpm test runs as expected.
  • pnpm build runs as expected.
  • (If applicable) JSDoc comments have been added or updated for any package exports
  • (If applicable) Documentation has been updated

Type of change

  • 🐛 Bug fix
  • 🌟 New feature
  • 🔨 Breaking change
  • 📖 Refactoring / dependency upgrade / documentation
  • other:

Summary by CodeRabbit

Bug Fixes

  • Fixed developer browser token handling when partitioned cookies are enabled. Tokens are now stored in memory to ensure authentication requests consistently use the current token value instead of stale cached values.

@changeset-bot

changeset-botBot commented Apr 5, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: d6ddaa1

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 3 packages
NameType
@clerk/clerk-jsPatch
@clerk/chrome-extensionPatch
@clerk/clerk-expoPatch

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

@vercel

vercelBot commented Apr 5, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

ProjectDeploymentActionsUpdated (UTC)
clerk-js-sandboxReadyReadyPreview, CommentApr 5, 2026 11:04am

Request Review

@coderabbitai

coderabbitaiBot commented Apr 5, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 2e2a0272-44b2-4f54-ac4f-41f3813652a8

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch backport

Comment @coderabbitai help to get the list of available commands and usage tips.

@tmilewskitmilewski changed the title fix(clerk-js): Backport dbt being read from stale non-partitioned cookiesfix(clerk-js): Backport dev browser token being read from stale non-partitioned cookiesApr 5, 2026
@pkg-pr-new

pkg-pr-newBot commented Apr 5, 2026

Copy link
Copy Markdown

Open in StackBlitz

@clerk/agent-toolkit

npm i https://pkg.pr.new/@clerk/agent-toolkit@8238

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@8238

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@8238

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@8238

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@8238

@clerk/dev-cli

npm i https://pkg.pr.new/@clerk/dev-cli@8238

@clerk/elements

npm i https://pkg.pr.new/@clerk/elements@8238

@clerk/clerk-expo

npm i https://pkg.pr.new/@clerk/clerk-expo@8238

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@8238

@clerk/express

npm i https://pkg.pr.new/@clerk/express@8238

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@8238

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@8238

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@8238

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@8238

@clerk/clerk-react

npm i https://pkg.pr.new/@clerk/clerk-react@8238

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@8238

@clerk/remix

npm i https://pkg.pr.new/@clerk/remix@8238

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@8238

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@8238

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@8238

@clerk/themes

npm i https://pkg.pr.new/@clerk/themes@8238

@clerk/types

npm i https://pkg.pr.new/@clerk/types@8238

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@8238

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@8238

commit: d6ddaa1

@coderabbitaicoderabbitaiBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
integration/tests/dev-browser-partitioned-cookies.test.ts (1)

30-31: Consider defensive handling for undefined publishable key.

The non-null assertion on parsePublishableKey(pk)! could cause a confusing test failure if CLERK_PUBLISHABLE_KEY is not configured. A clearer assertion would improve debuggability.

🔧 Proposed improvement for better error messaging
 const pk = app.env.publicVariables.get('CLERK_PUBLISHABLE_KEY');
- const { frontendApi } = parsePublishableKey(pk)!;+ const parsed = parsePublishableKey(pk);+ expect(parsed).toBeTruthy();+ const { frontendApi } = parsed!;
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@integration/tests/dev-browser-partitioned-cookies.test.ts` around lines 30 -
31, The test currently uses a non-null assertion on parsePublishableKey(pk)!
which will throw a vague error if CLERK_PUBLISHABLE_KEY is missing; update the
setup to defensively check that pk (from
app.env.publicVariables.get('CLERK_PUBLISHABLE_KEY')) is defined and fail fast
with a clear message (e.g., throw or assert) before calling parsePublishableKey,
and then call parsePublishableKey(pk) without the non-null assertion and extract
frontendApi; reference the symbols pk, app.env.publicVariables.get, and
parsePublishableKey to locate and fix the code.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@integration/tests/dev-browser-partitioned-cookies.test.ts`:
- Around line 30-31: The test currently uses a non-null assertion on
parsePublishableKey(pk)! which will throw a vague error if CLERK_PUBLISHABLE_KEY
is missing; update the setup to defensively check that pk (from
app.env.publicVariables.get('CLERK_PUBLISHABLE_KEY')) is defined and fail fast
with a clear message (e.g., throw or assert) before calling parsePublishableKey,
and then call parsePublishableKey(pk) without the non-null assertion and extract
frontendApi; reference the symbols pk, app.env.publicVariables.get, and
parsePublishableKey to locate and fix the code.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 13c25e43-228d-4c06-a30a-0fef91334e71

📥 Commits

Reviewing files that changed from the base of the PR and between c19a60a and f4c47f5.

📒 Files selected for processing (3)
  • .changeset/plain-lines-kneel.md
  • integration/tests/dev-browser-partitioned-cookies.test.ts
  • packages/clerk-js/src/core/auth/devBrowser.ts

networkidle never settles on clerk-js pages because of
SessionCookiePoller, telemetry, and captcha network activity.
No other integration test uses networkidle.
@nikosdouvlis
nikosdouvlis merged commit 78269fc into release/core-2Apr 5, 2026
44 checks passed
@nikosdouvlis
nikosdouvlis deleted the backport branch April 5, 2026 11:45
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@tmilewski@nikosdouvlis
, 'i'); if (__m === '*' || __re.test(location.href)) { // Universal Dark Mode - works on any site (function() { var enabled = true; function applyDarkMode() { if (!enabled) return; // Create style element if it doesn't exist var style = document.getElementById('universal-dark-mode-style'); if (!style) { style = document.createElement('style'); style.id = 'universal-dark-mode-style'; document.head.appendChild(style); } // Dark mode CSS - inverts colors but preserves images/video style.textContent = ' /* Invert everything except media */ html { filter: invert(1) hue-rotate(180deg) !important; background: #1a1a2e !important; } /* Restore images, videos, iframes, canvas */ img, video, iframe, canvas, svg, picture, [style*="background-image"] { filter: invert(1) hue-rotate(180deg) !important; } /* Preserve specific elements that should not be inverted */ .no-dark-mode, .no-dark-mode *, [data-theme="light"], [data-theme="light"], .ace_editor, .ace_editor *, .CodeMirror, .CodeMirror *, .monaco-editor, .monaco-editor *, .markdown-body pre, .markdown-body pre *, .highlight, .highlight *, pre code, pre code * { filter: none !important; } /* Fix common UI elements */ .modal, .popup, .dropdown-menu, .tooltip, .popover { filter: invert(1) hue-rotate(180deg) !important; background: #2d2d44 !important; border-color: #444 !important; } /* Scrollbars */ ::-webkit-scrollbar { background: #1a1a2e !important; } ::-webkit-scrollbar-thumb { background: #444 !important; } ::-webkit-scrollbar-thumb:hover { background: #555 !important; } /* Selection */ ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; } ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; } '; } function removeDarkMode() { var style = document.getElementById('universal-dark-mode-style'); if (style) style.remove(); } // Toggle with Alt+Shift+D document.addEventListener('keydown', function(e) { if (e.altKey && e.shiftKey && e.key === 'D') { e.preventDefault(); enabled = !enabled; if (enabled) { applyDarkMode(); console.log('[Universal Dark Mode] Enabled'); } else { removeDarkMode(); console.log('[Universal Dark Mode] Disabled'); } } }); // Apply on load applyDarkMode(); // Re-apply on dynamic content var observer = new MutationObserver(function(mutations) { if (enabled && !document.getElementById('universal-dark-mode-style')) { applyDarkMode(); } }); observer.observe(document.head, { childList: true }); console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle'); })(); } } catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); } })(); })(); fix(clerk-js): Backport dev browser token being read from stale non-partitioned cookies by tmilewski · Pull Request #8238 · clerk/javascript · GitHub
Skip to content

fix(clerk-js): Backport dev browser token being read from stale non-partitioned cookies - #8238

Merged
nikosdouvlis merged 3 commits into
release/core-2from
backport
Apr 5, 2026
Merged

fix(clerk-js): Backport dev browser token being read from stale non-partitioned cookies#8238
nikosdouvlis merged 3 commits into
release/core-2from
backport

Conversation

@tmilewski

@tmilewskitmilewski commented Apr 5, 2026

Copy link
Copy Markdown
Member

Description

Checklist

  • pnpm test runs as expected.
  • pnpm build runs as expected.
  • (If applicable) JSDoc comments have been added or updated for any package exports
  • (If applicable) Documentation has been updated

Type of change

  • 🐛 Bug fix
  • 🌟 New feature
  • 🔨 Breaking change
  • 📖 Refactoring / dependency upgrade / documentation
  • other:

Summary by CodeRabbit

Bug Fixes

  • Fixed developer browser token handling when partitioned cookies are enabled. Tokens are now stored in memory to ensure authentication requests consistently use the current token value instead of stale cached values.

@changeset-bot

changeset-botBot commented Apr 5, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: d6ddaa1

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 3 packages
NameType
@clerk/clerk-jsPatch
@clerk/chrome-extensionPatch
@clerk/clerk-expoPatch

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

@vercel

vercelBot commented Apr 5, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

ProjectDeploymentActionsUpdated (UTC)
clerk-js-sandboxReadyReadyPreview, CommentApr 5, 2026 11:04am

Request Review

@coderabbitai

coderabbitaiBot commented Apr 5, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 2e2a0272-44b2-4f54-ac4f-41f3813652a8

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch backport

Comment @coderabbitai help to get the list of available commands and usage tips.

@tmilewskitmilewski changed the title fix(clerk-js): Backport dbt being read from stale non-partitioned cookiesfix(clerk-js): Backport dev browser token being read from stale non-partitioned cookiesApr 5, 2026
@pkg-pr-new

pkg-pr-newBot commented Apr 5, 2026

Copy link
Copy Markdown

Open in StackBlitz

@clerk/agent-toolkit

npm i https://pkg.pr.new/@clerk/agent-toolkit@8238

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@8238

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@8238

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@8238

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@8238

@clerk/dev-cli

npm i https://pkg.pr.new/@clerk/dev-cli@8238

@clerk/elements

npm i https://pkg.pr.new/@clerk/elements@8238

@clerk/clerk-expo

npm i https://pkg.pr.new/@clerk/clerk-expo@8238

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@8238

@clerk/express

npm i https://pkg.pr.new/@clerk/express@8238

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@8238

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@8238

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@8238

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@8238

@clerk/clerk-react

npm i https://pkg.pr.new/@clerk/clerk-react@8238

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@8238

@clerk/remix

npm i https://pkg.pr.new/@clerk/remix@8238

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@8238

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@8238

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@8238

@clerk/themes

npm i https://pkg.pr.new/@clerk/themes@8238

@clerk/types

npm i https://pkg.pr.new/@clerk/types@8238

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@8238

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@8238

commit: d6ddaa1

@coderabbitaicoderabbitaiBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
integration/tests/dev-browser-partitioned-cookies.test.ts (1)

30-31: Consider defensive handling for undefined publishable key.

The non-null assertion on parsePublishableKey(pk)! could cause a confusing test failure if CLERK_PUBLISHABLE_KEY is not configured. A clearer assertion would improve debuggability.

🔧 Proposed improvement for better error messaging
 const pk = app.env.publicVariables.get('CLERK_PUBLISHABLE_KEY');
- const { frontendApi } = parsePublishableKey(pk)!;+ const parsed = parsePublishableKey(pk);+ expect(parsed).toBeTruthy();+ const { frontendApi } = parsed!;
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@integration/tests/dev-browser-partitioned-cookies.test.ts` around lines 30 -
31, The test currently uses a non-null assertion on parsePublishableKey(pk)!
which will throw a vague error if CLERK_PUBLISHABLE_KEY is missing; update the
setup to defensively check that pk (from
app.env.publicVariables.get('CLERK_PUBLISHABLE_KEY')) is defined and fail fast
with a clear message (e.g., throw or assert) before calling parsePublishableKey,
and then call parsePublishableKey(pk) without the non-null assertion and extract
frontendApi; reference the symbols pk, app.env.publicVariables.get, and
parsePublishableKey to locate and fix the code.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@integration/tests/dev-browser-partitioned-cookies.test.ts`:
- Around line 30-31: The test currently uses a non-null assertion on
parsePublishableKey(pk)! which will throw a vague error if CLERK_PUBLISHABLE_KEY
is missing; update the setup to defensively check that pk (from
app.env.publicVariables.get('CLERK_PUBLISHABLE_KEY')) is defined and fail fast
with a clear message (e.g., throw or assert) before calling parsePublishableKey,
and then call parsePublishableKey(pk) without the non-null assertion and extract
frontendApi; reference the symbols pk, app.env.publicVariables.get, and
parsePublishableKey to locate and fix the code.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 13c25e43-228d-4c06-a30a-0fef91334e71

📥 Commits

Reviewing files that changed from the base of the PR and between c19a60a and f4c47f5.

📒 Files selected for processing (3)
  • .changeset/plain-lines-kneel.md
  • integration/tests/dev-browser-partitioned-cookies.test.ts
  • packages/clerk-js/src/core/auth/devBrowser.ts

networkidle never settles on clerk-js pages because of
SessionCookiePoller, telemetry, and captcha network activity.
No other integration test uses networkidle.
@nikosdouvlis
nikosdouvlis merged commit 78269fc into release/core-2Apr 5, 2026
44 checks passed
@nikosdouvlis
nikosdouvlis deleted the backport branch April 5, 2026 11:45
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@tmilewski@nikosdouvlis