Example threads. These questions and answers were written by the SDODS team to document real problems and how to fix them. The people named are illustrative, not real users. Questions asked on this site are marked new.
Every repo here uses yarn, so I passed it through and got:
--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.
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:
curl -fsSL https://sdods.com/install.sh | sh -s -- --pm npmThe 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.
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.
Wrap commands and output in triple backticks and they will render as a code block.
Checking whether you’re signed in…
Have a different question? Ask it.