Is there a way to force aube to always generate pnpm-lock.yaml?

[hilja]

aube install works fine with existing pnpm-lock.yaml and pnpm-workspace.yaml files. Like docs state:

On install (and on add, remove, update, dedupe), aube picks the lockfile to write from whichever supported file already exists in the project directory. Precedence is: aube-lock.yaml → pnpm-lock.yaml → bun.lock → yarn.lock → npm-shrinkwrap.json → package-lock.json. When none of those exist yet, aube writes aube-lock.yaml.

But if I have lock file drift and run aube clean --lockfile (nukes the lock file) followed by aube install, it creates aube-lock.yaml. And now I have aube-lock.yaml and pnpm-workspace.yaml.

For compatibility reasons with other tools I'd sometimes liked to keep using pnpm-lock.yaml.

[jdx]

Thanks for the report. I confirmed the behavior: clean --lockfile removes every recognized lockfile, so the next install has no existing format to preserve and falls back to aube-lock.yaml.

For lockfile drift, deleting the file is not necessary today:

# Repair only drifted entries and preserve pnpm-lock.yaml
aube install --fix-lockfile

# Or fully re-resolve while preserving pnpm-lock.yaml
aube install --no-frozen-lockfile

PR #1271 adds a persistent creation default for projects that do want to delete every lockfile or start without one:

# .npmrc
default-lockfile-format=pnpm

With that setting, aube clean --lockfile followed by aube install recreates pnpm-lock.yaml. Existing supported lockfiles still win, so the setting does not implicitly convert a project or create a second lockfile.

#1271

AI-assisted — Tool: Codex; model: unavailable; version: unavailable.