Before you act
- Confirm that the scope matches your case.
- Keep recommendations, enforced limits, exceptions, and unstated details distinct.
- Open the official source before relying on the rule for a consequential decision.
Source-backed platform rule
pnpm freezes lockfile generation only when the behavior is enabled, with the documented CI default conditional on an existing lockfile.
RuleRoster is independent and is not affiliated with or endorsed by pnpm.
Direct answer
When pnpm frozen-lockfile behavior is enabled, it does not generate a lockfile and installation fails if the lockfile is out of sync, needs an update, or is absent. The documented default is false outside CI and true in CI only when a lockfile is already present.
Published evidence
The failure contract applies only when frozen-lockfile behavior is enabled. pnpm then does not generate a lockfile and fails installation when the lockfile is out of sync with the manifest, needs an update, or is absent. The documented default is false outside CI and true in CI only when a lockfile is already present.
Service: pnpm. Rule group: lockfile-integrity. Scope is limited to this exact topic and every source-stated qualifier.
Evidence trail
pnpm · verified August 14, 2026
pnpm documentation by Zoltan Kochan and other contributors, Copyright (c) 2016-2022 Zoltan Kochan and other contributors. Source: https://github.com/pnpm/pnpm.io/tree/a50b57862a9e967d6ea0abe5a2c5e335ec24ebd2. Licensed under the MIT License: https://github.com/pnpm/pnpm.io/blob/a50b57862a9e967d6ea0abe5a2c5e335ec24ebd2/LICENSE. Modified by RuleRoster: RuleRoster extracted and restructured facts into typed rule fields and concise answers. Verified 2026-08-14. No endorsement by pnpm or its contributors is implied. Project names and marks remain descriptive source identifiers only.
Interpretation and accountability
If the source or summary appears wrong, submit precise evidence for human review.