experiment: revert PR 8035 to test e2e impact - #8423

Closed
jacekradko wants to merge 1 commit into
mainfrom
jacek/revert-pr-8035-experiment
Closed

experiment: revert PR 8035 to test e2e impact#8423
jacekradko wants to merge 1 commit into
mainfrom
jacek/revert-pr-8035-experiment

Conversation

@jacekradko

Copy link
Copy Markdown
Contributor

Do not merge. Sandbox to verify whether reverting #8035 (auto-proxy for eligible hosts) flips the consistently-failing express / hono / generic / nextjs / billing / machine integration suites back to green.

If the integration matrix on this branch goes mostly green compared to recent runs on `main`, that confirms #8035 is the regression source. Will be closed regardless of outcome.

Related: #8422 (the actual fix PR currently open).

@vercel

vercelBot commented Apr 30, 2026

Copy link
Copy Markdown

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

ProjectDeploymentActionsUpdated (UTC)
clerk-js-sandboxReadyReadyPreview, CommentApr 30, 2026 3:45am

Request Review

@changeset-bot

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 2df6b35

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

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@pkg-pr-new

Copy link
Copy Markdown

Open in StackBlitz

@clerk/astro

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

@clerk/backend

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

@clerk/chrome-extension

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

@clerk/clerk-js

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

@clerk/dev-cli

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

@clerk/expo

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

@clerk/expo-passkeys

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

@clerk/express

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

@clerk/fastify

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

@clerk/hono

npm i https://pkg.pr.new/@clerk/hono@8423

@clerk/localizations

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

@clerk/nextjs

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

@clerk/nuxt

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

@clerk/react

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

@clerk/react-router

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

@clerk/shared

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

@clerk/tanstack-react-start

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

@clerk/testing

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

@clerk/ui

npm i https://pkg.pr.new/@clerk/ui@8423

@clerk/upgrade

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

@clerk/vue

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

commit: 2df6b35

@coderabbitai

Copy link
Copy Markdown
Contributor
📝 Walkthrough

Walkthrough

This pull request removes the automatic proxy URL detection and derivation feature across the Clerk monorepo. The changes eliminate environment-based auto-proxy logic from multiple layers: the backend authentication context, the clerk-js core initialization, the nextjs middleware, utility functions, and the shared proxy utilities. Additionally, relative proxy URL path handling in script loading is removed, and Vercel-specific environment variables are removed from Turbo's global task dependencies. Corresponding test coverage for auto-proxy behavior is deleted across all affected packages.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check nameStatusExplanation
Title check✅ PassedThe title clearly summarizes the main change: this PR reverts PR #8035 to test its e2e impact on failing integration tests.
Description check✅ PassedThe description directly relates to the changeset by explaining the revert of auto-proxy functionality and its purpose for testing integration suite outcomes.
Docstring Coverage✅ PassedDocstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
Linked Issues check✅ PassedCheck skipped because no linked issues were found for this pull request.
Out of Scope Changes check✅ PassedCheck skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


Review rate limit: 4/5 reviews remaining, refill in 12 minutes.

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

@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.

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
packages/shared/src/loadClerkJsScript.ts (1)

283-293: ⚠️ Potential issue | 🟠 Major | ⚡ Quick win

Preserve relative proxy URL handling here.

proxyUrl still accepts relative values, but this branch now routes them through browser-only normalization and then concatenates the result directly. That breaks server-side clerkJSScriptUrl / clerkUIScriptUrl callers and can emit malformed .../proxy//npm/... URLs when the proxy path has a trailing slash.

Please restore the previous relative-proxy path or normalize the proxy path before building the script host.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@packages/shared/src/loadClerkJsScript.ts` around lines 283 - 293,
buildScriptHost currently converts proxyUrl via proxyUrlToAbsoluteURL then
strips the protocol, which breaks server-side callers and produces malformed
paths when proxyUrl is a relative path (especially with trailing slash). Update
the proxyUrl branch in buildScriptHost to detect relative proxy URLs and either
(a) return the original relative path (preserving behavior for server-side
callers) or (b) normalize the proxy path by removing a trailing slash before
concatenation; use the existing helpers (isValidProxyUrl, proxyUrlToAbsoluteURL)
but ensure relative URLs bypass proxyUrlToAbsoluteURL or are normalized (trim
trailing slash) so buildScriptHost returns a correct host string for both server
and browser usage. Reference: function buildScriptHost, helper
proxyUrlToAbsoluteURL, and isValidProxyUrl.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Outside diff comments:
In `@packages/shared/src/loadClerkJsScript.ts`:
- Around line 283-293: buildScriptHost currently converts proxyUrl via
proxyUrlToAbsoluteURL then strips the protocol, which breaks server-side callers
and produces malformed paths when proxyUrl is a relative path (especially with
trailing slash). Update the proxyUrl branch in buildScriptHost to detect
relative proxy URLs and either (a) return the original relative path (preserving
behavior for server-side callers) or (b) normalize the proxy path by removing a
trailing slash before concatenation; use the existing helpers (isValidProxyUrl,
proxyUrlToAbsoluteURL) but ensure relative URLs bypass proxyUrlToAbsoluteURL or
are normalized (trim trailing slash) so buildScriptHost returns a correct host
string for both server and browser usage. Reference: function buildScriptHost,
helper proxyUrlToAbsoluteURL, and isValidProxyUrl.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: 1560bd88-b204-41af-ad90-7a1bce2428e1

📥 Commits

Reviewing files that changed from the base of the PR and between 61e0a78 and 2df6b35.

📒 Files selected for processing (14)
  • packages/backend/src/tokens/__tests__/authenticateContext.test.ts
  • packages/backend/src/tokens/authenticateContext.ts
  • packages/clerk-js/src/core/__tests__/clerk.test.ts
  • packages/clerk-js/src/core/clerk.ts
  • packages/nextjs/src/app-router/server/__tests__/DynamicClerkScripts.test.tsx
  • packages/nextjs/src/server/__tests__/clerkMiddleware.test.ts
  • packages/nextjs/src/server/clerkMiddleware.ts
  • packages/nextjs/src/utils/__tests__/mergeNextClerkPropsWithEnv.test.ts
  • packages/nextjs/src/utils/mergeNextClerkPropsWithEnv.ts
  • packages/shared/src/__tests__/loadClerkJsScript.spec.ts
  • packages/shared/src/__tests__/proxy.spec.ts
  • packages/shared/src/loadClerkJsScript.ts
  • packages/shared/src/proxy.ts
  • turbo.json
💤 Files with no reviewable changes (8)
  • turbo.json
  • packages/nextjs/src/app-router/server/tests/DynamicClerkScripts.test.tsx
  • packages/backend/src/tokens/authenticateContext.ts
  • packages/nextjs/src/server/tests/clerkMiddleware.test.ts
  • packages/clerk-js/src/core/tests/clerk.test.ts
  • packages/backend/src/tokens/tests/authenticateContext.test.ts
  • packages/nextjs/src/utils/tests/mergeNextClerkPropsWithEnv.test.ts
  • packages/shared/src/tests/loadClerkJsScript.spec.ts

@jacekradko

Copy link
Copy Markdown
ContributorAuthor

Closing — the same 5 express tests (and same hono/billing/etc. patterns) fail identically on this branch as on main. reverting #8035 (auto-proxy) does not fix the userButton mount regression. Pattern is consistent across all four candidate branches we tested (#8422, #8423, #8424, #8426), so the cause is environmental, not in the JS source. Refocusing on infra: Clerk dashboard config on the test instances, FAPI deploys, Blacksmith runner image, or pnpm/Playwright resolution drift.

@jacekradko
jacekradko deleted the jacek/revert-pr-8035-experiment branch April 30, 2026 19:03
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.

1 participant

@jacekradko
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all
 blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n 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;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks");
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
Skip to content

experiment: revert PR 8035 to test e2e impact - #8423

Closed
jacekradko wants to merge 1 commit into
mainfrom
jacek/revert-pr-8035-experiment
Closed

experiment: revert PR 8035 to test e2e impact#8423
jacekradko wants to merge 1 commit into
mainfrom
jacek/revert-pr-8035-experiment

Conversation

@jacekradko

Copy link
Copy Markdown
Contributor

Do not merge. Sandbox to verify whether reverting #8035 (auto-proxy for eligible hosts) flips the consistently-failing express / hono / generic / nextjs / billing / machine integration suites back to green.

If the integration matrix on this branch goes mostly green compared to recent runs on `main`, that confirms #8035 is the regression source. Will be closed regardless of outcome.

Related: #8422 (the actual fix PR currently open).

@vercel

vercelBot commented Apr 30, 2026

Copy link
Copy Markdown

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

ProjectDeploymentActionsUpdated (UTC)
clerk-js-sandboxReadyReadyPreview, CommentApr 30, 2026 3:45am

Request Review

@changeset-bot

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 2df6b35

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

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@pkg-pr-new

Copy link
Copy Markdown

Open in StackBlitz

@clerk/astro

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

@clerk/backend

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

@clerk/chrome-extension

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

@clerk/clerk-js

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

@clerk/dev-cli

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

@clerk/expo

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

@clerk/expo-passkeys

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

@clerk/express

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

@clerk/fastify

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

@clerk/hono

npm i https://pkg.pr.new/@clerk/hono@8423

@clerk/localizations

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

@clerk/nextjs

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

@clerk/nuxt

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

@clerk/react

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

@clerk/react-router

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

@clerk/shared

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

@clerk/tanstack-react-start

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

@clerk/testing

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

@clerk/ui

npm i https://pkg.pr.new/@clerk/ui@8423

@clerk/upgrade

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

@clerk/vue

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

commit: 2df6b35

@coderabbitai

Copy link
Copy Markdown
Contributor
📝 Walkthrough

Walkthrough

This pull request removes the automatic proxy URL detection and derivation feature across the Clerk monorepo. The changes eliminate environment-based auto-proxy logic from multiple layers: the backend authentication context, the clerk-js core initialization, the nextjs middleware, utility functions, and the shared proxy utilities. Additionally, relative proxy URL path handling in script loading is removed, and Vercel-specific environment variables are removed from Turbo's global task dependencies. Corresponding test coverage for auto-proxy behavior is deleted across all affected packages.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check nameStatusExplanation
Title check✅ PassedThe title clearly summarizes the main change: this PR reverts PR #8035 to test its e2e impact on failing integration tests.
Description check✅ PassedThe description directly relates to the changeset by explaining the revert of auto-proxy functionality and its purpose for testing integration suite outcomes.
Docstring Coverage✅ PassedDocstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
Linked Issues check✅ PassedCheck skipped because no linked issues were found for this pull request.
Out of Scope Changes check✅ PassedCheck skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


Review rate limit: 4/5 reviews remaining, refill in 12 minutes.

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

@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.

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
packages/shared/src/loadClerkJsScript.ts (1)

283-293: ⚠️ Potential issue | 🟠 Major | ⚡ Quick win

Preserve relative proxy URL handling here.

proxyUrl still accepts relative values, but this branch now routes them through browser-only normalization and then concatenates the result directly. That breaks server-side clerkJSScriptUrl / clerkUIScriptUrl callers and can emit malformed .../proxy//npm/... URLs when the proxy path has a trailing slash.

Please restore the previous relative-proxy path or normalize the proxy path before building the script host.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@packages/shared/src/loadClerkJsScript.ts` around lines 283 - 293,
buildScriptHost currently converts proxyUrl via proxyUrlToAbsoluteURL then
strips the protocol, which breaks server-side callers and produces malformed
paths when proxyUrl is a relative path (especially with trailing slash). Update
the proxyUrl branch in buildScriptHost to detect relative proxy URLs and either
(a) return the original relative path (preserving behavior for server-side
callers) or (b) normalize the proxy path by removing a trailing slash before
concatenation; use the existing helpers (isValidProxyUrl, proxyUrlToAbsoluteURL)
but ensure relative URLs bypass proxyUrlToAbsoluteURL or are normalized (trim
trailing slash) so buildScriptHost returns a correct host string for both server
and browser usage. Reference: function buildScriptHost, helper
proxyUrlToAbsoluteURL, and isValidProxyUrl.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Outside diff comments:
In `@packages/shared/src/loadClerkJsScript.ts`:
- Around line 283-293: buildScriptHost currently converts proxyUrl via
proxyUrlToAbsoluteURL then strips the protocol, which breaks server-side callers
and produces malformed paths when proxyUrl is a relative path (especially with
trailing slash). Update the proxyUrl branch in buildScriptHost to detect
relative proxy URLs and either (a) return the original relative path (preserving
behavior for server-side callers) or (b) normalize the proxy path by removing a
trailing slash before concatenation; use the existing helpers (isValidProxyUrl,
proxyUrlToAbsoluteURL) but ensure relative URLs bypass proxyUrlToAbsoluteURL or
are normalized (trim trailing slash) so buildScriptHost returns a correct host
string for both server and browser usage. Reference: function buildScriptHost,
helper proxyUrlToAbsoluteURL, and isValidProxyUrl.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: 1560bd88-b204-41af-ad90-7a1bce2428e1

📥 Commits

Reviewing files that changed from the base of the PR and between 61e0a78 and 2df6b35.

📒 Files selected for processing (14)
  • packages/backend/src/tokens/__tests__/authenticateContext.test.ts
  • packages/backend/src/tokens/authenticateContext.ts
  • packages/clerk-js/src/core/__tests__/clerk.test.ts
  • packages/clerk-js/src/core/clerk.ts
  • packages/nextjs/src/app-router/server/__tests__/DynamicClerkScripts.test.tsx
  • packages/nextjs/src/server/__tests__/clerkMiddleware.test.ts
  • packages/nextjs/src/server/clerkMiddleware.ts
  • packages/nextjs/src/utils/__tests__/mergeNextClerkPropsWithEnv.test.ts
  • packages/nextjs/src/utils/mergeNextClerkPropsWithEnv.ts
  • packages/shared/src/__tests__/loadClerkJsScript.spec.ts
  • packages/shared/src/__tests__/proxy.spec.ts
  • packages/shared/src/loadClerkJsScript.ts
  • packages/shared/src/proxy.ts
  • turbo.json
💤 Files with no reviewable changes (8)
  • turbo.json
  • packages/nextjs/src/app-router/server/tests/DynamicClerkScripts.test.tsx
  • packages/backend/src/tokens/authenticateContext.ts
  • packages/nextjs/src/server/tests/clerkMiddleware.test.ts
  • packages/clerk-js/src/core/tests/clerk.test.ts
  • packages/backend/src/tokens/tests/authenticateContext.test.ts
  • packages/nextjs/src/utils/tests/mergeNextClerkPropsWithEnv.test.ts
  • packages/shared/src/tests/loadClerkJsScript.spec.ts

@jacekradko

Copy link
Copy Markdown
ContributorAuthor

Closing — the same 5 express tests (and same hono/billing/etc. patterns) fail identically on this branch as on main. reverting #8035 (auto-proxy) does not fix the userButton mount regression. Pattern is consistent across all four candidate branches we tested (#8422, #8423, #8424, #8426), so the cause is environmental, not in the JS source. Refocusing on infra: Clerk dashboard config on the test instances, FAPI deploys, Blacksmith runner image, or pnpm/Playwright resolution drift.

@jacekradko
jacekradko deleted the jacek/revert-pr-8035-experiment branch April 30, 2026 19:03
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.

1 participant

@jacekradko
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix"); } } catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

experiment: revert PR 8035 to test e2e impact - #8423

Closed
jacekradko wants to merge 1 commit into
mainfrom
jacek/revert-pr-8035-experiment
Closed

experiment: revert PR 8035 to test e2e impact#8423
jacekradko wants to merge 1 commit into
mainfrom
jacek/revert-pr-8035-experiment

Conversation

@jacekradko

Copy link
Copy Markdown
Contributor

Do not merge. Sandbox to verify whether reverting #8035 (auto-proxy for eligible hosts) flips the consistently-failing express / hono / generic / nextjs / billing / machine integration suites back to green.

If the integration matrix on this branch goes mostly green compared to recent runs on `main`, that confirms #8035 is the regression source. Will be closed regardless of outcome.

Related: #8422 (the actual fix PR currently open).

@vercel

vercelBot commented Apr 30, 2026

Copy link
Copy Markdown

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

ProjectDeploymentActionsUpdated (UTC)
clerk-js-sandboxReadyReadyPreview, CommentApr 30, 2026 3:45am

Request Review

@changeset-bot

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 2df6b35

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

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@pkg-pr-new

Copy link
Copy Markdown

Open in StackBlitz

@clerk/astro

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

@clerk/backend

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

@clerk/chrome-extension

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

@clerk/clerk-js

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

@clerk/dev-cli

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

@clerk/expo

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

@clerk/expo-passkeys

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

@clerk/express

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

@clerk/fastify

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

@clerk/hono

npm i https://pkg.pr.new/@clerk/hono@8423

@clerk/localizations

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

@clerk/nextjs

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

@clerk/nuxt

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

@clerk/react

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

@clerk/react-router

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

@clerk/shared

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

@clerk/tanstack-react-start

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

@clerk/testing

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

@clerk/ui

npm i https://pkg.pr.new/@clerk/ui@8423

@clerk/upgrade

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

@clerk/vue

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

commit: 2df6b35

@coderabbitai

Copy link
Copy Markdown
Contributor
📝 Walkthrough

Walkthrough

This pull request removes the automatic proxy URL detection and derivation feature across the Clerk monorepo. The changes eliminate environment-based auto-proxy logic from multiple layers: the backend authentication context, the clerk-js core initialization, the nextjs middleware, utility functions, and the shared proxy utilities. Additionally, relative proxy URL path handling in script loading is removed, and Vercel-specific environment variables are removed from Turbo's global task dependencies. Corresponding test coverage for auto-proxy behavior is deleted across all affected packages.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check nameStatusExplanation
Title check✅ PassedThe title clearly summarizes the main change: this PR reverts PR #8035 to test its e2e impact on failing integration tests.
Description check✅ PassedThe description directly relates to the changeset by explaining the revert of auto-proxy functionality and its purpose for testing integration suite outcomes.
Docstring Coverage✅ PassedDocstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
Linked Issues check✅ PassedCheck skipped because no linked issues were found for this pull request.
Out of Scope Changes check✅ PassedCheck skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


Review rate limit: 4/5 reviews remaining, refill in 12 minutes.

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

@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.

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
packages/shared/src/loadClerkJsScript.ts (1)

283-293: ⚠️ Potential issue | 🟠 Major | ⚡ Quick win

Preserve relative proxy URL handling here.

proxyUrl still accepts relative values, but this branch now routes them through browser-only normalization and then concatenates the result directly. That breaks server-side clerkJSScriptUrl / clerkUIScriptUrl callers and can emit malformed .../proxy//npm/... URLs when the proxy path has a trailing slash.

Please restore the previous relative-proxy path or normalize the proxy path before building the script host.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@packages/shared/src/loadClerkJsScript.ts` around lines 283 - 293,
buildScriptHost currently converts proxyUrl via proxyUrlToAbsoluteURL then
strips the protocol, which breaks server-side callers and produces malformed
paths when proxyUrl is a relative path (especially with trailing slash). Update
the proxyUrl branch in buildScriptHost to detect relative proxy URLs and either
(a) return the original relative path (preserving behavior for server-side
callers) or (b) normalize the proxy path by removing a trailing slash before
concatenation; use the existing helpers (isValidProxyUrl, proxyUrlToAbsoluteURL)
but ensure relative URLs bypass proxyUrlToAbsoluteURL or are normalized (trim
trailing slash) so buildScriptHost returns a correct host string for both server
and browser usage. Reference: function buildScriptHost, helper
proxyUrlToAbsoluteURL, and isValidProxyUrl.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Outside diff comments:
In `@packages/shared/src/loadClerkJsScript.ts`:
- Around line 283-293: buildScriptHost currently converts proxyUrl via
proxyUrlToAbsoluteURL then strips the protocol, which breaks server-side callers
and produces malformed paths when proxyUrl is a relative path (especially with
trailing slash). Update the proxyUrl branch in buildScriptHost to detect
relative proxy URLs and either (a) return the original relative path (preserving
behavior for server-side callers) or (b) normalize the proxy path by removing a
trailing slash before concatenation; use the existing helpers (isValidProxyUrl,
proxyUrlToAbsoluteURL) but ensure relative URLs bypass proxyUrlToAbsoluteURL or
are normalized (trim trailing slash) so buildScriptHost returns a correct host
string for both server and browser usage. Reference: function buildScriptHost,
helper proxyUrlToAbsoluteURL, and isValidProxyUrl.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: 1560bd88-b204-41af-ad90-7a1bce2428e1

📥 Commits

Reviewing files that changed from the base of the PR and between 61e0a78 and 2df6b35.

📒 Files selected for processing (14)
  • packages/backend/src/tokens/__tests__/authenticateContext.test.ts
  • packages/backend/src/tokens/authenticateContext.ts
  • packages/clerk-js/src/core/__tests__/clerk.test.ts
  • packages/clerk-js/src/core/clerk.ts
  • packages/nextjs/src/app-router/server/__tests__/DynamicClerkScripts.test.tsx
  • packages/nextjs/src/server/__tests__/clerkMiddleware.test.ts
  • packages/nextjs/src/server/clerkMiddleware.ts
  • packages/nextjs/src/utils/__tests__/mergeNextClerkPropsWithEnv.test.ts
  • packages/nextjs/src/utils/mergeNextClerkPropsWithEnv.ts
  • packages/shared/src/__tests__/loadClerkJsScript.spec.ts
  • packages/shared/src/__tests__/proxy.spec.ts
  • packages/shared/src/loadClerkJsScript.ts
  • packages/shared/src/proxy.ts
  • turbo.json
💤 Files with no reviewable changes (8)
  • turbo.json
  • packages/nextjs/src/app-router/server/tests/DynamicClerkScripts.test.tsx
  • packages/backend/src/tokens/authenticateContext.ts
  • packages/nextjs/src/server/tests/clerkMiddleware.test.ts
  • packages/clerk-js/src/core/tests/clerk.test.ts
  • packages/backend/src/tokens/tests/authenticateContext.test.ts
  • packages/nextjs/src/utils/tests/mergeNextClerkPropsWithEnv.test.ts
  • packages/shared/src/tests/loadClerkJsScript.spec.ts

@jacekradko

Copy link
Copy Markdown
ContributorAuthor

Closing — the same 5 express tests (and same hono/billing/etc. patterns) fail identically on this branch as on main. reverting #8035 (auto-proxy) does not fix the userButton mount regression. Pattern is consistent across all four candidate branches we tested (#8422, #8423, #8424, #8426), so the cause is environmental, not in the JS source. Refocusing on infra: Clerk dashboard config on the test instances, FAPI deploys, Blacksmith runner image, or pnpm/Playwright resolution drift.

@jacekradko
jacekradko deleted the jacek/revert-pr-8035-experiment branch April 30, 2026 19:03
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.

1 participant

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

experiment: revert PR 8035 to test e2e impact - #8423

Closed
jacekradko wants to merge 1 commit into
mainfrom
jacek/revert-pr-8035-experiment
Closed

experiment: revert PR 8035 to test e2e impact#8423
jacekradko wants to merge 1 commit into
mainfrom
jacek/revert-pr-8035-experiment

Conversation

@jacekradko

Copy link
Copy Markdown
Contributor

Do not merge. Sandbox to verify whether reverting #8035 (auto-proxy for eligible hosts) flips the consistently-failing express / hono / generic / nextjs / billing / machine integration suites back to green.

If the integration matrix on this branch goes mostly green compared to recent runs on `main`, that confirms #8035 is the regression source. Will be closed regardless of outcome.

Related: #8422 (the actual fix PR currently open).

@vercel

vercelBot commented Apr 30, 2026

Copy link
Copy Markdown

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

ProjectDeploymentActionsUpdated (UTC)
clerk-js-sandboxReadyReadyPreview, CommentApr 30, 2026 3:45am

Request Review

@changeset-bot

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 2df6b35

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

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@pkg-pr-new

Copy link
Copy Markdown

Open in StackBlitz

@clerk/astro

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

@clerk/backend

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

@clerk/chrome-extension

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

@clerk/clerk-js

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

@clerk/dev-cli

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

@clerk/expo

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

@clerk/expo-passkeys

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

@clerk/express

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

@clerk/fastify

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

@clerk/hono

npm i https://pkg.pr.new/@clerk/hono@8423

@clerk/localizations

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

@clerk/nextjs

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

@clerk/nuxt

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

@clerk/react

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

@clerk/react-router

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

@clerk/shared

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

@clerk/tanstack-react-start

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

@clerk/testing

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

@clerk/ui

npm i https://pkg.pr.new/@clerk/ui@8423

@clerk/upgrade

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

@clerk/vue

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

commit: 2df6b35

@coderabbitai

Copy link
Copy Markdown
Contributor
📝 Walkthrough

Walkthrough

This pull request removes the automatic proxy URL detection and derivation feature across the Clerk monorepo. The changes eliminate environment-based auto-proxy logic from multiple layers: the backend authentication context, the clerk-js core initialization, the nextjs middleware, utility functions, and the shared proxy utilities. Additionally, relative proxy URL path handling in script loading is removed, and Vercel-specific environment variables are removed from Turbo's global task dependencies. Corresponding test coverage for auto-proxy behavior is deleted across all affected packages.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check nameStatusExplanation
Title check✅ PassedThe title clearly summarizes the main change: this PR reverts PR #8035 to test its e2e impact on failing integration tests.
Description check✅ PassedThe description directly relates to the changeset by explaining the revert of auto-proxy functionality and its purpose for testing integration suite outcomes.
Docstring Coverage✅ PassedDocstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
Linked Issues check✅ PassedCheck skipped because no linked issues were found for this pull request.
Out of Scope Changes check✅ PassedCheck skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


Review rate limit: 4/5 reviews remaining, refill in 12 minutes.

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

@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.

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
packages/shared/src/loadClerkJsScript.ts (1)

283-293: ⚠️ Potential issue | 🟠 Major | ⚡ Quick win

Preserve relative proxy URL handling here.

proxyUrl still accepts relative values, but this branch now routes them through browser-only normalization and then concatenates the result directly. That breaks server-side clerkJSScriptUrl / clerkUIScriptUrl callers and can emit malformed .../proxy//npm/... URLs when the proxy path has a trailing slash.

Please restore the previous relative-proxy path or normalize the proxy path before building the script host.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@packages/shared/src/loadClerkJsScript.ts` around lines 283 - 293,
buildScriptHost currently converts proxyUrl via proxyUrlToAbsoluteURL then
strips the protocol, which breaks server-side callers and produces malformed
paths when proxyUrl is a relative path (especially with trailing slash). Update
the proxyUrl branch in buildScriptHost to detect relative proxy URLs and either
(a) return the original relative path (preserving behavior for server-side
callers) or (b) normalize the proxy path by removing a trailing slash before
concatenation; use the existing helpers (isValidProxyUrl, proxyUrlToAbsoluteURL)
but ensure relative URLs bypass proxyUrlToAbsoluteURL or are normalized (trim
trailing slash) so buildScriptHost returns a correct host string for both server
and browser usage. Reference: function buildScriptHost, helper
proxyUrlToAbsoluteURL, and isValidProxyUrl.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Outside diff comments:
In `@packages/shared/src/loadClerkJsScript.ts`:
- Around line 283-293: buildScriptHost currently converts proxyUrl via
proxyUrlToAbsoluteURL then strips the protocol, which breaks server-side callers
and produces malformed paths when proxyUrl is a relative path (especially with
trailing slash). Update the proxyUrl branch in buildScriptHost to detect
relative proxy URLs and either (a) return the original relative path (preserving
behavior for server-side callers) or (b) normalize the proxy path by removing a
trailing slash before concatenation; use the existing helpers (isValidProxyUrl,
proxyUrlToAbsoluteURL) but ensure relative URLs bypass proxyUrlToAbsoluteURL or
are normalized (trim trailing slash) so buildScriptHost returns a correct host
string for both server and browser usage. Reference: function buildScriptHost,
helper proxyUrlToAbsoluteURL, and isValidProxyUrl.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: 1560bd88-b204-41af-ad90-7a1bce2428e1

📥 Commits

Reviewing files that changed from the base of the PR and between 61e0a78 and 2df6b35.

📒 Files selected for processing (14)
  • packages/backend/src/tokens/__tests__/authenticateContext.test.ts
  • packages/backend/src/tokens/authenticateContext.ts
  • packages/clerk-js/src/core/__tests__/clerk.test.ts
  • packages/clerk-js/src/core/clerk.ts
  • packages/nextjs/src/app-router/server/__tests__/DynamicClerkScripts.test.tsx
  • packages/nextjs/src/server/__tests__/clerkMiddleware.test.ts
  • packages/nextjs/src/server/clerkMiddleware.ts
  • packages/nextjs/src/utils/__tests__/mergeNextClerkPropsWithEnv.test.ts
  • packages/nextjs/src/utils/mergeNextClerkPropsWithEnv.ts
  • packages/shared/src/__tests__/loadClerkJsScript.spec.ts
  • packages/shared/src/__tests__/proxy.spec.ts
  • packages/shared/src/loadClerkJsScript.ts
  • packages/shared/src/proxy.ts
  • turbo.json
💤 Files with no reviewable changes (8)
  • turbo.json
  • packages/nextjs/src/app-router/server/tests/DynamicClerkScripts.test.tsx
  • packages/backend/src/tokens/authenticateContext.ts
  • packages/nextjs/src/server/tests/clerkMiddleware.test.ts
  • packages/clerk-js/src/core/tests/clerk.test.ts
  • packages/backend/src/tokens/tests/authenticateContext.test.ts
  • packages/nextjs/src/utils/tests/mergeNextClerkPropsWithEnv.test.ts
  • packages/shared/src/tests/loadClerkJsScript.spec.ts

@jacekradko

Copy link
Copy Markdown
ContributorAuthor

Closing — the same 5 express tests (and same hono/billing/etc. patterns) fail identically on this branch as on main. reverting #8035 (auto-proxy) does not fix the userButton mount regression. Pattern is consistent across all four candidate branches we tested (#8422, #8423, #8424, #8426), so the cause is environmental, not in the JS source. Refocusing on infra: Clerk dashboard config on the test instances, FAPI deploys, Blacksmith runner image, or pnpm/Playwright resolution drift.

@jacekradko
jacekradko deleted the jacek/revert-pr-8035-experiment branch April 30, 2026 19:03
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.

1 participant

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

experiment: revert PR 8035 to test e2e impact - #8423

Closed
jacekradko wants to merge 1 commit into
mainfrom
jacek/revert-pr-8035-experiment
Closed

experiment: revert PR 8035 to test e2e impact#8423
jacekradko wants to merge 1 commit into
mainfrom
jacek/revert-pr-8035-experiment

Conversation

@jacekradko

Copy link
Copy Markdown
Contributor

Do not merge. Sandbox to verify whether reverting #8035 (auto-proxy for eligible hosts) flips the consistently-failing express / hono / generic / nextjs / billing / machine integration suites back to green.

If the integration matrix on this branch goes mostly green compared to recent runs on `main`, that confirms #8035 is the regression source. Will be closed regardless of outcome.

Related: #8422 (the actual fix PR currently open).

@vercel

vercelBot commented Apr 30, 2026

Copy link
Copy Markdown

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

ProjectDeploymentActionsUpdated (UTC)
clerk-js-sandboxReadyReadyPreview, CommentApr 30, 2026 3:45am

Request Review

@changeset-bot

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 2df6b35

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

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@pkg-pr-new

Copy link
Copy Markdown

Open in StackBlitz

@clerk/astro

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

@clerk/backend

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

@clerk/chrome-extension

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

@clerk/clerk-js

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

@clerk/dev-cli

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

@clerk/expo

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

@clerk/expo-passkeys

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

@clerk/express

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

@clerk/fastify

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

@clerk/hono

npm i https://pkg.pr.new/@clerk/hono@8423

@clerk/localizations

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

@clerk/nextjs

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

@clerk/nuxt

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

@clerk/react

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

@clerk/react-router

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

@clerk/shared

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

@clerk/tanstack-react-start

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

@clerk/testing

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

@clerk/ui

npm i https://pkg.pr.new/@clerk/ui@8423

@clerk/upgrade

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

@clerk/vue

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

commit: 2df6b35

@coderabbitai

Copy link
Copy Markdown
Contributor
📝 Walkthrough

Walkthrough

This pull request removes the automatic proxy URL detection and derivation feature across the Clerk monorepo. The changes eliminate environment-based auto-proxy logic from multiple layers: the backend authentication context, the clerk-js core initialization, the nextjs middleware, utility functions, and the shared proxy utilities. Additionally, relative proxy URL path handling in script loading is removed, and Vercel-specific environment variables are removed from Turbo's global task dependencies. Corresponding test coverage for auto-proxy behavior is deleted across all affected packages.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check nameStatusExplanation
Title check✅ PassedThe title clearly summarizes the main change: this PR reverts PR #8035 to test its e2e impact on failing integration tests.
Description check✅ PassedThe description directly relates to the changeset by explaining the revert of auto-proxy functionality and its purpose for testing integration suite outcomes.
Docstring Coverage✅ PassedDocstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
Linked Issues check✅ PassedCheck skipped because no linked issues were found for this pull request.
Out of Scope Changes check✅ PassedCheck skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


Review rate limit: 4/5 reviews remaining, refill in 12 minutes.

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

@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.

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
packages/shared/src/loadClerkJsScript.ts (1)

283-293: ⚠️ Potential issue | 🟠 Major | ⚡ Quick win

Preserve relative proxy URL handling here.

proxyUrl still accepts relative values, but this branch now routes them through browser-only normalization and then concatenates the result directly. That breaks server-side clerkJSScriptUrl / clerkUIScriptUrl callers and can emit malformed .../proxy//npm/... URLs when the proxy path has a trailing slash.

Please restore the previous relative-proxy path or normalize the proxy path before building the script host.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@packages/shared/src/loadClerkJsScript.ts` around lines 283 - 293,
buildScriptHost currently converts proxyUrl via proxyUrlToAbsoluteURL then
strips the protocol, which breaks server-side callers and produces malformed
paths when proxyUrl is a relative path (especially with trailing slash). Update
the proxyUrl branch in buildScriptHost to detect relative proxy URLs and either
(a) return the original relative path (preserving behavior for server-side
callers) or (b) normalize the proxy path by removing a trailing slash before
concatenation; use the existing helpers (isValidProxyUrl, proxyUrlToAbsoluteURL)
but ensure relative URLs bypass proxyUrlToAbsoluteURL or are normalized (trim
trailing slash) so buildScriptHost returns a correct host string for both server
and browser usage. Reference: function buildScriptHost, helper
proxyUrlToAbsoluteURL, and isValidProxyUrl.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Outside diff comments:
In `@packages/shared/src/loadClerkJsScript.ts`:
- Around line 283-293: buildScriptHost currently converts proxyUrl via
proxyUrlToAbsoluteURL then strips the protocol, which breaks server-side callers
and produces malformed paths when proxyUrl is a relative path (especially with
trailing slash). Update the proxyUrl branch in buildScriptHost to detect
relative proxy URLs and either (a) return the original relative path (preserving
behavior for server-side callers) or (b) normalize the proxy path by removing a
trailing slash before concatenation; use the existing helpers (isValidProxyUrl,
proxyUrlToAbsoluteURL) but ensure relative URLs bypass proxyUrlToAbsoluteURL or
are normalized (trim trailing slash) so buildScriptHost returns a correct host
string for both server and browser usage. Reference: function buildScriptHost,
helper proxyUrlToAbsoluteURL, and isValidProxyUrl.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: 1560bd88-b204-41af-ad90-7a1bce2428e1

📥 Commits

Reviewing files that changed from the base of the PR and between 61e0a78 and 2df6b35.

📒 Files selected for processing (14)
  • packages/backend/src/tokens/__tests__/authenticateContext.test.ts
  • packages/backend/src/tokens/authenticateContext.ts
  • packages/clerk-js/src/core/__tests__/clerk.test.ts
  • packages/clerk-js/src/core/clerk.ts
  • packages/nextjs/src/app-router/server/__tests__/DynamicClerkScripts.test.tsx
  • packages/nextjs/src/server/__tests__/clerkMiddleware.test.ts
  • packages/nextjs/src/server/clerkMiddleware.ts
  • packages/nextjs/src/utils/__tests__/mergeNextClerkPropsWithEnv.test.ts
  • packages/nextjs/src/utils/mergeNextClerkPropsWithEnv.ts
  • packages/shared/src/__tests__/loadClerkJsScript.spec.ts
  • packages/shared/src/__tests__/proxy.spec.ts
  • packages/shared/src/loadClerkJsScript.ts
  • packages/shared/src/proxy.ts
  • turbo.json
💤 Files with no reviewable changes (8)
  • turbo.json
  • packages/nextjs/src/app-router/server/tests/DynamicClerkScripts.test.tsx
  • packages/backend/src/tokens/authenticateContext.ts
  • packages/nextjs/src/server/tests/clerkMiddleware.test.ts
  • packages/clerk-js/src/core/tests/clerk.test.ts
  • packages/backend/src/tokens/tests/authenticateContext.test.ts
  • packages/nextjs/src/utils/tests/mergeNextClerkPropsWithEnv.test.ts
  • packages/shared/src/tests/loadClerkJsScript.spec.ts

@jacekradko

Copy link
Copy Markdown
ContributorAuthor

Closing — the same 5 express tests (and same hono/billing/etc. patterns) fail identically on this branch as on main. reverting #8035 (auto-proxy) does not fix the userButton mount regression. Pattern is consistent across all four candidate branches we tested (#8422, #8423, #8424, #8426), so the cause is environmental, not in the JS source. Refocusing on infra: Clerk dashboard config on the test instances, FAPI deploys, Blacksmith runner image, or pnpm/Playwright resolution drift.

@jacekradko
jacekradko deleted the jacek/revert-pr-8035-experiment branch April 30, 2026 19:03
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.

1 participant

@jacekradko
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default"); } } catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

experiment: revert PR 8035 to test e2e impact - #8423

Closed
jacekradko wants to merge 1 commit into
mainfrom
jacek/revert-pr-8035-experiment
Closed

experiment: revert PR 8035 to test e2e impact#8423
jacekradko wants to merge 1 commit into
mainfrom
jacek/revert-pr-8035-experiment

Conversation

@jacekradko

Copy link
Copy Markdown
Contributor

Do not merge. Sandbox to verify whether reverting #8035 (auto-proxy for eligible hosts) flips the consistently-failing express / hono / generic / nextjs / billing / machine integration suites back to green.

If the integration matrix on this branch goes mostly green compared to recent runs on `main`, that confirms #8035 is the regression source. Will be closed regardless of outcome.

Related: #8422 (the actual fix PR currently open).

@vercel

vercelBot commented Apr 30, 2026

Copy link
Copy Markdown

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

ProjectDeploymentActionsUpdated (UTC)
clerk-js-sandboxReadyReadyPreview, CommentApr 30, 2026 3:45am

Request Review

@changeset-bot

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 2df6b35

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

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@pkg-pr-new

Copy link
Copy Markdown

Open in StackBlitz

@clerk/astro

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

@clerk/backend

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

@clerk/chrome-extension

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

@clerk/clerk-js

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

@clerk/dev-cli

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

@clerk/expo

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

@clerk/expo-passkeys

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

@clerk/express

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

@clerk/fastify

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

@clerk/hono

npm i https://pkg.pr.new/@clerk/hono@8423

@clerk/localizations

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

@clerk/nextjs

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

@clerk/nuxt

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

@clerk/react

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

@clerk/react-router

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

@clerk/shared

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

@clerk/tanstack-react-start

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

@clerk/testing

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

@clerk/ui

npm i https://pkg.pr.new/@clerk/ui@8423

@clerk/upgrade

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

@clerk/vue

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

commit: 2df6b35

@coderabbitai

Copy link
Copy Markdown
Contributor
📝 Walkthrough

Walkthrough

This pull request removes the automatic proxy URL detection and derivation feature across the Clerk monorepo. The changes eliminate environment-based auto-proxy logic from multiple layers: the backend authentication context, the clerk-js core initialization, the nextjs middleware, utility functions, and the shared proxy utilities. Additionally, relative proxy URL path handling in script loading is removed, and Vercel-specific environment variables are removed from Turbo's global task dependencies. Corresponding test coverage for auto-proxy behavior is deleted across all affected packages.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check nameStatusExplanation
Title check✅ PassedThe title clearly summarizes the main change: this PR reverts PR #8035 to test its e2e impact on failing integration tests.
Description check✅ PassedThe description directly relates to the changeset by explaining the revert of auto-proxy functionality and its purpose for testing integration suite outcomes.
Docstring Coverage✅ PassedDocstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
Linked Issues check✅ PassedCheck skipped because no linked issues were found for this pull request.
Out of Scope Changes check✅ PassedCheck skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


Review rate limit: 4/5 reviews remaining, refill in 12 minutes.

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

@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.

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
packages/shared/src/loadClerkJsScript.ts (1)

283-293: ⚠️ Potential issue | 🟠 Major | ⚡ Quick win

Preserve relative proxy URL handling here.

proxyUrl still accepts relative values, but this branch now routes them through browser-only normalization and then concatenates the result directly. That breaks server-side clerkJSScriptUrl / clerkUIScriptUrl callers and can emit malformed .../proxy//npm/... URLs when the proxy path has a trailing slash.

Please restore the previous relative-proxy path or normalize the proxy path before building the script host.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@packages/shared/src/loadClerkJsScript.ts` around lines 283 - 293,
buildScriptHost currently converts proxyUrl via proxyUrlToAbsoluteURL then
strips the protocol, which breaks server-side callers and produces malformed
paths when proxyUrl is a relative path (especially with trailing slash). Update
the proxyUrl branch in buildScriptHost to detect relative proxy URLs and either
(a) return the original relative path (preserving behavior for server-side
callers) or (b) normalize the proxy path by removing a trailing slash before
concatenation; use the existing helpers (isValidProxyUrl, proxyUrlToAbsoluteURL)
but ensure relative URLs bypass proxyUrlToAbsoluteURL or are normalized (trim
trailing slash) so buildScriptHost returns a correct host string for both server
and browser usage. Reference: function buildScriptHost, helper
proxyUrlToAbsoluteURL, and isValidProxyUrl.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Outside diff comments:
In `@packages/shared/src/loadClerkJsScript.ts`:
- Around line 283-293: buildScriptHost currently converts proxyUrl via
proxyUrlToAbsoluteURL then strips the protocol, which breaks server-side callers
and produces malformed paths when proxyUrl is a relative path (especially with
trailing slash). Update the proxyUrl branch in buildScriptHost to detect
relative proxy URLs and either (a) return the original relative path (preserving
behavior for server-side callers) or (b) normalize the proxy path by removing a
trailing slash before concatenation; use the existing helpers (isValidProxyUrl,
proxyUrlToAbsoluteURL) but ensure relative URLs bypass proxyUrlToAbsoluteURL or
are normalized (trim trailing slash) so buildScriptHost returns a correct host
string for both server and browser usage. Reference: function buildScriptHost,
helper proxyUrlToAbsoluteURL, and isValidProxyUrl.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: 1560bd88-b204-41af-ad90-7a1bce2428e1

📥 Commits

Reviewing files that changed from the base of the PR and between 61e0a78 and 2df6b35.

📒 Files selected for processing (14)
  • packages/backend/src/tokens/__tests__/authenticateContext.test.ts
  • packages/backend/src/tokens/authenticateContext.ts
  • packages/clerk-js/src/core/__tests__/clerk.test.ts
  • packages/clerk-js/src/core/clerk.ts
  • packages/nextjs/src/app-router/server/__tests__/DynamicClerkScripts.test.tsx
  • packages/nextjs/src/server/__tests__/clerkMiddleware.test.ts
  • packages/nextjs/src/server/clerkMiddleware.ts
  • packages/nextjs/src/utils/__tests__/mergeNextClerkPropsWithEnv.test.ts
  • packages/nextjs/src/utils/mergeNextClerkPropsWithEnv.ts
  • packages/shared/src/__tests__/loadClerkJsScript.spec.ts
  • packages/shared/src/__tests__/proxy.spec.ts
  • packages/shared/src/loadClerkJsScript.ts
  • packages/shared/src/proxy.ts
  • turbo.json
💤 Files with no reviewable changes (8)
  • turbo.json
  • packages/nextjs/src/app-router/server/tests/DynamicClerkScripts.test.tsx
  • packages/backend/src/tokens/authenticateContext.ts
  • packages/nextjs/src/server/tests/clerkMiddleware.test.ts
  • packages/clerk-js/src/core/tests/clerk.test.ts
  • packages/backend/src/tokens/tests/authenticateContext.test.ts
  • packages/nextjs/src/utils/tests/mergeNextClerkPropsWithEnv.test.ts
  • packages/shared/src/tests/loadClerkJsScript.spec.ts

@jacekradko

Copy link
Copy Markdown
ContributorAuthor

Closing — the same 5 express tests (and same hono/billing/etc. patterns) fail identically on this branch as on main. reverting #8035 (auto-proxy) does not fix the userButton mount regression. Pattern is consistent across all four candidate branches we tested (#8422, #8423, #8424, #8426), so the cause is environmental, not in the JS source. Refocusing on infra: Clerk dashboard config on the test instances, FAPI deploys, Blacksmith runner image, or pnpm/Playwright resolution drift.

@jacekradko
jacekradko deleted the jacek/revert-pr-8035-experiment branch April 30, 2026 19:03
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.

1 participant

@jacekradko
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers"); } } catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

experiment: revert PR 8035 to test e2e impact - #8423

Closed
jacekradko wants to merge 1 commit into
mainfrom
jacek/revert-pr-8035-experiment
Closed

experiment: revert PR 8035 to test e2e impact#8423
jacekradko wants to merge 1 commit into
mainfrom
jacek/revert-pr-8035-experiment

Conversation

@jacekradko

Copy link
Copy Markdown
Contributor

Do not merge. Sandbox to verify whether reverting #8035 (auto-proxy for eligible hosts) flips the consistently-failing express / hono / generic / nextjs / billing / machine integration suites back to green.

If the integration matrix on this branch goes mostly green compared to recent runs on `main`, that confirms #8035 is the regression source. Will be closed regardless of outcome.

Related: #8422 (the actual fix PR currently open).

@vercel

vercelBot commented Apr 30, 2026

Copy link
Copy Markdown

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

ProjectDeploymentActionsUpdated (UTC)
clerk-js-sandboxReadyReadyPreview, CommentApr 30, 2026 3:45am

Request Review

@changeset-bot

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 2df6b35

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

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@pkg-pr-new

Copy link
Copy Markdown

Open in StackBlitz

@clerk/astro

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

@clerk/backend

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

@clerk/chrome-extension

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

@clerk/clerk-js

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

@clerk/dev-cli

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

@clerk/expo

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

@clerk/expo-passkeys

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

@clerk/express

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

@clerk/fastify

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

@clerk/hono

npm i https://pkg.pr.new/@clerk/hono@8423

@clerk/localizations

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

@clerk/nextjs

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

@clerk/nuxt

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

@clerk/react

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

@clerk/react-router

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

@clerk/shared

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

@clerk/tanstack-react-start

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

@clerk/testing

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

@clerk/ui

npm i https://pkg.pr.new/@clerk/ui@8423

@clerk/upgrade

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

@clerk/vue

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

commit: 2df6b35

@coderabbitai

Copy link
Copy Markdown
Contributor
📝 Walkthrough

Walkthrough

This pull request removes the automatic proxy URL detection and derivation feature across the Clerk monorepo. The changes eliminate environment-based auto-proxy logic from multiple layers: the backend authentication context, the clerk-js core initialization, the nextjs middleware, utility functions, and the shared proxy utilities. Additionally, relative proxy URL path handling in script loading is removed, and Vercel-specific environment variables are removed from Turbo's global task dependencies. Corresponding test coverage for auto-proxy behavior is deleted across all affected packages.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check nameStatusExplanation
Title check✅ PassedThe title clearly summarizes the main change: this PR reverts PR #8035 to test its e2e impact on failing integration tests.
Description check✅ PassedThe description directly relates to the changeset by explaining the revert of auto-proxy functionality and its purpose for testing integration suite outcomes.
Docstring Coverage✅ PassedDocstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
Linked Issues check✅ PassedCheck skipped because no linked issues were found for this pull request.
Out of Scope Changes check✅ PassedCheck skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


Review rate limit: 4/5 reviews remaining, refill in 12 minutes.

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

@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.

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
packages/shared/src/loadClerkJsScript.ts (1)

283-293: ⚠️ Potential issue | 🟠 Major | ⚡ Quick win

Preserve relative proxy URL handling here.

proxyUrl still accepts relative values, but this branch now routes them through browser-only normalization and then concatenates the result directly. That breaks server-side clerkJSScriptUrl / clerkUIScriptUrl callers and can emit malformed .../proxy//npm/... URLs when the proxy path has a trailing slash.

Please restore the previous relative-proxy path or normalize the proxy path before building the script host.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@packages/shared/src/loadClerkJsScript.ts` around lines 283 - 293,
buildScriptHost currently converts proxyUrl via proxyUrlToAbsoluteURL then
strips the protocol, which breaks server-side callers and produces malformed
paths when proxyUrl is a relative path (especially with trailing slash). Update
the proxyUrl branch in buildScriptHost to detect relative proxy URLs and either
(a) return the original relative path (preserving behavior for server-side
callers) or (b) normalize the proxy path by removing a trailing slash before
concatenation; use the existing helpers (isValidProxyUrl, proxyUrlToAbsoluteURL)
but ensure relative URLs bypass proxyUrlToAbsoluteURL or are normalized (trim
trailing slash) so buildScriptHost returns a correct host string for both server
and browser usage. Reference: function buildScriptHost, helper
proxyUrlToAbsoluteURL, and isValidProxyUrl.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Outside diff comments:
In `@packages/shared/src/loadClerkJsScript.ts`:
- Around line 283-293: buildScriptHost currently converts proxyUrl via
proxyUrlToAbsoluteURL then strips the protocol, which breaks server-side callers
and produces malformed paths when proxyUrl is a relative path (especially with
trailing slash). Update the proxyUrl branch in buildScriptHost to detect
relative proxy URLs and either (a) return the original relative path (preserving
behavior for server-side callers) or (b) normalize the proxy path by removing a
trailing slash before concatenation; use the existing helpers (isValidProxyUrl,
proxyUrlToAbsoluteURL) but ensure relative URLs bypass proxyUrlToAbsoluteURL or
are normalized (trim trailing slash) so buildScriptHost returns a correct host
string for both server and browser usage. Reference: function buildScriptHost,
helper proxyUrlToAbsoluteURL, and isValidProxyUrl.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: 1560bd88-b204-41af-ad90-7a1bce2428e1

📥 Commits

Reviewing files that changed from the base of the PR and between 61e0a78 and 2df6b35.

📒 Files selected for processing (14)
  • packages/backend/src/tokens/__tests__/authenticateContext.test.ts
  • packages/backend/src/tokens/authenticateContext.ts
  • packages/clerk-js/src/core/__tests__/clerk.test.ts
  • packages/clerk-js/src/core/clerk.ts
  • packages/nextjs/src/app-router/server/__tests__/DynamicClerkScripts.test.tsx
  • packages/nextjs/src/server/__tests__/clerkMiddleware.test.ts
  • packages/nextjs/src/server/clerkMiddleware.ts
  • packages/nextjs/src/utils/__tests__/mergeNextClerkPropsWithEnv.test.ts
  • packages/nextjs/src/utils/mergeNextClerkPropsWithEnv.ts
  • packages/shared/src/__tests__/loadClerkJsScript.spec.ts
  • packages/shared/src/__tests__/proxy.spec.ts
  • packages/shared/src/loadClerkJsScript.ts
  • packages/shared/src/proxy.ts
  • turbo.json
💤 Files with no reviewable changes (8)
  • turbo.json
  • packages/nextjs/src/app-router/server/tests/DynamicClerkScripts.test.tsx
  • packages/backend/src/tokens/authenticateContext.ts
  • packages/nextjs/src/server/tests/clerkMiddleware.test.ts
  • packages/clerk-js/src/core/tests/clerk.test.ts
  • packages/backend/src/tokens/tests/authenticateContext.test.ts
  • packages/nextjs/src/utils/tests/mergeNextClerkPropsWithEnv.test.ts
  • packages/shared/src/tests/loadClerkJsScript.spec.ts

@jacekradko

Copy link
Copy Markdown
ContributorAuthor

Closing — the same 5 express tests (and same hono/billing/etc. patterns) fail identically on this branch as on main. reverting #8035 (auto-proxy) does not fix the userButton mount regression. Pattern is consistent across all four candidate branches we tested (#8422, #8423, #8424, #8426), so the cause is environmental, not in the JS source. Refocusing on infra: Clerk dashboard config on the test instances, FAPI deploys, Blacksmith runner image, or pnpm/Playwright resolution drift.

@jacekradko
jacekradko deleted the jacek/revert-pr-8035-experiment branch April 30, 2026 19:03
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.

1 participant

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

experiment: revert PR 8035 to test e2e impact - #8423

Closed
jacekradko wants to merge 1 commit into
mainfrom
jacek/revert-pr-8035-experiment
Closed

experiment: revert PR 8035 to test e2e impact#8423
jacekradko wants to merge 1 commit into
mainfrom
jacek/revert-pr-8035-experiment

Conversation

@jacekradko

Copy link
Copy Markdown
Contributor

Do not merge. Sandbox to verify whether reverting #8035 (auto-proxy for eligible hosts) flips the consistently-failing express / hono / generic / nextjs / billing / machine integration suites back to green.

If the integration matrix on this branch goes mostly green compared to recent runs on `main`, that confirms #8035 is the regression source. Will be closed regardless of outcome.

Related: #8422 (the actual fix PR currently open).

@vercel

vercelBot commented Apr 30, 2026

Copy link
Copy Markdown

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

ProjectDeploymentActionsUpdated (UTC)
clerk-js-sandboxReadyReadyPreview, CommentApr 30, 2026 3:45am

Request Review

@changeset-bot

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 2df6b35

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

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@pkg-pr-new

Copy link
Copy Markdown

Open in StackBlitz

@clerk/astro

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

@clerk/backend

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

@clerk/chrome-extension

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

@clerk/clerk-js

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

@clerk/dev-cli

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

@clerk/expo

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

@clerk/expo-passkeys

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

@clerk/express

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

@clerk/fastify

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

@clerk/hono

npm i https://pkg.pr.new/@clerk/hono@8423

@clerk/localizations

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

@clerk/nextjs

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

@clerk/nuxt

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

@clerk/react

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

@clerk/react-router

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

@clerk/shared

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

@clerk/tanstack-react-start

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

@clerk/testing

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

@clerk/ui

npm i https://pkg.pr.new/@clerk/ui@8423

@clerk/upgrade

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

@clerk/vue

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

commit: 2df6b35

@coderabbitai

Copy link
Copy Markdown
Contributor
📝 Walkthrough

Walkthrough

This pull request removes the automatic proxy URL detection and derivation feature across the Clerk monorepo. The changes eliminate environment-based auto-proxy logic from multiple layers: the backend authentication context, the clerk-js core initialization, the nextjs middleware, utility functions, and the shared proxy utilities. Additionally, relative proxy URL path handling in script loading is removed, and Vercel-specific environment variables are removed from Turbo's global task dependencies. Corresponding test coverage for auto-proxy behavior is deleted across all affected packages.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check nameStatusExplanation
Title check✅ PassedThe title clearly summarizes the main change: this PR reverts PR #8035 to test its e2e impact on failing integration tests.
Description check✅ PassedThe description directly relates to the changeset by explaining the revert of auto-proxy functionality and its purpose for testing integration suite outcomes.
Docstring Coverage✅ PassedDocstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
Linked Issues check✅ PassedCheck skipped because no linked issues were found for this pull request.
Out of Scope Changes check✅ PassedCheck skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


Review rate limit: 4/5 reviews remaining, refill in 12 minutes.

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

@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.

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
packages/shared/src/loadClerkJsScript.ts (1)

283-293: ⚠️ Potential issue | 🟠 Major | ⚡ Quick win

Preserve relative proxy URL handling here.

proxyUrl still accepts relative values, but this branch now routes them through browser-only normalization and then concatenates the result directly. That breaks server-side clerkJSScriptUrl / clerkUIScriptUrl callers and can emit malformed .../proxy//npm/... URLs when the proxy path has a trailing slash.

Please restore the previous relative-proxy path or normalize the proxy path before building the script host.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@packages/shared/src/loadClerkJsScript.ts` around lines 283 - 293,
buildScriptHost currently converts proxyUrl via proxyUrlToAbsoluteURL then
strips the protocol, which breaks server-side callers and produces malformed
paths when proxyUrl is a relative path (especially with trailing slash). Update
the proxyUrl branch in buildScriptHost to detect relative proxy URLs and either
(a) return the original relative path (preserving behavior for server-side
callers) or (b) normalize the proxy path by removing a trailing slash before
concatenation; use the existing helpers (isValidProxyUrl, proxyUrlToAbsoluteURL)
but ensure relative URLs bypass proxyUrlToAbsoluteURL or are normalized (trim
trailing slash) so buildScriptHost returns a correct host string for both server
and browser usage. Reference: function buildScriptHost, helper
proxyUrlToAbsoluteURL, and isValidProxyUrl.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Outside diff comments:
In `@packages/shared/src/loadClerkJsScript.ts`:
- Around line 283-293: buildScriptHost currently converts proxyUrl via
proxyUrlToAbsoluteURL then strips the protocol, which breaks server-side callers
and produces malformed paths when proxyUrl is a relative path (especially with
trailing slash). Update the proxyUrl branch in buildScriptHost to detect
relative proxy URLs and either (a) return the original relative path (preserving
behavior for server-side callers) or (b) normalize the proxy path by removing a
trailing slash before concatenation; use the existing helpers (isValidProxyUrl,
proxyUrlToAbsoluteURL) but ensure relative URLs bypass proxyUrlToAbsoluteURL or
are normalized (trim trailing slash) so buildScriptHost returns a correct host
string for both server and browser usage. Reference: function buildScriptHost,
helper proxyUrlToAbsoluteURL, and isValidProxyUrl.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: 1560bd88-b204-41af-ad90-7a1bce2428e1

📥 Commits

Reviewing files that changed from the base of the PR and between 61e0a78 and 2df6b35.

📒 Files selected for processing (14)
  • packages/backend/src/tokens/__tests__/authenticateContext.test.ts
  • packages/backend/src/tokens/authenticateContext.ts
  • packages/clerk-js/src/core/__tests__/clerk.test.ts
  • packages/clerk-js/src/core/clerk.ts
  • packages/nextjs/src/app-router/server/__tests__/DynamicClerkScripts.test.tsx
  • packages/nextjs/src/server/__tests__/clerkMiddleware.test.ts
  • packages/nextjs/src/server/clerkMiddleware.ts
  • packages/nextjs/src/utils/__tests__/mergeNextClerkPropsWithEnv.test.ts
  • packages/nextjs/src/utils/mergeNextClerkPropsWithEnv.ts
  • packages/shared/src/__tests__/loadClerkJsScript.spec.ts
  • packages/shared/src/__tests__/proxy.spec.ts
  • packages/shared/src/loadClerkJsScript.ts
  • packages/shared/src/proxy.ts
  • turbo.json
💤 Files with no reviewable changes (8)
  • turbo.json
  • packages/nextjs/src/app-router/server/tests/DynamicClerkScripts.test.tsx
  • packages/backend/src/tokens/authenticateContext.ts
  • packages/nextjs/src/server/tests/clerkMiddleware.test.ts
  • packages/clerk-js/src/core/tests/clerk.test.ts
  • packages/backend/src/tokens/tests/authenticateContext.test.ts
  • packages/nextjs/src/utils/tests/mergeNextClerkPropsWithEnv.test.ts
  • packages/shared/src/tests/loadClerkJsScript.spec.ts

@jacekradko

Copy link
Copy Markdown
ContributorAuthor

Closing — the same 5 express tests (and same hono/billing/etc. patterns) fail identically on this branch as on main. reverting #8035 (auto-proxy) does not fix the userButton mount regression. Pattern is consistent across all four candidate branches we tested (#8422, #8423, #8424, #8426), so the cause is environmental, not in the JS source. Refocusing on infra: Clerk dashboard config on the test instances, FAPI deploys, Blacksmith runner image, or pnpm/Playwright resolution drift.

@jacekradko
jacekradko deleted the jacek/revert-pr-8035-experiment branch April 30, 2026 19:03
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.

1 participant

@jacekradko