<!-- QuestI have a Next.js 16.2.3 app deployed to Vercel, and NEXT_PUBLIC_* environment variables set in the project dashboard are not reaching the build. The values come through as undefined at runtime, breaking my Supabase client initialization. **Setup** - Repo is a monorepo with the Next.js app in a subdirectory: `exteriors-crm/` - Root Directory in Vercel is correctly set to `exteriors-crm` - Framework Preset is set to Next.js - Production branch is `feature/job-profile` - Env vars are defined in Settings > Environment Variables: - NEXT_PUBLIC_SUPABASE_URL - NEXT_PUBLIC_SUPABASE_ANON_KEY Both are scoped to Production, Preview, and Development. Not marked sensitive/encrypted. **Symptom** Runtime error in Vercel logs: Error: Your project's URL and Key are required to create a Supabase client! (from @supabase/ssr, fires when the URL or key arg is falsy/undefined) **What I verified** To confirm env vars aren't reaching the build, I added a debug page that reads process.env.NEXT_PUBLIC_SUPABASE_URL directly and renders it. On production it shows: URL: UNDEFINED URL length: 0 Key (first 10 chars): UNDEFINED Locally with the same code and a .env.local file, the page shows the actual values. So the code is correct; env vars just aren't present during the Vercel build. **What I tried** - Deleted and re-added both env vars - Forced fresh rebuild with "Use existing Build Cache" unchecked - Verified no duplicate env vars (searched full env vars list) - No Vercel-Supabase integration installed - Deleted a .env.local.example file that was being detected by the build **The weird detail** When I try to add a third test NEXT_PUBLIC_* variable, Vercel lets me select Production and Preview but blocks me from selecting Development — as if a hidden Development-scoped version already exists. But no such entry shows in the env vars list (searched with Cmd+F). **Build log shows** ▲ Next.js 16.2.3 (webpack) Build Completed in /vercel/output [41s] Deployment completed All 41 routes are built and deployed as functions correctly. Build succeeds, just without env vars. Any help tracking down why these vars aren't available at build time would be appreciated.ions that get answered the fastest are the ones with relevant info included in the original post. Be sure to include all detail needed to let others see and understand the problem! --> <!-- Current versus Expected behavior --> <!-- Code, configuration, and steps that reproduce this issue --> <!-- Project information (URL, framework, environment, project settings) -->
