What problem does it solve?
Provides clear, practical guidance to securely manage Vercel environment variables and OIDC tokens, preventing leaked secrets, misconfigured environments, and authentication failures during local development and deployments.
Core Features & Use Cases
- Environment bootstrapping: Steps to pull project secrets into .env.local and verify required keys against .env.example.
- CLI operations & lifecycle: Practical usage patterns for vercel env pull/add/ls/rm and strategies to avoid overwriting custom local variables.
- OIDC and troubleshooting: How OIDC tokens are injected, refresh behaviour, common failure modes, and remediation steps for local development.
- Use case: On a fresh developer machine, follow the bootstrap flow to link the project, pull secrets into .env.local, and validate that NEXT_PUBLIC variables are safe for client exposure.
Quick Start
Run vercel link then vercel env pull .env.local --yes and confirm required keys from .env.example are present.