vendix-monorepo-workspaces

Manage npm monorepo dependencies and workspace configurations.

5|Updated Aug 23, 2025

Search Tags:#ci/cd #npm #dependencies #docker #monorepo #workspaces

Ready to run

npx skills add https://github.com/Rzyfront/Vendix --skill vendix-monorepo-workspaces

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: vendix-monorepo-workspaces
Source: https://github.com/Rzyfront/Vendix/tree/main/skills/vendix-monorepo-workspaces
Command: npx skills add https://github.com/Rzyfront/Vendix --skill vendix-monorepo-workspaces

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables organizations to manage a multi-project monorepo using npm workspaces with clear, self-contained dependencies per workspace. It emphasizes keeping production dependencies out of the root and ensuring consistent tooling across apps.

Core Features & Use Cases

Auto-contained dependencies: Each workspace declares its own production and development dependencies to avoid cross-project duplication.
Clear structure and governance: Root contains orchestration scripts; apps/ and libs/ house their own configurations for predictable builds.
CI/CD and containerization guidance: Provides patterns for building per-workspace images and integrating with common CI pipelines.
Evolution and scalability: Easy to add/remove workspaces with minimal cross-impact by keeping each workspace self-contained.

Quick Start

From the repository root, install dependencies: npm install
Add a dependency to a specific workspace: npm install <pkg> -w apps/frontend
Build or test a single workspace: npm run build -w apps/frontend

Frequently Asked Questions about vendix-monorepo-workspaces

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I manage dependencies in an npm workspaces monorepo without polluting the root package.json?▼

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.

What is the best way to add a dependency to a specific workspace in an npm monorepo?▼

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.

How do I build or test a single workspace within a monorepo?▼

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.

How does npm workspaces handle CI/CD and Docker containerization for monorepos?▼

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.

Can I use npm workspaces for a monorepo with separate apps and shared libs directories?▼

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.

When should I avoid putting production dependencies in the root package.json of a monorepo?▼

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.