Skip to main content
Use thru-cli abi bundle when you want a machine-readable dependency manifest rather than a flattened YAML file.

​
Use This When

  • you are preparing ABI dependencies for WASM-backed or browser tooling
  • you want resolved package content in one JSON artifact
  • you need both local and remote imports resolved before another tool consumes them
Choose another ABI command when:

​
Syntax

thru-cli abi bundle \
  --file <FILE> \
  --output <FILE> \
  [--include-dir <DIR>...] \
  [--verbose]

​
Output

bundle resolves dependencies and writes a pretty-printed JSON manifest that maps packages to resolved ABI YAML content.

​
Minimal Pattern

thru-cli abi bundle \
  --file ./program.abi.yaml \
  --include-dir ./abi \
  --output ./dist/program.manifest.json \
  --verbose

​
Notes

  • bundle is the ABI command most clearly aimed at downstream tooling rather than human review.
  • Verbose mode prints the resolved package count and package names before writing the manifest.
  • If your task only needs a local, publish-ready YAML file, bundle is usually more output than you need.