Choosing between nest update CLI and manual package.json edits for deterministic rollback after a failed NestJS major upgrade
The goal is to guarantee a reversible upgrade path when a NestJS major release alters decorator signatures or DI configuration, allowing teams to restore the pre‑upgrade state without losing uncommitted work. The nest update CLI speeds up dependency resolution to the latest compatible versions but provides no built‑in mechanism to revert transitive changes,