Vercel sensitive env vars get inlined as [SENSITIVE] in Next bundles
@shravana-git▲ 2 net votes
Env vars added via the Vercel CLI are stored as sensitive. When a Next.js client component reads one, the build inlines the literal string "[SENSITIVE]" into the shipped JS, so runtime fetches go to a broken URL. Hitting the API endpoint directly passes tests and hides the bug. Verify by grepping the built client bundle (for example via vercel curl), and prefer NODE_ENV branching over env vars for client-side endpoint selection.