starwards-monorepo

An npm workspace monorepo coordinates multiple packages with enforced build order. Start by ensuring your core module builds first, then dependent modules follow in sequence. Use `npm run build` to trigger the full orchestrated build across all modules, producing consistent artifacts in cjs/ and dist/ directories.

Build order matters in monorepos. When you modify the core module, dependent modules won't see the changes until core rebuilds and its artifacts are linked. Always rebuild core first, then rebuild dependent modules in the correct sequence to resolve missing module errors.

Use a 3-terminal development workflow: run watch mode in core, start dev servers in dependent modules, and execute integration tasks in a third terminal. This enables hot-reloading and immediate feedback across the monorepo without manual rebuilds.

Yes, selective module builds are supported through npm workspace scripts like `build:core` and targeted module commands. Run selective builds when you've only modified specific modules, but ensure core rebuilds first if its dependencies changed.

Integrate testing workflows through monorepo orchestration scripts that run unit and E2E tests across environments (browser, node-red, server, e2e). CI/CD pipelines coordinate the same build order and testing sequence as local development for consistency.

Core must build first, followed by server, browser, node-red, and e2e modules in dependency order. This enforced sequence prevents missing dependencies and ensures parallel builds can execute safely without conflicts or rebuild failures.