ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
npm workspaces solves monorepo dependency duplication with hoisting and a single lockfile, but phantom dependencies and peer behavior changes require deliberate handling. A practical walkthrough with verification steps.
npm 7+ includes built-in monorepo support via workspaces — no extra tools, single lockfile, symlinked local packages. Here's how it works, a minimal reproducible example, and the gotchas (phantom deps, no version sync) to watch before you publish.
Stop copying shared code between repositories. npm workspaces let you manage multiple packages under one root with a single install.
Learn how pnpm catalogs let you centralize dependency versions in a monorepo, avoid phantom dependencies, and safely update packages across workspaces.
Opera’s Workspaces let you partition tabs into distinct UI groups while sharing session data. This guide shows how to enable, create, and use workspaces, a shared login example, trade‑offs like memory use and lack of isolation, and a real‑world workflow for freelancers and developers.
Workspaces let you compile once and reuse output across jobs in a single workflow. Here is when to use persist_to_workspace, how to wire a build-test-deploy pipeline, and why workspaces are not a cache.
npm workspaces let you manage interdependent packages in one repository by declaring them in a root package.json, hoisting shared dependencies, and symlinking local packages automatically.
pnpm workspaces store every dependency once in a content-addressable store and link it into each package, ending the monorepo habit of keeping ten copies of lodash. Here's how it works, a concrete setup, and the flat-tree trade-off.
An architecture note covering the requirements, minimal file set, trust boundaries, operational checks, failure modes, and change triggers for pnpm workspaces.
javascript
pnpm
circleci
nodejs