ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
pnpm Upgrade Failure: Lockfile vs Global Store Consistency The goal is to understand how pnpm behaves when an upgrade operation is interrupted and the lockfile becomes partially updated while the global store remains intact. The main uncertainty is whether pnpm offers any automatic rollback mechanism that restores the lockfile to its pre‑upgrade state or whe
Goal Establish a repeatable development environment where pnpm install produces an identical pnpm-lock.yaml on every machine and in CI, regardless of when the lockfile is regenerated or which pnpm major version is used. Constraints and uncertainty The resolution-mode setting controls how version ranges are resolved when the lockfile is updated. time-based se
Context A deployment pipeline running pnpm install --frozen-lockfile aborts with ERR_PNPM_OUTDATED_LOCKFILE when package.json no longer matches the committed pnpm-lock.yaml . The error names the mismatching specifiers, pinpointing drift between the manifest and lockfile. Goal Decide whether to catch lockfile staleness earlier via a pre-commit or CI gate (e.g
Goal Build a repeatable Racket development setup that consistently loads the same package versions across different machines. Constraints The current raco pkg tool does not generate a lockfile; it only records exact versions in pkginfo.rktd , and transitive dependencies are not pinned automatically. Manual version specification in info.rkt or using --no-deps
When using Bun's --frozen-lockfile flag, the lockfile guarantees that direct and transitive dependencies are installed at the exact versions recorded in bun.lockb . However, the flag does not constrain how Bun handles optional dependencies listed in package.json . Depending on the target platform and the package’s optionalDependencies field, Bun may still re
Goal: achieve deterministic builds for a PureScript project that calls JavaScript via FFI. Constraint: Spago’s Dhall lockfile guarantees exact PureScript package versions but does not capture the npm packages used in foreign imports, leaving the JS dependency tree vulnerable to drift. Uncertainty: teams can either rely solely on Spago's lockfile and manage J
Goal: ensure that a Nimble lockfile captures the exact Nim compiler version used during dependency resolution so that rebuilding the project on any machine yields bit‑identical binaries. Currently, Nimble writes package versions and source URLs to nimble.lock but omits the compiler version; the minNimVersion field in nimble.yml only specifies a minimum versi
Goal Determine whether a pnpm installation can safely revert to an older CLI version after a lockfile schema upgrade without manual intervention. Constraints & Uncertainty The CLI automatically bumps the lockfile to the newest schema (e.g., v6) when running pnpm install with a newer pnpm release. Older pnpm binaries cannot parse newer lockfile versions,
pnpm