Skip to main content
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:check
  • GET /api/health
  • npm run lint
  • npm run typecheck
  • npm test
  • Playwright
  • GitHub Actions CI
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

  1. After changing env values, restart the dev server and make sure npm run env:check does not show unintentionally active fallback states.
  2. GET /api/health matches expectations.
  3. npm run lint passes.
  4. npm run typecheck passes.
  5. npm test passes.
  6. Playwright passes at least the most important core flow.
If you are preparing a launch, continue to Launch checklists and Testing recipes.