This is not a user-facing product feature, but it is essential for keeping setup, custom work, and launch safe. This area helps the team verify that changes have not damaged application readiness.
What this feature includes
npm run env:checkGET /api/healthnpm run lintnpm run typechecknpm test- Playwright
- GitHub Actions CI
Related routes, endpoints, and commands
Because
npm run env:check now loads env files from the working directory using the same pattern as Next.js, its output is usually closer to the behavior of the running dev server.Main dependencies
What teams usually customize
- smoke tests,
- staging URLs,
- test data,
- internal QA flow,
- the threshold for “ready to deploy.”
When this feature matters most
- before launch,
- after large custom work,
- during handoff to another developer or client,
- when bugs appear in staging or production.
Verification checklist
- After changing env values, restart the dev server and make sure
npm run env:checkdoes not show unintentionally active fallback states. GET /api/healthmatches expectations.npm run lintpasses.npm run typecheckpasses.npm testpasses.- Playwright passes at least the most important core flow.