--pm yarn is rejected — we standardised on yarn everywhere

Asked 17 Feb 20261,290 views2 answers

8votes

Every repo here uses yarn, so I passed it through and got:

text

--pm must be bun, pnpm or npm (got 'yarn').

Is that a deliberate omission or just something nobody has got to yet? I would rather not have a second package manager on the machine only for this.

asked by Thom Vasseur5,470 · 17 Feb 2026

2 answers

12votes✓
Accepted answer
Deliberate, and narrower than it looks: --pm only chooses which package manager performs the install of the SDODS packages. It has nothing to do with the package manager your own projects use, and it does not go near your repos.
Pick npm and nothing else changes on the machine — it ships with Node, which you already need:
bash
```
curl -fsSL https://sdods.com/install.sh | sh -s -- --pm npm
```
The default is bun, which the installer will install into the SDODS home if you do not have it. If you would rather it did not, --pm npm is the flag that prevents that.
answered by Daniel Oyelaranmaintainer24,177 · 17 Feb 2026
6votes
To be explicit about the part that worries people: SDODS does not require a lockfile, a workspace field or a package manager in your test repository. A workspace scaffolded by sdods init is project YAML, environment YAML and feature files. Your yarn setup and this flag never meet.
answered by Reeta Nandalmaintainer41,280 · 18 Feb 2026

Have the same question?

Ask it with the command you ran and the output you got, and it will be answered here.