Managing Local Package Dependencies with Yarn Workspaces
Learn how to implement Yarn Workspaces to manage multiple packages in a single repository, optimize dependency hoisting, and link local packages without manual publishing.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how to implement Yarn Workspaces to manage multiple packages in a single repository, optimize dependency hoisting, and link local packages without manual publishing.
Learn how to use Vitest Workspaces to manage multi-package monorepos, enabling isolated environments like jsdom and node while sharing a single worker pool for performance.
Use workspace:* in pnpm workspaces to link internal packages without publishing. A minimal pnpm-workspace.yaml and package.json setup, how pnpm resolves via symlinks in node_modules/.pnpm, and limits around peer dependencies, build order, and pnpm-only compatibility.
Bazel’s remote cache can turn slow monorepo builds into fast, distributed pipelines. Learn how to configure caching, add remote execution, and monitor hit ratios to cut wall‑clock time.
Dependency Resolution in Mixed Linker Environments Yarn Berry (v2+) introduces the Plug'n'Play (PnP) installation strategy, which replaces the traditional node_modules directory with a .pnp.cjs resolution map. While the nodeLinker setting in .yarnrc.yml allows a project to switch between pnp and node-modules , monorepo architectures often face complexities w
Integration boundary Storybook stores its manager and preview build artifacts in node_modules/.cache/storybook , which means the cache directory is owned by the host project's package manager while its contents are produced by Storybook. After upgrading Storybook or framework addons, stale entries in that directory are a documented source of confusing behavi