feat(nextjs): point missing and invalid key errors at the Clerk CLI - #9492

Closed
djgould wants to merge 2 commits into
dg/keyless-cli/2-prod-errorfrom
dg/keyless-cli/3-invalid-keys
Closed

feat(nextjs): point missing and invalid key errors at the Clerk CLI#9492
djgould wants to merge 2 commits into
dg/keyless-cli/2-prod-errorfrom
dg/keyless-cli/3-invalid-keys

Conversation

@djgould

@djgoulddjgould commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

Description

Part 2 of the keyless→CLI stack (#9491#9492#9493#9487#9488), stacked on #9491. Written against main's middleware (keyless mode untouched — that lands in #9493):

  • clerkMiddleware() with missing keys throws missingEnvVars (code=missing_env_keys): npx clerk@latest init first, with npx clerk@latest deploy / npx clerk@latest env pull --instance prod guidance for production. The same message is thrown in every environment — the reader knows whether they are developing or deploying better than NODE_ENV does (e.g. next build && next start locally reports production).
  • clerkMiddleware() validates the publishable key format upfront, throwing invalidEnvKeys (code=invalid_env_keys). Previously fabricated or mistyped keys surfaced later as a bare Publishable key not valid. — sandbox agent trials showed invented placeholder keys are the most common agent failure mode.
  • Three existing dynamic-key test fixtures used placeholder-format keys and now use validly-formatted ones.

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

  • 🌟 New feature

🤖 Generated with Claude Code

@changeset-bot

changeset-botBot commented Aug 18, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 0cddd6d

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

This PR includes changesets to release 1 package
NameType
@clerk/nextjsPatch

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 Aug 18, 2026

Copy link
Copy Markdown

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

ProjectDeploymentActionsUpdated (UTC)
clerk-js-sandboxReadyReadyPreviewAug 18, 2026 8:13pm
swingsetReadyReadyPreviewAug 18, 2026 8:13pm

Request Review

@pkg-pr-new

pkg-pr-newBot commented Aug 18, 2026

Copy link
Copy Markdown

Open in StackBlitz

@clerk/astro

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

@clerk/backend

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

@clerk/chrome-extension

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

@clerk/clerk-js

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

@clerk/electron

npm i https://pkg.pr.new/@clerk/electron@9492

@clerk/electron-passkeys

npm i https://pkg.pr.new/@clerk/electron-passkeys@9492

@clerk/eslint-plugin

npm i https://pkg.pr.new/@clerk/eslint-plugin@9492

@clerk/expo

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

@clerk/expo-google-signin

npm i https://pkg.pr.new/@clerk/expo-google-signin@9492

@clerk/expo-passkeys

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

@clerk/express

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

@clerk/fastify

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

@clerk/hono

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

@clerk/localizations

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

@clerk/nextjs

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

@clerk/nuxt

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

@clerk/react

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

@clerk/react-router

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

@clerk/shared

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

@clerk/tanstack-react-start

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

@clerk/testing

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

@clerk/ui

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

@clerk/upgrade

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

@clerk/vue

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

commit: 0cddd6d

@djgould
djgouldforce-pushed the dg/keyless-cli/2-prod-error branch from 68162e8 to 13802d9CompareAugust 18, 2026 20:08
@djgould
djgouldforce-pushed the dg/keyless-cli/3-invalid-keys branch from 3093159 to 8a7793fCompareAugust 18, 2026 20:08
@djgoulddjgould changed the title feat(nextjs): point production and invalid-key errors at the Clerk CLIfeat(nextjs): point missing and invalid key errors at the Clerk CLIAug 18, 2026
@djgould

Copy link
Copy Markdown
ContributorAuthor

Collapsed into the rest of the stack: the invalid-key fix moved to the actual throw site — the fatal messages in parsePublishableKey (#9491, fixes every server SDK at once) — and the missing-key paths keep using the shared errorThrower messages, which now carry the CLI guidance. No nextjs-specific error constants needed. Stack is now #9491#9493#9487#9488.

@djgoulddjgould closed this Aug 18, 2026
@djgould
djgould deleted the dg/keyless-cli/3-invalid-keys branch August 18, 2026 20:41
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@djgould
, '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" + '
Skip to content

feat(nextjs): point missing and invalid key errors at the Clerk CLI - #9492

Closed
djgould wants to merge 2 commits into
dg/keyless-cli/2-prod-errorfrom
dg/keyless-cli/3-invalid-keys
Closed

feat(nextjs): point missing and invalid key errors at the Clerk CLI#9492
djgould wants to merge 2 commits into
dg/keyless-cli/2-prod-errorfrom
dg/keyless-cli/3-invalid-keys

Conversation

@djgould

@djgoulddjgould commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

Description

Part 2 of the keyless→CLI stack (#9491#9492#9493#9487#9488), stacked on #9491. Written against main's middleware (keyless mode untouched — that lands in #9493):

  • clerkMiddleware() with missing keys throws missingEnvVars (code=missing_env_keys): npx clerk@latest init first, with npx clerk@latest deploy / npx clerk@latest env pull --instance prod guidance for production. The same message is thrown in every environment — the reader knows whether they are developing or deploying better than NODE_ENV does (e.g. next build && next start locally reports production).
  • clerkMiddleware() validates the publishable key format upfront, throwing invalidEnvKeys (code=invalid_env_keys). Previously fabricated or mistyped keys surfaced later as a bare Publishable key not valid. — sandbox agent trials showed invented placeholder keys are the most common agent failure mode.
  • Three existing dynamic-key test fixtures used placeholder-format keys and now use validly-formatted ones.

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

  • 🌟 New feature

🤖 Generated with Claude Code

@changeset-bot

changeset-botBot commented Aug 18, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 0cddd6d

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

This PR includes changesets to release 1 package
NameType
@clerk/nextjsPatch

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 Aug 18, 2026

Copy link
Copy Markdown

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

ProjectDeploymentActionsUpdated (UTC)
clerk-js-sandboxReadyReadyPreviewAug 18, 2026 8:13pm
swingsetReadyReadyPreviewAug 18, 2026 8:13pm

Request Review

@pkg-pr-new

pkg-pr-newBot commented Aug 18, 2026

Copy link
Copy Markdown

Open in StackBlitz

@clerk/astro

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

@clerk/backend

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

@clerk/chrome-extension

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

@clerk/clerk-js

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

@clerk/electron

npm i https://pkg.pr.new/@clerk/electron@9492

@clerk/electron-passkeys

npm i https://pkg.pr.new/@clerk/electron-passkeys@9492

@clerk/eslint-plugin

npm i https://pkg.pr.new/@clerk/eslint-plugin@9492

@clerk/expo

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

@clerk/expo-google-signin

npm i https://pkg.pr.new/@clerk/expo-google-signin@9492

@clerk/expo-passkeys

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

@clerk/express

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

@clerk/fastify

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

@clerk/hono

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

@clerk/localizations

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

@clerk/nextjs

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

@clerk/nuxt

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

@clerk/react

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

@clerk/react-router

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

@clerk/shared

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

@clerk/tanstack-react-start

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

@clerk/testing

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

@clerk/ui

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

@clerk/upgrade

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

@clerk/vue

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

commit: 0cddd6d

@djgould
djgouldforce-pushed the dg/keyless-cli/2-prod-error branch from 68162e8 to 13802d9CompareAugust 18, 2026 20:08
@djgould
djgouldforce-pushed the dg/keyless-cli/3-invalid-keys branch from 3093159 to 8a7793fCompareAugust 18, 2026 20:08
@djgoulddjgould changed the title feat(nextjs): point production and invalid-key errors at the Clerk CLIfeat(nextjs): point missing and invalid key errors at the Clerk CLIAug 18, 2026
@djgould

Copy link
Copy Markdown
ContributorAuthor

Collapsed into the rest of the stack: the invalid-key fix moved to the actual throw site — the fatal messages in parsePublishableKey (#9491, fixes every server SDK at once) — and the missing-key paths keep using the shared errorThrower messages, which now carry the CLI guidance. No nextjs-specific error constants needed. Stack is now #9491#9493#9487#9488.

@djgoulddjgould closed this Aug 18, 2026
@djgould
djgould deleted the dg/keyless-cli/3-invalid-keys branch August 18, 2026 20:41
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@djgould
, '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('^' + ".*" + '
Skip to content

feat(nextjs): point missing and invalid key errors at the Clerk CLI - #9492

Closed
djgould wants to merge 2 commits into
dg/keyless-cli/2-prod-errorfrom
dg/keyless-cli/3-invalid-keys
Closed

feat(nextjs): point missing and invalid key errors at the Clerk CLI#9492
djgould wants to merge 2 commits into
dg/keyless-cli/2-prod-errorfrom
dg/keyless-cli/3-invalid-keys

Conversation

@djgould

@djgoulddjgould commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

Description

Part 2 of the keyless→CLI stack (#9491#9492#9493#9487#9488), stacked on #9491. Written against main's middleware (keyless mode untouched — that lands in #9493):

  • clerkMiddleware() with missing keys throws missingEnvVars (code=missing_env_keys): npx clerk@latest init first, with npx clerk@latest deploy / npx clerk@latest env pull --instance prod guidance for production. The same message is thrown in every environment — the reader knows whether they are developing or deploying better than NODE_ENV does (e.g. next build && next start locally reports production).
  • clerkMiddleware() validates the publishable key format upfront, throwing invalidEnvKeys (code=invalid_env_keys). Previously fabricated or mistyped keys surfaced later as a bare Publishable key not valid. — sandbox agent trials showed invented placeholder keys are the most common agent failure mode.
  • Three existing dynamic-key test fixtures used placeholder-format keys and now use validly-formatted ones.

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

  • 🌟 New feature

🤖 Generated with Claude Code

@changeset-bot

changeset-botBot commented Aug 18, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 0cddd6d

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

This PR includes changesets to release 1 package
NameType
@clerk/nextjsPatch

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 Aug 18, 2026

Copy link
Copy Markdown

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

ProjectDeploymentActionsUpdated (UTC)
clerk-js-sandboxReadyReadyPreviewAug 18, 2026 8:13pm
swingsetReadyReadyPreviewAug 18, 2026 8:13pm

Request Review

@pkg-pr-new

pkg-pr-newBot commented Aug 18, 2026

Copy link
Copy Markdown

Open in StackBlitz

@clerk/astro

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

@clerk/backend

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

@clerk/chrome-extension

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

@clerk/clerk-js

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

@clerk/electron

npm i https://pkg.pr.new/@clerk/electron@9492

@clerk/electron-passkeys

npm i https://pkg.pr.new/@clerk/electron-passkeys@9492

@clerk/eslint-plugin

npm i https://pkg.pr.new/@clerk/eslint-plugin@9492

@clerk/expo

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

@clerk/expo-google-signin

npm i https://pkg.pr.new/@clerk/expo-google-signin@9492

@clerk/expo-passkeys

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

@clerk/express

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

@clerk/fastify

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

@clerk/hono

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

@clerk/localizations

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

@clerk/nextjs

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

@clerk/nuxt

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

@clerk/react

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

@clerk/react-router

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

@clerk/shared

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

@clerk/tanstack-react-start

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

@clerk/testing

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

@clerk/ui

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

@clerk/upgrade

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

@clerk/vue

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

commit: 0cddd6d

@djgould
djgouldforce-pushed the dg/keyless-cli/2-prod-error branch from 68162e8 to 13802d9CompareAugust 18, 2026 20:08
@djgould
djgouldforce-pushed the dg/keyless-cli/3-invalid-keys branch from 3093159 to 8a7793fCompareAugust 18, 2026 20:08
@djgoulddjgould changed the title feat(nextjs): point production and invalid-key errors at the Clerk CLIfeat(nextjs): point missing and invalid key errors at the Clerk CLIAug 18, 2026
@djgould

Copy link
Copy Markdown
ContributorAuthor

Collapsed into the rest of the stack: the invalid-key fix moved to the actual throw site — the fatal messages in parsePublishableKey (#9491, fixes every server SDK at once) — and the missing-key paths keep using the shared errorThrower messages, which now carry the CLI guidance. No nextjs-specific error constants needed. Stack is now #9491#9493#9487#9488.

@djgoulddjgould closed this Aug 18, 2026
@djgould
djgould deleted the dg/keyless-cli/3-invalid-keys branch August 18, 2026 20:41
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@djgould
, '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('^' + ".*" + '
Skip to content

feat(nextjs): point missing and invalid key errors at the Clerk CLI - #9492

Closed
djgould wants to merge 2 commits into
dg/keyless-cli/2-prod-errorfrom
dg/keyless-cli/3-invalid-keys
Closed

feat(nextjs): point missing and invalid key errors at the Clerk CLI#9492
djgould wants to merge 2 commits into
dg/keyless-cli/2-prod-errorfrom
dg/keyless-cli/3-invalid-keys

Conversation

@djgould

@djgoulddjgould commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

Description

Part 2 of the keyless→CLI stack (#9491#9492#9493#9487#9488), stacked on #9491. Written against main's middleware (keyless mode untouched — that lands in #9493):

  • clerkMiddleware() with missing keys throws missingEnvVars (code=missing_env_keys): npx clerk@latest init first, with npx clerk@latest deploy / npx clerk@latest env pull --instance prod guidance for production. The same message is thrown in every environment — the reader knows whether they are developing or deploying better than NODE_ENV does (e.g. next build && next start locally reports production).
  • clerkMiddleware() validates the publishable key format upfront, throwing invalidEnvKeys (code=invalid_env_keys). Previously fabricated or mistyped keys surfaced later as a bare Publishable key not valid. — sandbox agent trials showed invented placeholder keys are the most common agent failure mode.
  • Three existing dynamic-key test fixtures used placeholder-format keys and now use validly-formatted ones.

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

  • 🌟 New feature

🤖 Generated with Claude Code

@changeset-bot

changeset-botBot commented Aug 18, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 0cddd6d

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

This PR includes changesets to release 1 package
NameType
@clerk/nextjsPatch

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 Aug 18, 2026

Copy link
Copy Markdown

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

ProjectDeploymentActionsUpdated (UTC)
clerk-js-sandboxReadyReadyPreviewAug 18, 2026 8:13pm
swingsetReadyReadyPreviewAug 18, 2026 8:13pm

Request Review

@pkg-pr-new

pkg-pr-newBot commented Aug 18, 2026

Copy link
Copy Markdown

Open in StackBlitz

@clerk/astro

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

@clerk/backend

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

@clerk/chrome-extension

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

@clerk/clerk-js

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

@clerk/electron

npm i https://pkg.pr.new/@clerk/electron@9492

@clerk/electron-passkeys

npm i https://pkg.pr.new/@clerk/electron-passkeys@9492

@clerk/eslint-plugin

npm i https://pkg.pr.new/@clerk/eslint-plugin@9492

@clerk/expo

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

@clerk/expo-google-signin

npm i https://pkg.pr.new/@clerk/expo-google-signin@9492

@clerk/expo-passkeys

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

@clerk/express

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

@clerk/fastify

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

@clerk/hono

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

@clerk/localizations

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

@clerk/nextjs

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

@clerk/nuxt

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

@clerk/react

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

@clerk/react-router

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

@clerk/shared

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

@clerk/tanstack-react-start

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

@clerk/testing

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

@clerk/ui

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

@clerk/upgrade

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

@clerk/vue

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

commit: 0cddd6d

@djgould
djgouldforce-pushed the dg/keyless-cli/2-prod-error branch from 68162e8 to 13802d9CompareAugust 18, 2026 20:08
@djgould
djgouldforce-pushed the dg/keyless-cli/3-invalid-keys branch from 3093159 to 8a7793fCompareAugust 18, 2026 20:08
@djgoulddjgould changed the title feat(nextjs): point production and invalid-key errors at the Clerk CLIfeat(nextjs): point missing and invalid key errors at the Clerk CLIAug 18, 2026
@djgould

Copy link
Copy Markdown
ContributorAuthor

Collapsed into the rest of the stack: the invalid-key fix moved to the actual throw site — the fatal messages in parsePublishableKey (#9491, fixes every server SDK at once) — and the missing-key paths keep using the shared errorThrower messages, which now carry the CLI guidance. No nextjs-specific error constants needed. Stack is now #9491#9493#9487#9488.

@djgoulddjgould closed this Aug 18, 2026
@djgould
djgould deleted the dg/keyless-cli/3-invalid-keys branch August 18, 2026 20:41
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@djgould
, '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" + '
Skip to content

feat(nextjs): point missing and invalid key errors at the Clerk CLI - #9492

Closed
djgould wants to merge 2 commits into
dg/keyless-cli/2-prod-errorfrom
dg/keyless-cli/3-invalid-keys
Closed

feat(nextjs): point missing and invalid key errors at the Clerk CLI#9492
djgould wants to merge 2 commits into
dg/keyless-cli/2-prod-errorfrom
dg/keyless-cli/3-invalid-keys

Conversation

@djgould

@djgoulddjgould commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

Description

Part 2 of the keyless→CLI stack (#9491#9492#9493#9487#9488), stacked on #9491. Written against main's middleware (keyless mode untouched — that lands in #9493):

  • clerkMiddleware() with missing keys throws missingEnvVars (code=missing_env_keys): npx clerk@latest init first, with npx clerk@latest deploy / npx clerk@latest env pull --instance prod guidance for production. The same message is thrown in every environment — the reader knows whether they are developing or deploying better than NODE_ENV does (e.g. next build && next start locally reports production).
  • clerkMiddleware() validates the publishable key format upfront, throwing invalidEnvKeys (code=invalid_env_keys). Previously fabricated or mistyped keys surfaced later as a bare Publishable key not valid. — sandbox agent trials showed invented placeholder keys are the most common agent failure mode.
  • Three existing dynamic-key test fixtures used placeholder-format keys and now use validly-formatted ones.

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

  • 🌟 New feature

🤖 Generated with Claude Code

@changeset-bot

changeset-botBot commented Aug 18, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 0cddd6d

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

This PR includes changesets to release 1 package
NameType
@clerk/nextjsPatch

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 Aug 18, 2026

Copy link
Copy Markdown

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

ProjectDeploymentActionsUpdated (UTC)
clerk-js-sandboxReadyReadyPreviewAug 18, 2026 8:13pm
swingsetReadyReadyPreviewAug 18, 2026 8:13pm

Request Review

@pkg-pr-new

pkg-pr-newBot commented Aug 18, 2026

Copy link
Copy Markdown

Open in StackBlitz

@clerk/astro

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

@clerk/backend

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

@clerk/chrome-extension

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

@clerk/clerk-js

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

@clerk/electron

npm i https://pkg.pr.new/@clerk/electron@9492

@clerk/electron-passkeys

npm i https://pkg.pr.new/@clerk/electron-passkeys@9492

@clerk/eslint-plugin

npm i https://pkg.pr.new/@clerk/eslint-plugin@9492

@clerk/expo

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

@clerk/expo-google-signin

npm i https://pkg.pr.new/@clerk/expo-google-signin@9492

@clerk/expo-passkeys

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

@clerk/express

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

@clerk/fastify

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

@clerk/hono

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

@clerk/localizations

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

@clerk/nextjs

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

@clerk/nuxt

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

@clerk/react

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

@clerk/react-router

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

@clerk/shared

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

@clerk/tanstack-react-start

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

@clerk/testing

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

@clerk/ui

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

@clerk/upgrade

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

@clerk/vue

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

commit: 0cddd6d

@djgould
djgouldforce-pushed the dg/keyless-cli/2-prod-error branch from 68162e8 to 13802d9CompareAugust 18, 2026 20:08
@djgould
djgouldforce-pushed the dg/keyless-cli/3-invalid-keys branch from 3093159 to 8a7793fCompareAugust 18, 2026 20:08
@djgoulddjgould changed the title feat(nextjs): point production and invalid-key errors at the Clerk CLIfeat(nextjs): point missing and invalid key errors at the Clerk CLIAug 18, 2026
@djgould

Copy link
Copy Markdown
ContributorAuthor

Collapsed into the rest of the stack: the invalid-key fix moved to the actual throw site — the fatal messages in parsePublishableKey (#9491, fixes every server SDK at once) — and the missing-key paths keep using the shared errorThrower messages, which now carry the CLI guidance. No nextjs-specific error constants needed. Stack is now #9491#9493#9487#9488.

@djgoulddjgould closed this Aug 18, 2026
@djgould
djgould deleted the dg/keyless-cli/3-invalid-keys branch August 18, 2026 20:41
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@djgould
, '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('^' + ".*" + '
Skip to content

feat(nextjs): point missing and invalid key errors at the Clerk CLI - #9492

Closed
djgould wants to merge 2 commits into
dg/keyless-cli/2-prod-errorfrom
dg/keyless-cli/3-invalid-keys
Closed

feat(nextjs): point missing and invalid key errors at the Clerk CLI#9492
djgould wants to merge 2 commits into
dg/keyless-cli/2-prod-errorfrom
dg/keyless-cli/3-invalid-keys

Conversation

@djgould

@djgoulddjgould commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

Description

Part 2 of the keyless→CLI stack (#9491#9492#9493#9487#9488), stacked on #9491. Written against main's middleware (keyless mode untouched — that lands in #9493):

  • clerkMiddleware() with missing keys throws missingEnvVars (code=missing_env_keys): npx clerk@latest init first, with npx clerk@latest deploy / npx clerk@latest env pull --instance prod guidance for production. The same message is thrown in every environment — the reader knows whether they are developing or deploying better than NODE_ENV does (e.g. next build && next start locally reports production).
  • clerkMiddleware() validates the publishable key format upfront, throwing invalidEnvKeys (code=invalid_env_keys). Previously fabricated or mistyped keys surfaced later as a bare Publishable key not valid. — sandbox agent trials showed invented placeholder keys are the most common agent failure mode.
  • Three existing dynamic-key test fixtures used placeholder-format keys and now use validly-formatted ones.

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

  • 🌟 New feature

🤖 Generated with Claude Code

@changeset-bot

changeset-botBot commented Aug 18, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 0cddd6d

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

This PR includes changesets to release 1 package
NameType
@clerk/nextjsPatch

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 Aug 18, 2026

Copy link
Copy Markdown

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

ProjectDeploymentActionsUpdated (UTC)
clerk-js-sandboxReadyReadyPreviewAug 18, 2026 8:13pm
swingsetReadyReadyPreviewAug 18, 2026 8:13pm

Request Review

@pkg-pr-new

pkg-pr-newBot commented Aug 18, 2026

Copy link
Copy Markdown

Open in StackBlitz

@clerk/astro

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

@clerk/backend

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

@clerk/chrome-extension

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

@clerk/clerk-js

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

@clerk/electron

npm i https://pkg.pr.new/@clerk/electron@9492

@clerk/electron-passkeys

npm i https://pkg.pr.new/@clerk/electron-passkeys@9492

@clerk/eslint-plugin

npm i https://pkg.pr.new/@clerk/eslint-plugin@9492

@clerk/expo

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

@clerk/expo-google-signin

npm i https://pkg.pr.new/@clerk/expo-google-signin@9492

@clerk/expo-passkeys

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

@clerk/express

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

@clerk/fastify

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

@clerk/hono

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

@clerk/localizations

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

@clerk/nextjs

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

@clerk/nuxt

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

@clerk/react

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

@clerk/react-router

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

@clerk/shared

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

@clerk/tanstack-react-start

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

@clerk/testing

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

@clerk/ui

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

@clerk/upgrade

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

@clerk/vue

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

commit: 0cddd6d

@djgould
djgouldforce-pushed the dg/keyless-cli/2-prod-error branch from 68162e8 to 13802d9CompareAugust 18, 2026 20:08
@djgould
djgouldforce-pushed the dg/keyless-cli/3-invalid-keys branch from 3093159 to 8a7793fCompareAugust 18, 2026 20:08
@djgoulddjgould changed the title feat(nextjs): point production and invalid-key errors at the Clerk CLIfeat(nextjs): point missing and invalid key errors at the Clerk CLIAug 18, 2026
@djgould

Copy link
Copy Markdown
ContributorAuthor

Collapsed into the rest of the stack: the invalid-key fix moved to the actual throw site — the fatal messages in parsePublishableKey (#9491, fixes every server SDK at once) — and the missing-key paths keep using the shared errorThrower messages, which now carry the CLI guidance. No nextjs-specific error constants needed. Stack is now #9491#9493#9487#9488.

@djgoulddjgould closed this Aug 18, 2026
@djgould
djgould deleted the dg/keyless-cli/3-invalid-keys branch August 18, 2026 20:41
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@djgould
, '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('^' + ".*" + '
Skip to content

feat(nextjs): point missing and invalid key errors at the Clerk CLI - #9492

Closed
djgould wants to merge 2 commits into
dg/keyless-cli/2-prod-errorfrom
dg/keyless-cli/3-invalid-keys
Closed

feat(nextjs): point missing and invalid key errors at the Clerk CLI#9492
djgould wants to merge 2 commits into
dg/keyless-cli/2-prod-errorfrom
dg/keyless-cli/3-invalid-keys

Conversation

@djgould

@djgoulddjgould commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

Description

Part 2 of the keyless→CLI stack (#9491#9492#9493#9487#9488), stacked on #9491. Written against main's middleware (keyless mode untouched — that lands in #9493):

  • clerkMiddleware() with missing keys throws missingEnvVars (code=missing_env_keys): npx clerk@latest init first, with npx clerk@latest deploy / npx clerk@latest env pull --instance prod guidance for production. The same message is thrown in every environment — the reader knows whether they are developing or deploying better than NODE_ENV does (e.g. next build && next start locally reports production).
  • clerkMiddleware() validates the publishable key format upfront, throwing invalidEnvKeys (code=invalid_env_keys). Previously fabricated or mistyped keys surfaced later as a bare Publishable key not valid. — sandbox agent trials showed invented placeholder keys are the most common agent failure mode.
  • Three existing dynamic-key test fixtures used placeholder-format keys and now use validly-formatted ones.

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

  • 🌟 New feature

🤖 Generated with Claude Code

@changeset-bot

changeset-botBot commented Aug 18, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 0cddd6d

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

This PR includes changesets to release 1 package
NameType
@clerk/nextjsPatch

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 Aug 18, 2026

Copy link
Copy Markdown

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

ProjectDeploymentActionsUpdated (UTC)
clerk-js-sandboxReadyReadyPreviewAug 18, 2026 8:13pm
swingsetReadyReadyPreviewAug 18, 2026 8:13pm

Request Review

@pkg-pr-new

pkg-pr-newBot commented Aug 18, 2026

Copy link
Copy Markdown

Open in StackBlitz

@clerk/astro

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

@clerk/backend

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

@clerk/chrome-extension

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

@clerk/clerk-js

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

@clerk/electron

npm i https://pkg.pr.new/@clerk/electron@9492

@clerk/electron-passkeys

npm i https://pkg.pr.new/@clerk/electron-passkeys@9492

@clerk/eslint-plugin

npm i https://pkg.pr.new/@clerk/eslint-plugin@9492

@clerk/expo

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

@clerk/expo-google-signin

npm i https://pkg.pr.new/@clerk/expo-google-signin@9492

@clerk/expo-passkeys

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

@clerk/express

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

@clerk/fastify

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

@clerk/hono

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

@clerk/localizations

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

@clerk/nextjs

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

@clerk/nuxt

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

@clerk/react

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

@clerk/react-router

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

@clerk/shared

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

@clerk/tanstack-react-start

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

@clerk/testing

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

@clerk/ui

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

@clerk/upgrade

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

@clerk/vue

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

commit: 0cddd6d

@djgould
djgouldforce-pushed the dg/keyless-cli/2-prod-error branch from 68162e8 to 13802d9CompareAugust 18, 2026 20:08
@djgould
djgouldforce-pushed the dg/keyless-cli/3-invalid-keys branch from 3093159 to 8a7793fCompareAugust 18, 2026 20:08
@djgoulddjgould changed the title feat(nextjs): point production and invalid-key errors at the Clerk CLIfeat(nextjs): point missing and invalid key errors at the Clerk CLIAug 18, 2026
@djgould

Copy link
Copy Markdown
ContributorAuthor

Collapsed into the rest of the stack: the invalid-key fix moved to the actual throw site — the fatal messages in parsePublishableKey (#9491, fixes every server SDK at once) — and the missing-key paths keep using the shared errorThrower messages, which now carry the CLI guidance. No nextjs-specific error constants needed. Stack is now #9491#9493#9487#9488.

@djgoulddjgould closed this Aug 18, 2026
@djgould
djgould deleted the dg/keyless-cli/3-invalid-keys branch August 18, 2026 20:41
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@djgould
, '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); } })(); })();
Skip to content

feat(nextjs): point missing and invalid key errors at the Clerk CLI - #9492

Closed
djgould wants to merge 2 commits into
dg/keyless-cli/2-prod-errorfrom
dg/keyless-cli/3-invalid-keys
Closed

feat(nextjs): point missing and invalid key errors at the Clerk CLI#9492
djgould wants to merge 2 commits into
dg/keyless-cli/2-prod-errorfrom
dg/keyless-cli/3-invalid-keys

Conversation

@djgould

@djgoulddjgould commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

Description

Part 2 of the keyless→CLI stack (#9491#9492#9493#9487#9488), stacked on #9491. Written against main's middleware (keyless mode untouched — that lands in #9493):

  • clerkMiddleware() with missing keys throws missingEnvVars (code=missing_env_keys): npx clerk@latest init first, with npx clerk@latest deploy / npx clerk@latest env pull --instance prod guidance for production. The same message is thrown in every environment — the reader knows whether they are developing or deploying better than NODE_ENV does (e.g. next build && next start locally reports production).
  • clerkMiddleware() validates the publishable key format upfront, throwing invalidEnvKeys (code=invalid_env_keys). Previously fabricated or mistyped keys surfaced later as a bare Publishable key not valid. — sandbox agent trials showed invented placeholder keys are the most common agent failure mode.
  • Three existing dynamic-key test fixtures used placeholder-format keys and now use validly-formatted ones.

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

  • 🌟 New feature

🤖 Generated with Claude Code

@changeset-bot

changeset-botBot commented Aug 18, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 0cddd6d

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

This PR includes changesets to release 1 package
NameType
@clerk/nextjsPatch

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 Aug 18, 2026

Copy link
Copy Markdown

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

ProjectDeploymentActionsUpdated (UTC)
clerk-js-sandboxReadyReadyPreviewAug 18, 2026 8:13pm
swingsetReadyReadyPreviewAug 18, 2026 8:13pm

Request Review

@pkg-pr-new

pkg-pr-newBot commented Aug 18, 2026

Copy link
Copy Markdown

Open in StackBlitz

@clerk/astro

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

@clerk/backend

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

@clerk/chrome-extension

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

@clerk/clerk-js

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

@clerk/electron

npm i https://pkg.pr.new/@clerk/electron@9492

@clerk/electron-passkeys

npm i https://pkg.pr.new/@clerk/electron-passkeys@9492

@clerk/eslint-plugin

npm i https://pkg.pr.new/@clerk/eslint-plugin@9492

@clerk/expo

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

@clerk/expo-google-signin

npm i https://pkg.pr.new/@clerk/expo-google-signin@9492

@clerk/expo-passkeys

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

@clerk/express

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

@clerk/fastify

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

@clerk/hono

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

@clerk/localizations

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

@clerk/nextjs

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

@clerk/nuxt

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

@clerk/react

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

@clerk/react-router

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

@clerk/shared

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

@clerk/tanstack-react-start

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

@clerk/testing

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

@clerk/ui

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

@clerk/upgrade

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

@clerk/vue

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

commit: 0cddd6d

@djgould
djgouldforce-pushed the dg/keyless-cli/2-prod-error branch from 68162e8 to 13802d9CompareAugust 18, 2026 20:08
@djgould
djgouldforce-pushed the dg/keyless-cli/3-invalid-keys branch from 3093159 to 8a7793fCompareAugust 18, 2026 20:08
@djgoulddjgould changed the title feat(nextjs): point production and invalid-key errors at the Clerk CLIfeat(nextjs): point missing and invalid key errors at the Clerk CLIAug 18, 2026
@djgould

Copy link
Copy Markdown
ContributorAuthor

Collapsed into the rest of the stack: the invalid-key fix moved to the actual throw site — the fatal messages in parsePublishableKey (#9491, fixes every server SDK at once) — and the missing-key paths keep using the shared errorThrower messages, which now carry the CLI guidance. No nextjs-specific error constants needed. Stack is now #9491#9493#9487#9488.

@djgoulddjgould closed this Aug 18, 2026
@djgould
djgould deleted the dg/keyless-cli/3-invalid-keys branch August 18, 2026 20:41
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@djgould