ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Adopt pnpm workspaces with a single root lockfile and filtered CI builds to get deterministic installs, prevent phantom dependencies, and speed up CI. This guide explains the minimal design, trust boundaries, operational checks, failure modes, and when to redesign.
A decision guide that compares bun install with pnpm/npm/yarn, outlines trade‑offs, shows how to lock the Bun version in CI, and validates that the lockfile stays stable without changing production behavior.
Running every Terraform root module on every commit wastes CI and hides risk. Terramate stacks plus change detection let you plan only affected code—if your Git metadata is sound.
Monorepo PRs can show fake coverage drops when tests run selectively. Carryforward flags let Codecov reuse the base commit report for unchanged services, enabling per-service coverage gates.
npm workspaces let you symlink local packages from a single root install, share one lockfile, and target scripts per sub-package—without publishing to a registry.
pnpm workspaces avoid the node_modules bloat and phantom dependencies of traditional monorepo installs by using a shared content-addressable store and symlinks. Here is how the model works and how to verify it.
Project references split one tsconfig into a dependency graph so tsc --build can skip unchanged packages. A two-package example, verification steps, and the gotchas.
Monorepos often waste gigabytes of disk space because every package gets its own copy of shared dependencies. pnpm workspaces solve this with a single virtual store, symlinked node_modules, and one shared lockfile.
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.
nodejs
pnpm
terraform
codecov