rune init
Writes rune.config.ts in the current directory. It refuses to overwrite an existing file and
exits 1 when one is there.
A fresh config
rune.config.ts
The generated file loads through the normal pipeline. rune list works immediately after init.
Seeding from package.json
Reads the nearest package.json and writes one command script per entry in its scripts field,
keeping the command strings exactly as they were.
Given:
packages/api/package.json
The result:
rune.config.ts
Scripts are written sorted by name. Descriptions are left out, because package.json has nowhere
to put one.
Move the file to the repository root and delete the entries that belong to one package only. What remains is the shared set. Adopting Rune in a monorepo covers the rest.