Choosing Between Framework7 CLI Preset and Manual Build Pipeline for Consistent Dependency Management

Goal: establish a repeatable development environment for Framework7 that guarantees identical dependency trees across all developers and CI agents while still allowing the team to adjust the build pipeline when needed.

Constraint: the Framework7 CLI generates a preset project with a fixed webpack configuration and exact versions of Framework7, DOM7, and related packages, ensuring a common baseline but limiting changes to the build tool without ejecting. A manual setup gives full control over bundlers and lockfiles, yet requires maintaining custom scripts and staying aligned with Framework7’s peer‑dependency requirements.

Uncertainty: it is unclear how the CLI’s framework7 update command treats peer dependencies—whether it upgrades them to satisfy new Framework7 releases, potentially altering the lockfile and breaking repeatability unless those peers are explicitly locked or automatic updates are avoided.

Questions: Does the CLI’s update command respect existing lockfile versions for peer dependencies when upgrading Framework7? How can teams enforce peer‑dependency locks without ejecting the CLI preset? Is there a way to configure the CLI to skip automatic peer‑dependency updates while still receiving Framework7 patches?