3.7 KiB

Workspaces, type checking, builds, and CI

Use this topic for dependencies, public exports, aliases, auto-imports, production builds, or deployment configuration. Runtime requirements come from .nvmrc and the root manifest.

Question Read first Follow through
Workspace and dependency boundaries pnpm workspace, lockfile, workspace ownership Package-boundary check, environment check
Path aliases, type checking, and auto-imports TypeScript project graph, shared configuration, Vite aliases Plugin configuration, generated declarations, Vitest configuration
Build entry points, deployment base, and SEO Application Vite configuration, deployment configuration, site metadata Documentation configuration, artifact assembly, deployment conventions
CI, container images, and release artifacts GitHub Actions, Dockerfile, Compose Full verification workflow, toolchain history

Each workspace's package.json#exports defines its public exports. Compare Vite, TypeScript, and Vitest resolution when changing aliases. Update generated declarations through configuration. When publishing the combined site, check both the admin and documentation bases.

Targeted verification: pnpm harness verify toolchain runs package-boundary and type checks. For changes to dependencies, public exports, or build configuration, run pnpm harness verify all once at completion using the verification scope. Preview affected entry points when build artifacts or deployment paths change. Toolchain prose alone does not trigger these runtime checks. Passing targeted checks does not prove CI, Docker, or production publication succeeded.