What happens if the lock file and the packageManager field disagree?

The lock file wins. It is the file that actually determines the installed tree, so it is the more reliable signal.

How do I force a different package manager?

Pass --pm with npm, pnpm, yarn or bun. The flag takes priority over both the lock file and the packageManager field.

Yes. Every configuration file is created with skip-if-exists semantics and package.json is merged, so a second run only adds what is missing.

How DevFlow detects your package manager, TypeScript, React, Next.js, Vue or NestJS stack and monorepo layout, and which flags override it.

DevFlow reads your project structure to build a ProjectContext — used by every module to generate appropriate configs.

Detection priority:

CLI flag — --pm pnpm always wins
Lock file — pnpm-lock.yaml → pnpm, yarn.lock → yarn, bun.lockb → bun, package-lock.json → npm
packageManager field — in package.json (e.g., "packageManager": "pnpm@9.0.0")
Default — npm

Detected by presence of tsconfig.json in the project root. When TypeScript is detected:

DevFlow inspects dependencies and devDependencies in package.json:

You can override any detected value via CLI flags:

# Force package manager
devflow --pm pnpm

# Force CI provider
devflow --ci gitlab

DevFlow is idempotent. Every module's detect() method checks for existing configurations:

If a config file already exists (e.g., eslint.config.mjs), the file is left untouched — every create-file action is skip-if-exists
The wizard shows the detected modules, and the file is never overwritten on a re-run
File creation actions use skipIfExists: true by default, and package.json is merged rather than replaced