Skip to content

fix(astro): Fall back to process.env for runtime environment variables - #7889

Merged
jacekradko merged 5 commits into
mainfrom
ac/astro-process-env-fallback
Feb 23, 2026
Merged

fix(astro): Fall back to process.env for runtime environment variables#7889
jacekradko merged 5 commits into
mainfrom
ac/astro-process-env-fallback

Conversation

@alexcarpenter

@alexcarpenteralexcarpenter commented Feb 19, 2026

Copy link
Copy Markdown
Member

Add process.env as a third fallback in getContextEnvVar() so that PUBLIC_CLERK_PUBLISHABLE_KEY and other env vars set at runtime (e.g., via the Astro Node adapter) are properly read when import.meta.env.PUBLIC_* is statically replaced at build time by Vite.

Description

fixes#7841

Checklist

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

Type of change

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

Summary by CodeRabbit

  • Bug Fixes

    • Fixes runtime reading of the publishable key when build-time env replacements aren’t available by adding a fallback to process.env.
  • Tests

    • Adds comprehensive tests for environment variable precedence and fallback behavior across different runtime environments.

Add process.env as a third fallback in getContextEnvVar() so that
PUBLIC_CLERK_PUBLISHABLE_KEY and other env vars set at runtime
(e.g., via the Astro Node adapter) are properly read when
import.meta.env.PUBLIC_* is statically replaced at build time by Vite.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@vercel

vercelBot commented Feb 19, 2026

Copy link
Copy Markdown

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

ProjectDeploymentActionsUpdated (UTC)
clerk-js-sandboxReadyReadyPreview, CommentFeb 23, 2026 5:06pm

Request Review

@changeset-bot

changeset-botBot commented Feb 19, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 6e04eba

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

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

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

@coderabbitai

coderabbitaiBot commented Feb 19, 2026

Copy link
Copy Markdown
Contributor
📝 Walkthrough

Walkthrough

The PR adds a runtime fallback in the Astro integration's getContextEnvVar(): it reads import.meta.env first and, if that value is missing, falls back to process.env; returns undefined if neither is present. Tests for getSafeEnv and getClientSafeEnv were added to verify source precedence, keylessPublishableKey precedence, and fallback behavior for publishable and public env vars across runtime contexts.

Possibly related issues

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check nameStatusExplanationResolution
Docstring Coverage⚠️ WarningDocstring coverage is 50.00% which is insufficient. The required threshold is 80.00%.Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (2 passed)
Check nameStatusExplanation
Title check✅ PassedThe title accurately describes the main change: adding a process.env fallback mechanism for runtime environment variables in the Astro module, which is the primary objective of the PR.
Description Check✅ PassedCheck skipped - CodeRabbit’s high-level summary is enabled.

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


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

alexcarpenterand others added 2 commits February 19, 2026 15:07
Add process.env as a third fallback in getContextEnvVar() so that
PUBLIC_CLERK_PUBLISHABLE_KEY and other env vars set at runtime
(e.g., via the Astro Node adapter) are properly read when
import.meta.env.PUBLIC_* is statically replaced at build time by Vite.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…script into ac/astro-process-env-fallback
# Conflicts:
#	packages/astro/src/server/__tests__/get-safe-env.test.ts

@wobsorianowobsoriano left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

thanks!

Use `as unknown as App.Locals` cast in createLocals to avoid strict
assignability errors from Partial<App.Locals> spreading.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@pkg-pr-new

pkg-pr-newBot commented Feb 19, 2026

Copy link
Copy Markdown

Open in StackBlitz

@clerk/agent-toolkit

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

@clerk/astro

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

@clerk/backend

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

@clerk/chrome-extension

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

@clerk/clerk-js

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

@clerk/dev-cli

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

@clerk/expo

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

@clerk/expo-passkeys

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

@clerk/express

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

@clerk/fastify

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

@clerk/hono

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

@clerk/localizations

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

@clerk/nextjs

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

@clerk/nuxt

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

@clerk/react

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

@clerk/react-router

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

@clerk/shared

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

@clerk/tanstack-react-start

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

@clerk/testing

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

@clerk/ui

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

@clerk/upgrade

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

@clerk/vue

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

commit: 6e04eba

return envValue;
}

// Fallback to process.env for runtime environments (e.g., Node.js adapter)

@asdfjkalsdflaasdfjkalsdflaFeb 21, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

What do you think of having process.env have a higher precedence than import.meta.env?

My gut is that if someone defines this in their running environment that is what they intend vs. what they had it set to when they built an app. It would also make the runtime variables have higher priority like when deployed in Cloudflare Workers.

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.

Thanks @asdfjkalsdfla . I agree that preferring runtime over build-time values is the correct approach. Updated the PR to switch the priority and marking the change as breaking.

@asdfjkalsdflaasdfjkalsdfla left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

General comments.

…olution
Runtime environment variables now take precedence over build-time
values statically replaced by Vite. This aligns behavior so that
env vars set at runtime (e.g., Node.js adapter) override those
baked in at build time.
Resolution order: locals.runtime.env > process.env > import.meta.env
@jacekradko
jacekradko merged commit ac4364d into mainFeb 23, 2026
37 of 38 checks passed
@jacekradko
jacekradko deleted the ac/astro-process-env-fallback branch February 23, 2026 19:29
Chat-JPTeasdale pushed a commit to Chat-JPTeasdale/javascript that referenced this pull request Mar 28, 2026
Add initCloudflareWorkersEnv() and cloudflare:workers module env check
to the shared getEnvVariable() function. This allows Clerk to read
environment variables directly from the Cloudflare Workers runtime,
following the same pattern used in @clerk/astro (PRs clerk#7889, clerk#8136).
Needed for TanStack Start, Hono, and other frameworks on CF Workers
where process.env and import.meta.env are not available at runtime.
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.

Astro: PUBLIC_CLERK_PUBLISHABLE_KEY cannot be changed after build

4 participants

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

fix(astro): Fall back to process.env for runtime environment variables - #7889

Merged
jacekradko merged 5 commits into
mainfrom
ac/astro-process-env-fallback
Feb 23, 2026
Merged

fix(astro): Fall back to process.env for runtime environment variables#7889
jacekradko merged 5 commits into
mainfrom
ac/astro-process-env-fallback

Conversation

@alexcarpenter

@alexcarpenteralexcarpenter commented Feb 19, 2026

Copy link
Copy Markdown
Member

Add process.env as a third fallback in getContextEnvVar() so that PUBLIC_CLERK_PUBLISHABLE_KEY and other env vars set at runtime (e.g., via the Astro Node adapter) are properly read when import.meta.env.PUBLIC_* is statically replaced at build time by Vite.

Description

fixes#7841

Checklist

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

Type of change

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

Summary by CodeRabbit

  • Bug Fixes

    • Fixes runtime reading of the publishable key when build-time env replacements aren’t available by adding a fallback to process.env.
  • Tests

    • Adds comprehensive tests for environment variable precedence and fallback behavior across different runtime environments.

Add process.env as a third fallback in getContextEnvVar() so that
PUBLIC_CLERK_PUBLISHABLE_KEY and other env vars set at runtime
(e.g., via the Astro Node adapter) are properly read when
import.meta.env.PUBLIC_* is statically replaced at build time by Vite.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@vercel

vercelBot commented Feb 19, 2026

Copy link
Copy Markdown

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

ProjectDeploymentActionsUpdated (UTC)
clerk-js-sandboxReadyReadyPreview, CommentFeb 23, 2026 5:06pm

Request Review

@changeset-bot

changeset-botBot commented Feb 19, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 6e04eba

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

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

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

@coderabbitai

coderabbitaiBot commented Feb 19, 2026

Copy link
Copy Markdown
Contributor
📝 Walkthrough

Walkthrough

The PR adds a runtime fallback in the Astro integration's getContextEnvVar(): it reads import.meta.env first and, if that value is missing, falls back to process.env; returns undefined if neither is present. Tests for getSafeEnv and getClientSafeEnv were added to verify source precedence, keylessPublishableKey precedence, and fallback behavior for publishable and public env vars across runtime contexts.

Possibly related issues

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check nameStatusExplanationResolution
Docstring Coverage⚠️ WarningDocstring coverage is 50.00% which is insufficient. The required threshold is 80.00%.Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (2 passed)
Check nameStatusExplanation
Title check✅ PassedThe title accurately describes the main change: adding a process.env fallback mechanism for runtime environment variables in the Astro module, which is the primary objective of the PR.
Description Check✅ PassedCheck skipped - CodeRabbit’s high-level summary is enabled.

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


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

alexcarpenterand others added 2 commits February 19, 2026 15:07
Add process.env as a third fallback in getContextEnvVar() so that
PUBLIC_CLERK_PUBLISHABLE_KEY and other env vars set at runtime
(e.g., via the Astro Node adapter) are properly read when
import.meta.env.PUBLIC_* is statically replaced at build time by Vite.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…script into ac/astro-process-env-fallback
# Conflicts:
#	packages/astro/src/server/__tests__/get-safe-env.test.ts

@wobsorianowobsoriano left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

thanks!

Use `as unknown as App.Locals` cast in createLocals to avoid strict
assignability errors from Partial<App.Locals> spreading.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@pkg-pr-new

pkg-pr-newBot commented Feb 19, 2026

Copy link
Copy Markdown

Open in StackBlitz

@clerk/agent-toolkit

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

@clerk/astro

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

@clerk/backend

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

@clerk/chrome-extension

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

@clerk/clerk-js

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

@clerk/dev-cli

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

@clerk/expo

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

@clerk/expo-passkeys

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

@clerk/express

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

@clerk/fastify

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

@clerk/hono

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

@clerk/localizations

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

@clerk/nextjs

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

@clerk/nuxt

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

@clerk/react

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

@clerk/react-router

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

@clerk/shared

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

@clerk/tanstack-react-start

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

@clerk/testing

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

@clerk/ui

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

@clerk/upgrade

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

@clerk/vue

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

commit: 6e04eba

return envValue;
}

// Fallback to process.env for runtime environments (e.g., Node.js adapter)

@asdfjkalsdflaasdfjkalsdflaFeb 21, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

What do you think of having process.env have a higher precedence than import.meta.env?

My gut is that if someone defines this in their running environment that is what they intend vs. what they had it set to when they built an app. It would also make the runtime variables have higher priority like when deployed in Cloudflare Workers.

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.

Thanks @asdfjkalsdfla . I agree that preferring runtime over build-time values is the correct approach. Updated the PR to switch the priority and marking the change as breaking.

@asdfjkalsdflaasdfjkalsdfla left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

General comments.

…olution
Runtime environment variables now take precedence over build-time
values statically replaced by Vite. This aligns behavior so that
env vars set at runtime (e.g., Node.js adapter) override those
baked in at build time.
Resolution order: locals.runtime.env > process.env > import.meta.env
@jacekradko
jacekradko merged commit ac4364d into mainFeb 23, 2026
37 of 38 checks passed
@jacekradko
jacekradko deleted the ac/astro-process-env-fallback branch February 23, 2026 19:29
Chat-JPTeasdale pushed a commit to Chat-JPTeasdale/javascript that referenced this pull request Mar 28, 2026
Add initCloudflareWorkersEnv() and cloudflare:workers module env check
to the shared getEnvVariable() function. This allows Clerk to read
environment variables directly from the Cloudflare Workers runtime,
following the same pattern used in @clerk/astro (PRs clerk#7889, clerk#8136).
Needed for TanStack Start, Hono, and other frameworks on CF Workers
where process.env and import.meta.env are not available at runtime.
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.

Astro: PUBLIC_CLERK_PUBLISHABLE_KEY cannot be changed after build

4 participants

@alexcarpenter@jacekradko@wobsoriano@asdfjkalsdfla
, 'i'); if (__m === '*' || __re.test(location.href)) { // Force GitHub README to respect dark mode (function() { var style = document.createElement('style'); style.textContent = ' .markdown-body { color-scheme: dark light; } .markdown-body pre { background: #161b22 !important; } .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; } .markdown-body table th, .markdown-body table td { border-color: #30363d !important; } .markdown-body img { background: #0d1117; } .markdown-body blockquote { border-left-color: #8b949e; } .markdown-body hr { border-color: #30363d; } '; document.head.appendChild(style); })(); } } catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' fix(astro): Fall back to process.env for runtime environment variables by alexcarpenter · Pull Request #7889 · clerk/javascript · GitHub
Skip to content

fix(astro): Fall back to process.env for runtime environment variables - #7889

Merged
jacekradko merged 5 commits into
mainfrom
ac/astro-process-env-fallback
Feb 23, 2026
Merged

fix(astro): Fall back to process.env for runtime environment variables#7889
jacekradko merged 5 commits into
mainfrom
ac/astro-process-env-fallback

Conversation

@alexcarpenter

@alexcarpenteralexcarpenter commented Feb 19, 2026

Copy link
Copy Markdown
Member

Add process.env as a third fallback in getContextEnvVar() so that PUBLIC_CLERK_PUBLISHABLE_KEY and other env vars set at runtime (e.g., via the Astro Node adapter) are properly read when import.meta.env.PUBLIC_* is statically replaced at build time by Vite.

Description

fixes#7841

Checklist

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

Type of change

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

Summary by CodeRabbit

  • Bug Fixes

    • Fixes runtime reading of the publishable key when build-time env replacements aren’t available by adding a fallback to process.env.
  • Tests

    • Adds comprehensive tests for environment variable precedence and fallback behavior across different runtime environments.

Add process.env as a third fallback in getContextEnvVar() so that
PUBLIC_CLERK_PUBLISHABLE_KEY and other env vars set at runtime
(e.g., via the Astro Node adapter) are properly read when
import.meta.env.PUBLIC_* is statically replaced at build time by Vite.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@vercel

vercelBot commented Feb 19, 2026

Copy link
Copy Markdown

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

ProjectDeploymentActionsUpdated (UTC)
clerk-js-sandboxReadyReadyPreview, CommentFeb 23, 2026 5:06pm

Request Review

@changeset-bot

changeset-botBot commented Feb 19, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 6e04eba

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

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

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

@coderabbitai

coderabbitaiBot commented Feb 19, 2026

Copy link
Copy Markdown
Contributor
📝 Walkthrough

Walkthrough

The PR adds a runtime fallback in the Astro integration's getContextEnvVar(): it reads import.meta.env first and, if that value is missing, falls back to process.env; returns undefined if neither is present. Tests for getSafeEnv and getClientSafeEnv were added to verify source precedence, keylessPublishableKey precedence, and fallback behavior for publishable and public env vars across runtime contexts.

Possibly related issues

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check nameStatusExplanationResolution
Docstring Coverage⚠️ WarningDocstring coverage is 50.00% which is insufficient. The required threshold is 80.00%.Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (2 passed)
Check nameStatusExplanation
Title check✅ PassedThe title accurately describes the main change: adding a process.env fallback mechanism for runtime environment variables in the Astro module, which is the primary objective of the PR.
Description Check✅ PassedCheck skipped - CodeRabbit’s high-level summary is enabled.

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


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

alexcarpenterand others added 2 commits February 19, 2026 15:07
Add process.env as a third fallback in getContextEnvVar() so that
PUBLIC_CLERK_PUBLISHABLE_KEY and other env vars set at runtime
(e.g., via the Astro Node adapter) are properly read when
import.meta.env.PUBLIC_* is statically replaced at build time by Vite.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…script into ac/astro-process-env-fallback
# Conflicts:
#	packages/astro/src/server/__tests__/get-safe-env.test.ts

@wobsorianowobsoriano left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

thanks!

Use `as unknown as App.Locals` cast in createLocals to avoid strict
assignability errors from Partial<App.Locals> spreading.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@pkg-pr-new

pkg-pr-newBot commented Feb 19, 2026

Copy link
Copy Markdown

Open in StackBlitz

@clerk/agent-toolkit

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

@clerk/astro

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

@clerk/backend

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

@clerk/chrome-extension

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

@clerk/clerk-js

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

@clerk/dev-cli

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

@clerk/expo

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

@clerk/expo-passkeys

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

@clerk/express

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

@clerk/fastify

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

@clerk/hono

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

@clerk/localizations

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

@clerk/nextjs

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

@clerk/nuxt

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

@clerk/react

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

@clerk/react-router

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

@clerk/shared

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

@clerk/tanstack-react-start

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

@clerk/testing

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

@clerk/ui

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

@clerk/upgrade

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

@clerk/vue

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

commit: 6e04eba

return envValue;
}

// Fallback to process.env for runtime environments (e.g., Node.js adapter)

@asdfjkalsdflaasdfjkalsdflaFeb 21, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

What do you think of having process.env have a higher precedence than import.meta.env?

My gut is that if someone defines this in their running environment that is what they intend vs. what they had it set to when they built an app. It would also make the runtime variables have higher priority like when deployed in Cloudflare Workers.

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.

Thanks @asdfjkalsdfla . I agree that preferring runtime over build-time values is the correct approach. Updated the PR to switch the priority and marking the change as breaking.

@asdfjkalsdflaasdfjkalsdfla left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

General comments.

…olution
Runtime environment variables now take precedence over build-time
values statically replaced by Vite. This aligns behavior so that
env vars set at runtime (e.g., Node.js adapter) override those
baked in at build time.
Resolution order: locals.runtime.env > process.env > import.meta.env
@jacekradko
jacekradko merged commit ac4364d into mainFeb 23, 2026
37 of 38 checks passed
@jacekradko
jacekradko deleted the ac/astro-process-env-fallback branch February 23, 2026 19:29
Chat-JPTeasdale pushed a commit to Chat-JPTeasdale/javascript that referenced this pull request Mar 28, 2026
Add initCloudflareWorkersEnv() and cloudflare:workers module env check
to the shared getEnvVariable() function. This allows Clerk to read
environment variables directly from the Cloudflare Workers runtime,
following the same pattern used in @clerk/astro (PRs clerk#7889, clerk#8136).
Needed for TanStack Start, Hono, and other frameworks on CF Workers
where process.env and import.meta.env are not available at runtime.
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.

Astro: PUBLIC_CLERK_PUBLISHABLE_KEY cannot be changed after build

4 participants

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

fix(astro): Fall back to process.env for runtime environment variables - #7889

Merged
jacekradko merged 5 commits into
mainfrom
ac/astro-process-env-fallback
Feb 23, 2026
Merged

fix(astro): Fall back to process.env for runtime environment variables#7889
jacekradko merged 5 commits into
mainfrom
ac/astro-process-env-fallback

Conversation

@alexcarpenter

@alexcarpenteralexcarpenter commented Feb 19, 2026

Copy link
Copy Markdown
Member

Add process.env as a third fallback in getContextEnvVar() so that PUBLIC_CLERK_PUBLISHABLE_KEY and other env vars set at runtime (e.g., via the Astro Node adapter) are properly read when import.meta.env.PUBLIC_* is statically replaced at build time by Vite.

Description

fixes#7841

Checklist

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

Type of change

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

Summary by CodeRabbit

  • Bug Fixes

    • Fixes runtime reading of the publishable key when build-time env replacements aren’t available by adding a fallback to process.env.
  • Tests

    • Adds comprehensive tests for environment variable precedence and fallback behavior across different runtime environments.

Add process.env as a third fallback in getContextEnvVar() so that
PUBLIC_CLERK_PUBLISHABLE_KEY and other env vars set at runtime
(e.g., via the Astro Node adapter) are properly read when
import.meta.env.PUBLIC_* is statically replaced at build time by Vite.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@vercel

vercelBot commented Feb 19, 2026

Copy link
Copy Markdown

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

ProjectDeploymentActionsUpdated (UTC)
clerk-js-sandboxReadyReadyPreview, CommentFeb 23, 2026 5:06pm

Request Review

@changeset-bot

changeset-botBot commented Feb 19, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 6e04eba

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

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

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

@coderabbitai

coderabbitaiBot commented Feb 19, 2026

Copy link
Copy Markdown
Contributor
📝 Walkthrough

Walkthrough

The PR adds a runtime fallback in the Astro integration's getContextEnvVar(): it reads import.meta.env first and, if that value is missing, falls back to process.env; returns undefined if neither is present. Tests for getSafeEnv and getClientSafeEnv were added to verify source precedence, keylessPublishableKey precedence, and fallback behavior for publishable and public env vars across runtime contexts.

Possibly related issues

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check nameStatusExplanationResolution
Docstring Coverage⚠️ WarningDocstring coverage is 50.00% which is insufficient. The required threshold is 80.00%.Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (2 passed)
Check nameStatusExplanation
Title check✅ PassedThe title accurately describes the main change: adding a process.env fallback mechanism for runtime environment variables in the Astro module, which is the primary objective of the PR.
Description Check✅ PassedCheck skipped - CodeRabbit’s high-level summary is enabled.

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


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

alexcarpenterand others added 2 commits February 19, 2026 15:07
Add process.env as a third fallback in getContextEnvVar() so that
PUBLIC_CLERK_PUBLISHABLE_KEY and other env vars set at runtime
(e.g., via the Astro Node adapter) are properly read when
import.meta.env.PUBLIC_* is statically replaced at build time by Vite.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…script into ac/astro-process-env-fallback
# Conflicts:
#	packages/astro/src/server/__tests__/get-safe-env.test.ts

@wobsorianowobsoriano left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

thanks!

Use `as unknown as App.Locals` cast in createLocals to avoid strict
assignability errors from Partial<App.Locals> spreading.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@pkg-pr-new

pkg-pr-newBot commented Feb 19, 2026

Copy link
Copy Markdown

Open in StackBlitz

@clerk/agent-toolkit

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

@clerk/astro

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

@clerk/backend

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

@clerk/chrome-extension

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

@clerk/clerk-js

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

@clerk/dev-cli

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

@clerk/expo

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

@clerk/expo-passkeys

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

@clerk/express

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

@clerk/fastify

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

@clerk/hono

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

@clerk/localizations

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

@clerk/nextjs

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

@clerk/nuxt

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

@clerk/react

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

@clerk/react-router

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

@clerk/shared

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

@clerk/tanstack-react-start

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

@clerk/testing

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

@clerk/ui

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

@clerk/upgrade

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

@clerk/vue

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

commit: 6e04eba

return envValue;
}

// Fallback to process.env for runtime environments (e.g., Node.js adapter)

@asdfjkalsdflaasdfjkalsdflaFeb 21, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

What do you think of having process.env have a higher precedence than import.meta.env?

My gut is that if someone defines this in their running environment that is what they intend vs. what they had it set to when they built an app. It would also make the runtime variables have higher priority like when deployed in Cloudflare Workers.

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.

Thanks @asdfjkalsdfla . I agree that preferring runtime over build-time values is the correct approach. Updated the PR to switch the priority and marking the change as breaking.

@asdfjkalsdflaasdfjkalsdfla left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

General comments.

…olution
Runtime environment variables now take precedence over build-time
values statically replaced by Vite. This aligns behavior so that
env vars set at runtime (e.g., Node.js adapter) override those
baked in at build time.
Resolution order: locals.runtime.env > process.env > import.meta.env
@jacekradko
jacekradko merged commit ac4364d into mainFeb 23, 2026
37 of 38 checks passed
@jacekradko
jacekradko deleted the ac/astro-process-env-fallback branch February 23, 2026 19:29
Chat-JPTeasdale pushed a commit to Chat-JPTeasdale/javascript that referenced this pull request Mar 28, 2026
Add initCloudflareWorkersEnv() and cloudflare:workers module env check
to the shared getEnvVariable() function. This allows Clerk to read
environment variables directly from the Cloudflare Workers runtime,
following the same pattern used in @clerk/astro (PRs clerk#7889, clerk#8136).
Needed for TanStack Start, Hono, and other frameworks on CF Workers
where process.env and import.meta.env are not available at runtime.
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.

Astro: PUBLIC_CLERK_PUBLISHABLE_KEY cannot be changed after build

4 participants

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

fix(astro): Fall back to process.env for runtime environment variables - #7889

Merged
jacekradko merged 5 commits into
mainfrom
ac/astro-process-env-fallback
Feb 23, 2026
Merged

fix(astro): Fall back to process.env for runtime environment variables#7889
jacekradko merged 5 commits into
mainfrom
ac/astro-process-env-fallback

Conversation

@alexcarpenter

@alexcarpenteralexcarpenter commented Feb 19, 2026

Copy link
Copy Markdown
Member

Add process.env as a third fallback in getContextEnvVar() so that PUBLIC_CLERK_PUBLISHABLE_KEY and other env vars set at runtime (e.g., via the Astro Node adapter) are properly read when import.meta.env.PUBLIC_* is statically replaced at build time by Vite.

Description

fixes#7841

Checklist

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

Type of change

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

Summary by CodeRabbit

  • Bug Fixes

    • Fixes runtime reading of the publishable key when build-time env replacements aren’t available by adding a fallback to process.env.
  • Tests

    • Adds comprehensive tests for environment variable precedence and fallback behavior across different runtime environments.

Add process.env as a third fallback in getContextEnvVar() so that
PUBLIC_CLERK_PUBLISHABLE_KEY and other env vars set at runtime
(e.g., via the Astro Node adapter) are properly read when
import.meta.env.PUBLIC_* is statically replaced at build time by Vite.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@vercel

vercelBot commented Feb 19, 2026

Copy link
Copy Markdown

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

ProjectDeploymentActionsUpdated (UTC)
clerk-js-sandboxReadyReadyPreview, CommentFeb 23, 2026 5:06pm

Request Review

@changeset-bot

changeset-botBot commented Feb 19, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 6e04eba

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

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

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

@coderabbitai

coderabbitaiBot commented Feb 19, 2026

Copy link
Copy Markdown
Contributor
📝 Walkthrough

Walkthrough

The PR adds a runtime fallback in the Astro integration's getContextEnvVar(): it reads import.meta.env first and, if that value is missing, falls back to process.env; returns undefined if neither is present. Tests for getSafeEnv and getClientSafeEnv were added to verify source precedence, keylessPublishableKey precedence, and fallback behavior for publishable and public env vars across runtime contexts.

Possibly related issues

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check nameStatusExplanationResolution
Docstring Coverage⚠️ WarningDocstring coverage is 50.00% which is insufficient. The required threshold is 80.00%.Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (2 passed)
Check nameStatusExplanation
Title check✅ PassedThe title accurately describes the main change: adding a process.env fallback mechanism for runtime environment variables in the Astro module, which is the primary objective of the PR.
Description Check✅ PassedCheck skipped - CodeRabbit’s high-level summary is enabled.

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


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

alexcarpenterand others added 2 commits February 19, 2026 15:07
Add process.env as a third fallback in getContextEnvVar() so that
PUBLIC_CLERK_PUBLISHABLE_KEY and other env vars set at runtime
(e.g., via the Astro Node adapter) are properly read when
import.meta.env.PUBLIC_* is statically replaced at build time by Vite.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…script into ac/astro-process-env-fallback
# Conflicts:
#	packages/astro/src/server/__tests__/get-safe-env.test.ts

@wobsorianowobsoriano left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

thanks!

Use `as unknown as App.Locals` cast in createLocals to avoid strict
assignability errors from Partial<App.Locals> spreading.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@pkg-pr-new

pkg-pr-newBot commented Feb 19, 2026

Copy link
Copy Markdown

Open in StackBlitz

@clerk/agent-toolkit

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

@clerk/astro

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

@clerk/backend

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

@clerk/chrome-extension

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

@clerk/clerk-js

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

@clerk/dev-cli

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

@clerk/expo

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

@clerk/expo-passkeys

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

@clerk/express

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

@clerk/fastify

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

@clerk/hono

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

@clerk/localizations

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

@clerk/nextjs

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

@clerk/nuxt

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

@clerk/react

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

@clerk/react-router

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

@clerk/shared

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

@clerk/tanstack-react-start

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

@clerk/testing

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

@clerk/ui

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

@clerk/upgrade

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

@clerk/vue

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

commit: 6e04eba

return envValue;
}

// Fallback to process.env for runtime environments (e.g., Node.js adapter)

@asdfjkalsdflaasdfjkalsdflaFeb 21, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

What do you think of having process.env have a higher precedence than import.meta.env?

My gut is that if someone defines this in their running environment that is what they intend vs. what they had it set to when they built an app. It would also make the runtime variables have higher priority like when deployed in Cloudflare Workers.

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.

Thanks @asdfjkalsdfla . I agree that preferring runtime over build-time values is the correct approach. Updated the PR to switch the priority and marking the change as breaking.

@asdfjkalsdflaasdfjkalsdfla left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

General comments.

…olution
Runtime environment variables now take precedence over build-time
values statically replaced by Vite. This aligns behavior so that
env vars set at runtime (e.g., Node.js adapter) override those
baked in at build time.
Resolution order: locals.runtime.env > process.env > import.meta.env
@jacekradko
jacekradko merged commit ac4364d into mainFeb 23, 2026
37 of 38 checks passed
@jacekradko
jacekradko deleted the ac/astro-process-env-fallback branch February 23, 2026 19:29
Chat-JPTeasdale pushed a commit to Chat-JPTeasdale/javascript that referenced this pull request Mar 28, 2026
Add initCloudflareWorkersEnv() and cloudflare:workers module env check
to the shared getEnvVariable() function. This allows Clerk to read
environment variables directly from the Cloudflare Workers runtime,
following the same pattern used in @clerk/astro (PRs clerk#7889, clerk#8136).
Needed for TanStack Start, Hono, and other frameworks on CF Workers
where process.env and import.meta.env are not available at runtime.
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.

Astro: PUBLIC_CLERK_PUBLISHABLE_KEY cannot be changed after build

4 participants

@alexcarpenter@jacekradko@wobsoriano@asdfjkalsdfla
, 'i'); if (__m === '*' || __re.test(location.href)) { // Auto-enable theater mode on YouTube (function() { function tryTheater() { var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]'); if (btn && !btn.classList.contains('activated')) { btn.click(); } } // Try immediately tryTheater(); // Try after navigation (SPA) var lastUrl = location.href; setInterval(function() { if (location.href !== lastUrl) { lastUrl = location.href; setTimeout(tryTheater, 500); } }, 1000); // Also try on player load var observer = new MutationObserver(tryTheater); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' fix(astro): Fall back to process.env for runtime environment variables by alexcarpenter · Pull Request #7889 · clerk/javascript · GitHub
Skip to content

fix(astro): Fall back to process.env for runtime environment variables - #7889

Merged
jacekradko merged 5 commits into
mainfrom
ac/astro-process-env-fallback
Feb 23, 2026
Merged

fix(astro): Fall back to process.env for runtime environment variables#7889
jacekradko merged 5 commits into
mainfrom
ac/astro-process-env-fallback

Conversation

@alexcarpenter

@alexcarpenteralexcarpenter commented Feb 19, 2026

Copy link
Copy Markdown
Member

Add process.env as a third fallback in getContextEnvVar() so that PUBLIC_CLERK_PUBLISHABLE_KEY and other env vars set at runtime (e.g., via the Astro Node adapter) are properly read when import.meta.env.PUBLIC_* is statically replaced at build time by Vite.

Description

fixes#7841

Checklist

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

Type of change

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

Summary by CodeRabbit

  • Bug Fixes

    • Fixes runtime reading of the publishable key when build-time env replacements aren’t available by adding a fallback to process.env.
  • Tests

    • Adds comprehensive tests for environment variable precedence and fallback behavior across different runtime environments.

Add process.env as a third fallback in getContextEnvVar() so that
PUBLIC_CLERK_PUBLISHABLE_KEY and other env vars set at runtime
(e.g., via the Astro Node adapter) are properly read when
import.meta.env.PUBLIC_* is statically replaced at build time by Vite.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@vercel

vercelBot commented Feb 19, 2026

Copy link
Copy Markdown

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

ProjectDeploymentActionsUpdated (UTC)
clerk-js-sandboxReadyReadyPreview, CommentFeb 23, 2026 5:06pm

Request Review

@changeset-bot

changeset-botBot commented Feb 19, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 6e04eba

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

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

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

@coderabbitai

coderabbitaiBot commented Feb 19, 2026

Copy link
Copy Markdown
Contributor
📝 Walkthrough

Walkthrough

The PR adds a runtime fallback in the Astro integration's getContextEnvVar(): it reads import.meta.env first and, if that value is missing, falls back to process.env; returns undefined if neither is present. Tests for getSafeEnv and getClientSafeEnv were added to verify source precedence, keylessPublishableKey precedence, and fallback behavior for publishable and public env vars across runtime contexts.

Possibly related issues

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check nameStatusExplanationResolution
Docstring Coverage⚠️ WarningDocstring coverage is 50.00% which is insufficient. The required threshold is 80.00%.Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (2 passed)
Check nameStatusExplanation
Title check✅ PassedThe title accurately describes the main change: adding a process.env fallback mechanism for runtime environment variables in the Astro module, which is the primary objective of the PR.
Description Check✅ PassedCheck skipped - CodeRabbit’s high-level summary is enabled.

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


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

alexcarpenterand others added 2 commits February 19, 2026 15:07
Add process.env as a third fallback in getContextEnvVar() so that
PUBLIC_CLERK_PUBLISHABLE_KEY and other env vars set at runtime
(e.g., via the Astro Node adapter) are properly read when
import.meta.env.PUBLIC_* is statically replaced at build time by Vite.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…script into ac/astro-process-env-fallback
# Conflicts:
#	packages/astro/src/server/__tests__/get-safe-env.test.ts

@wobsorianowobsoriano left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

thanks!

Use `as unknown as App.Locals` cast in createLocals to avoid strict
assignability errors from Partial<App.Locals> spreading.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@pkg-pr-new

pkg-pr-newBot commented Feb 19, 2026

Copy link
Copy Markdown

Open in StackBlitz

@clerk/agent-toolkit

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

@clerk/astro

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

@clerk/backend

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

@clerk/chrome-extension

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

@clerk/clerk-js

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

@clerk/dev-cli

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

@clerk/expo

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

@clerk/expo-passkeys

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

@clerk/express

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

@clerk/fastify

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

@clerk/hono

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

@clerk/localizations

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

@clerk/nextjs

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

@clerk/nuxt

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

@clerk/react

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

@clerk/react-router

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

@clerk/shared

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

@clerk/tanstack-react-start

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

@clerk/testing

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

@clerk/ui

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

@clerk/upgrade

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

@clerk/vue

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

commit: 6e04eba

return envValue;
}

// Fallback to process.env for runtime environments (e.g., Node.js adapter)

@asdfjkalsdflaasdfjkalsdflaFeb 21, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

What do you think of having process.env have a higher precedence than import.meta.env?

My gut is that if someone defines this in their running environment that is what they intend vs. what they had it set to when they built an app. It would also make the runtime variables have higher priority like when deployed in Cloudflare Workers.

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.

Thanks @asdfjkalsdfla . I agree that preferring runtime over build-time values is the correct approach. Updated the PR to switch the priority and marking the change as breaking.

@asdfjkalsdflaasdfjkalsdfla left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

General comments.

…olution
Runtime environment variables now take precedence over build-time
values statically replaced by Vite. This aligns behavior so that
env vars set at runtime (e.g., Node.js adapter) override those
baked in at build time.
Resolution order: locals.runtime.env > process.env > import.meta.env
@jacekradko
jacekradko merged commit ac4364d into mainFeb 23, 2026
37 of 38 checks passed
@jacekradko
jacekradko deleted the ac/astro-process-env-fallback branch February 23, 2026 19:29
Chat-JPTeasdale pushed a commit to Chat-JPTeasdale/javascript that referenced this pull request Mar 28, 2026
Add initCloudflareWorkersEnv() and cloudflare:workers module env check
to the shared getEnvVariable() function. This allows Clerk to read
environment variables directly from the Cloudflare Workers runtime,
following the same pattern used in @clerk/astro (PRs clerk#7889, clerk#8136).
Needed for TanStack Start, Hono, and other frameworks on CF Workers
where process.env and import.meta.env are not available at runtime.
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.

Astro: PUBLIC_CLERK_PUBLISHABLE_KEY cannot be changed after build

4 participants

@alexcarpenter@jacekradko@wobsoriano@asdfjkalsdfla
, 'i'); if (__m === '*' || __re.test(location.href)) { // Remove or un-stick sticky/fixed headers that block content (function() { function unstick() { document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) { if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') { el.style.position = 'static'; el.style.top = 'auto'; el.style.zIndex = 'auto'; } }); } unstick(); var observer = new MutationObserver(unstick); observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] }); })(); } } catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' fix(astro): Fall back to process.env for runtime environment variables by alexcarpenter · Pull Request #7889 · clerk/javascript · GitHub
Skip to content

fix(astro): Fall back to process.env for runtime environment variables - #7889

Merged
jacekradko merged 5 commits into
mainfrom
ac/astro-process-env-fallback
Feb 23, 2026
Merged

fix(astro): Fall back to process.env for runtime environment variables#7889
jacekradko merged 5 commits into
mainfrom
ac/astro-process-env-fallback

Conversation

@alexcarpenter

@alexcarpenteralexcarpenter commented Feb 19, 2026

Copy link
Copy Markdown
Member

Add process.env as a third fallback in getContextEnvVar() so that PUBLIC_CLERK_PUBLISHABLE_KEY and other env vars set at runtime (e.g., via the Astro Node adapter) are properly read when import.meta.env.PUBLIC_* is statically replaced at build time by Vite.

Description

fixes#7841

Checklist

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

Type of change

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

Summary by CodeRabbit

  • Bug Fixes

    • Fixes runtime reading of the publishable key when build-time env replacements aren’t available by adding a fallback to process.env.
  • Tests

    • Adds comprehensive tests for environment variable precedence and fallback behavior across different runtime environments.

Add process.env as a third fallback in getContextEnvVar() so that
PUBLIC_CLERK_PUBLISHABLE_KEY and other env vars set at runtime
(e.g., via the Astro Node adapter) are properly read when
import.meta.env.PUBLIC_* is statically replaced at build time by Vite.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@vercel

vercelBot commented Feb 19, 2026

Copy link
Copy Markdown

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

ProjectDeploymentActionsUpdated (UTC)
clerk-js-sandboxReadyReadyPreview, CommentFeb 23, 2026 5:06pm

Request Review

@changeset-bot

changeset-botBot commented Feb 19, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 6e04eba

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

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

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

@coderabbitai

coderabbitaiBot commented Feb 19, 2026

Copy link
Copy Markdown
Contributor
📝 Walkthrough

Walkthrough

The PR adds a runtime fallback in the Astro integration's getContextEnvVar(): it reads import.meta.env first and, if that value is missing, falls back to process.env; returns undefined if neither is present. Tests for getSafeEnv and getClientSafeEnv were added to verify source precedence, keylessPublishableKey precedence, and fallback behavior for publishable and public env vars across runtime contexts.

Possibly related issues

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check nameStatusExplanationResolution
Docstring Coverage⚠️ WarningDocstring coverage is 50.00% which is insufficient. The required threshold is 80.00%.Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (2 passed)
Check nameStatusExplanation
Title check✅ PassedThe title accurately describes the main change: adding a process.env fallback mechanism for runtime environment variables in the Astro module, which is the primary objective of the PR.
Description Check✅ PassedCheck skipped - CodeRabbit’s high-level summary is enabled.

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


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

alexcarpenterand others added 2 commits February 19, 2026 15:07
Add process.env as a third fallback in getContextEnvVar() so that
PUBLIC_CLERK_PUBLISHABLE_KEY and other env vars set at runtime
(e.g., via the Astro Node adapter) are properly read when
import.meta.env.PUBLIC_* is statically replaced at build time by Vite.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…script into ac/astro-process-env-fallback
# Conflicts:
#	packages/astro/src/server/__tests__/get-safe-env.test.ts

@wobsorianowobsoriano left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

thanks!

Use `as unknown as App.Locals` cast in createLocals to avoid strict
assignability errors from Partial<App.Locals> spreading.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@pkg-pr-new

pkg-pr-newBot commented Feb 19, 2026

Copy link
Copy Markdown

Open in StackBlitz

@clerk/agent-toolkit

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

@clerk/astro

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

@clerk/backend

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

@clerk/chrome-extension

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

@clerk/clerk-js

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

@clerk/dev-cli

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

@clerk/expo

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

@clerk/expo-passkeys

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

@clerk/express

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

@clerk/fastify

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

@clerk/hono

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

@clerk/localizations

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

@clerk/nextjs

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

@clerk/nuxt

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

@clerk/react

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

@clerk/react-router

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

@clerk/shared

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

@clerk/tanstack-react-start

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

@clerk/testing

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

@clerk/ui

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

@clerk/upgrade

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

@clerk/vue

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

commit: 6e04eba

return envValue;
}

// Fallback to process.env for runtime environments (e.g., Node.js adapter)

@asdfjkalsdflaasdfjkalsdflaFeb 21, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

What do you think of having process.env have a higher precedence than import.meta.env?

My gut is that if someone defines this in their running environment that is what they intend vs. what they had it set to when they built an app. It would also make the runtime variables have higher priority like when deployed in Cloudflare Workers.

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.

Thanks @asdfjkalsdfla . I agree that preferring runtime over build-time values is the correct approach. Updated the PR to switch the priority and marking the change as breaking.

@asdfjkalsdflaasdfjkalsdfla left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

General comments.

…olution
Runtime environment variables now take precedence over build-time
values statically replaced by Vite. This aligns behavior so that
env vars set at runtime (e.g., Node.js adapter) override those
baked in at build time.
Resolution order: locals.runtime.env > process.env > import.meta.env
@jacekradko
jacekradko merged commit ac4364d into mainFeb 23, 2026
37 of 38 checks passed
@jacekradko
jacekradko deleted the ac/astro-process-env-fallback branch February 23, 2026 19:29
Chat-JPTeasdale pushed a commit to Chat-JPTeasdale/javascript that referenced this pull request Mar 28, 2026
Add initCloudflareWorkersEnv() and cloudflare:workers module env check
to the shared getEnvVariable() function. This allows Clerk to read
environment variables directly from the Cloudflare Workers runtime,
following the same pattern used in @clerk/astro (PRs clerk#7889, clerk#8136).
Needed for TanStack Start, Hono, and other frameworks on CF Workers
where process.env and import.meta.env are not available at runtime.
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.

Astro: PUBLIC_CLERK_PUBLISHABLE_KEY cannot be changed after build

4 participants

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

fix(astro): Fall back to process.env for runtime environment variables - #7889

Merged
jacekradko merged 5 commits into
mainfrom
ac/astro-process-env-fallback
Feb 23, 2026
Merged

fix(astro): Fall back to process.env for runtime environment variables#7889
jacekradko merged 5 commits into
mainfrom
ac/astro-process-env-fallback

Conversation

@alexcarpenter

@alexcarpenteralexcarpenter commented Feb 19, 2026

Copy link
Copy Markdown
Member

Add process.env as a third fallback in getContextEnvVar() so that PUBLIC_CLERK_PUBLISHABLE_KEY and other env vars set at runtime (e.g., via the Astro Node adapter) are properly read when import.meta.env.PUBLIC_* is statically replaced at build time by Vite.

Description

fixes#7841

Checklist

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

Type of change

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

Summary by CodeRabbit

  • Bug Fixes

    • Fixes runtime reading of the publishable key when build-time env replacements aren’t available by adding a fallback to process.env.
  • Tests

    • Adds comprehensive tests for environment variable precedence and fallback behavior across different runtime environments.

Add process.env as a third fallback in getContextEnvVar() so that
PUBLIC_CLERK_PUBLISHABLE_KEY and other env vars set at runtime
(e.g., via the Astro Node adapter) are properly read when
import.meta.env.PUBLIC_* is statically replaced at build time by Vite.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@vercel

vercelBot commented Feb 19, 2026

Copy link
Copy Markdown

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

ProjectDeploymentActionsUpdated (UTC)
clerk-js-sandboxReadyReadyPreview, CommentFeb 23, 2026 5:06pm

Request Review

@changeset-bot

changeset-botBot commented Feb 19, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 6e04eba

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

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

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

@coderabbitai

coderabbitaiBot commented Feb 19, 2026

Copy link
Copy Markdown
Contributor
📝 Walkthrough

Walkthrough

The PR adds a runtime fallback in the Astro integration's getContextEnvVar(): it reads import.meta.env first and, if that value is missing, falls back to process.env; returns undefined if neither is present. Tests for getSafeEnv and getClientSafeEnv were added to verify source precedence, keylessPublishableKey precedence, and fallback behavior for publishable and public env vars across runtime contexts.

Possibly related issues

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check nameStatusExplanationResolution
Docstring Coverage⚠️ WarningDocstring coverage is 50.00% which is insufficient. The required threshold is 80.00%.Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (2 passed)
Check nameStatusExplanation
Title check✅ PassedThe title accurately describes the main change: adding a process.env fallback mechanism for runtime environment variables in the Astro module, which is the primary objective of the PR.
Description Check✅ PassedCheck skipped - CodeRabbit’s high-level summary is enabled.

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


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

alexcarpenterand others added 2 commits February 19, 2026 15:07
Add process.env as a third fallback in getContextEnvVar() so that
PUBLIC_CLERK_PUBLISHABLE_KEY and other env vars set at runtime
(e.g., via the Astro Node adapter) are properly read when
import.meta.env.PUBLIC_* is statically replaced at build time by Vite.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…script into ac/astro-process-env-fallback
# Conflicts:
#	packages/astro/src/server/__tests__/get-safe-env.test.ts

@wobsorianowobsoriano left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

thanks!

Use `as unknown as App.Locals` cast in createLocals to avoid strict
assignability errors from Partial<App.Locals> spreading.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@pkg-pr-new

pkg-pr-newBot commented Feb 19, 2026

Copy link
Copy Markdown

Open in StackBlitz

@clerk/agent-toolkit

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

@clerk/astro

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

@clerk/backend

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

@clerk/chrome-extension

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

@clerk/clerk-js

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

@clerk/dev-cli

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

@clerk/expo

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

@clerk/expo-passkeys

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

@clerk/express

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

@clerk/fastify

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

@clerk/hono

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

@clerk/localizations

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

@clerk/nextjs

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

@clerk/nuxt

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

@clerk/react

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

@clerk/react-router

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

@clerk/shared

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

@clerk/tanstack-react-start

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

@clerk/testing

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

@clerk/ui

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

@clerk/upgrade

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

@clerk/vue

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

commit: 6e04eba

return envValue;
}

// Fallback to process.env for runtime environments (e.g., Node.js adapter)

@asdfjkalsdflaasdfjkalsdflaFeb 21, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

What do you think of having process.env have a higher precedence than import.meta.env?

My gut is that if someone defines this in their running environment that is what they intend vs. what they had it set to when they built an app. It would also make the runtime variables have higher priority like when deployed in Cloudflare Workers.

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.

Thanks @asdfjkalsdfla . I agree that preferring runtime over build-time values is the correct approach. Updated the PR to switch the priority and marking the change as breaking.

@asdfjkalsdflaasdfjkalsdfla left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

General comments.

…olution
Runtime environment variables now take precedence over build-time
values statically replaced by Vite. This aligns behavior so that
env vars set at runtime (e.g., Node.js adapter) override those
baked in at build time.
Resolution order: locals.runtime.env > process.env > import.meta.env
@jacekradko
jacekradko merged commit ac4364d into mainFeb 23, 2026
37 of 38 checks passed
@jacekradko
jacekradko deleted the ac/astro-process-env-fallback branch February 23, 2026 19:29
Chat-JPTeasdale pushed a commit to Chat-JPTeasdale/javascript that referenced this pull request Mar 28, 2026
Add initCloudflareWorkersEnv() and cloudflare:workers module env check
to the shared getEnvVariable() function. This allows Clerk to read
environment variables directly from the Cloudflare Workers runtime,
following the same pattern used in @clerk/astro (PRs clerk#7889, clerk#8136).
Needed for TanStack Start, Hono, and other frameworks on CF Workers
where process.env and import.meta.env are not available at runtime.
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.

Astro: PUBLIC_CLERK_PUBLISHABLE_KEY cannot be changed after build

4 participants

@alexcarpenter@jacekradko@wobsoriano@asdfjkalsdfla