Checks And Guards
Current local and CI validation paths for the site.
Local commands
bun run typecheck: TypeScript check onlybun run lint: Oxlint onlybun run format:check: Oxfmt check onlybun run format: Oxfmt writebun run build: Full Next.js static build toout/bun run preview:prod: Build and serve the GitHub Pages-shaped output locallybun run check: Lint, format check, typecheck, then buildbun run check:fix: Lint auto-fix, format write, typecheck, then build
What each one catches
- Lint:
finds code issues and style warnings through
oxlint - Format check:
catches files that do not match
oxfmt - Typecheck: catches TypeScript and route typing issues without building
- Build: catches real production build failures, static export problems, and content generation issues
- Preview:
lets you test the GitHub Pages base path locally at
/itamiforge/
CI checks
The GitHub Actions workflow currently does this:
bun install --frozen-lockfilebun run lintbun run format:checkbun run typecheckbun run build- upload the
out/artifact - deploy to GitHub Pages
Security checks
- Socket GitHub App is used outside the custom workflow
- branch protection is expected to enforce the required GitHub check
- local package audit can be checked with
bun audit
Current reality
bun run checkis the main all-in-one local gate- CI splits that same validation into separate steps before deploy
- lint still allows many style warnings, but correctness errors fail
- the lockfile matters because CI installs with
--frozen-lockfile