Running in CI

Never block

--yes takes the default for every question, so nothing waits for a keypress:

packall --file package.json --yes --out ./bundles

Behind a pipe or without a TTY the same thing happens automatically — the progress display drops to plain lines and prompts take their defaults. --yes makes it explicit, which is worth doing in a script that might one day be run by hand.

--quiet keeps warnings and errors and drops everything else.

Reproduce a bundle exactly

Every interactive or dry run ends by printing the command that reproduces it non-interactively:

  Re-run without --dry-run to fetch them:

    packall react@19.2.8 --layout single --platform linux

Only non-default values are printed, so the line stays short enough to paste. When a lockfile pinned the run, the echoed command names it by path rather than saying detect — so the CI job reproduces that bundle, not whatever lockfile happens to sit beside the package.json there.

Machine-readable output

--json writes a summary to stdout. Everything else keeps going to stderr, so redirecting stdout gives you clean JSON.

packall --file package.json --yes --json > report.json

See the JSON output reference for the shape.