vendix-monorepo-workspaces

To manage dependencies in an npm workspaces monorepo, each workspace must declare its own production and development dependencies. This approach keeps the root package.json free of production dependencies, preventing cross-project duplication and ensuring predictable builds.

The best way to add a dependency to a specific workspace in an npm monorepo is using the command `npm install <pkg> -w apps/frontend`. This ensures the package is scoped correctly to that workspace rather than being installed globally across the entire repository.

You can build or test a single workspace within a monorepo by running `npm run build -w apps/frontend`. This targets the specific workspace directory, allowing you to execute scripts without triggering builds for unrelated apps or shared libraries.

Npm workspaces handle CI/CD and Docker containerization for monorepos by providing patterns for building per-workspace images. This allows CI pipelines to isolate builds, testing only the specific apps and shared libs impacted by changes rather than rebuilding the entire repository.

Yes, you can use npm workspaces for a monorepo with separate apps and shared libs directories. This structure places orchestration scripts in the root while housing individual configurations inside apps/* and libs/* for predictable builds and easy scalability.

You should avoid putting production dependencies in the root package.json of a monorepo to ensure each workspace remains self-contained. Keeping the root limited to orchestration scripts minimizes cross-impact when adding or removing workspaces and maintains consistent tooling across apps.