A monorepo with ten workspaces requires orchestration. Running pnpm test in each workspace manually is tedious. Running it in every workspace simultaneously overloads the machine. The –filter flag selects which workspaces to target, and the –parallel and –workspace-concurrency flags control how many run at once. The filter syntax is more than a simple name matcher—it…
Zero-Installs is a Yarn pattern that eliminates the need to run yarn install after cloning a repository or switching branches. It works by committing the install artifacts—the PnP loader files and the project-local package cache—directly to version control. The result is a repository that is immediately runnable on checkout, with no network requests and no…
An npm script is a named shell command stored in package.json and executed by npm with a modified environment. The modification is the point: npm prepends node_modules/.bin to the PATH before running the script, so any binary provided by a locally installed dependency can be invoked by name without the full path . This is…
pnpm’s offline capabilities are a direct consequence of its content-addressable store architecture. Every package file that pnpm has ever downloaded is stored once in a global directory. When you run pnpm install –offline, pnpm does not contact the registry. It resolves the dependency tree from the lockfile, locates the required files in the store, and…
The .yarnrc.yml file is the central configuration hub for Yarn Berry (2+). Every project-level setting—how packages are linked, where the cache lives, which registry is queried, how workspaces behave—lives in this single YAML file. Unlike package.json, which is shared with npm and the broader Node.js ecosystem, .yarnrc.yml is Yarn-specific and is the only file that…
npm lifecycle scripts are hooks that run automatically at specific points in a package’s lifecycle—during install, pack, publish, or when a user-defined script is invoked. The pre and post prefixes are the general mechanism: any script named prefoo runs before foo, and postfoo runs after it . The special scripts prepare, prepublishOnly, and the deprecated…
Every yarn install is a network request away from failure. The npm registry can go down, a corporate proxy can block a scoped package, or a build server can be air-gapped entirely. Yarn’s offline caching and mirroring features exist to eliminate that dependency: once packages are downloaded, they are stored locally and can be reused…
Environment variables are the mechanism by which npm scripts receive configuration that varies by machine, by environment, or by deployment target. A script that reads process.env.NODE_ENV or process.env.API_URL is not hardcoded to a single setup; it adapts based on what the surrounding shell or .env file provides. The complication is that setting environment variables in…
A dependency has a bug. The upstream fix is months away, or the maintainer is unresponsive, or the fix exists only in a pull request that has not been merged. Forking the repository is heavy: you lose the link to the original, you must maintain the fork, and your package.json points to a Git URL…
Package maintenance is not a single command but a cycle. npm update advances dependencies within the semver ranges declared in package.json. npm audit inspects the dependency tree for known vulnerabilities and optionally applies fixes. npm uninstall removes a package and cleans up every reference to it. Each command modifies a different artifact—node_modules, package-lock.json, or package.json—and…