ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #npm
Learn how to set up npm workspaces, hoist dependencies, verify shared copies, and handle version conflicts in a monorepo.
npm install resolves and can change your dependency tree; npm ci reproduces the lockfile exactly. A decision guide with a behavior comparison, CI implementation, and validation checks.
Why committing package-lock.json and building with npm ci is one of the highest-leverage decisions in a JavaScript repo — and where npm install still belongs.
Learn how npm’s package‑lock.json guarantees reproducible builds and why npm ci is the CI‑friendly command. Discover the engineering trade‑offs and a practical example to help you decide whether to commit your lockfile.
Set up an npm workspace monorepo with minimal design, verify hoisting, run workspace scripts, and handle pitfalls like accidental dependency exposure and version conflicts.
A task guide to running npm ci in CI with a committed package-lock.json: prerequisites, an illustrative workflow, drift checks, and recovery from sync errors and cache corruption.
Learn how to use npm Workspaces to manage monorepos, optimize dependency hoisting, and link local packages using a single root lockfile.
Learn how npm workspaces unify dependency resolution, hoist shared packages, and run cross‑package scripts across a monorepo. Follow a step‑by‑step example, see trade‑offs, and finish with actionable tips.
Stop dependency drift in CI/CD by locking exact versions with package-lock.json and using npm ci to enforce reproducible installs across environments.
nodejs
javascript