Skip to main content
Use @thru/abi when you need to turn ABI YAML plus raw bytes into structured reflection output, especially for explorers, debuggers, or test harnesses that need human-readable decoded values.

​
Install

npm install @thru/abi

​
When to use it

Choose this package when you need one of these workflows:
  • Decode a flat ABI YAML definition into a type-specific reflection result.
  • Decode instruction, account, or event payloads with the ABI root type already implied.
  • Resolve ABI imports into a manifest before reflection.
  • Format reflection JSON into a compact tree for UI display.

​
Entry point

The package exposes a single public entry point at @thru/abi. 
import {
  buildLayoutIr,
  buildLayoutIrWithManifest,
  configureWasm,
  ensureWasmLoaded,
  formatReflection,
  getManifestPackages,
  reflect,
  reflectAccount,
  reflectAccountWithManifest,
  reflectEvent,
  reflectEventWithManifest,
  reflectInstruction,
  reflectInstructionWithManifest,
  reflectWithManifest,
  resolveImports,
  createManifest,
  validateManifest,
} from "@thru/abi";

​
Common workflows

TaskFunction
Decode a specific ABI typereflect
Decode an instruction payloadreflectInstruction
Decode an account payloadreflectAccount
Decode an event payloadreflectEvent
Resolve imports firstresolveImports, createManifest
Format decoded outputformatReflection

​
Decode a raw instruction

import { ensureWasmLoaded, formatReflection, reflectInstruction } from "@thru/abi";

await ensureWasmLoaded();

const raw = await reflectInstruction(abiYaml, {
  type: "hex",
  value: "0x0123456789abcdef",
});

const formatted = formatReflection(raw);

​
Decode flattened ABI YAML

Use reflect when your ABI YAML is already flattened and you want to decode a specific type.

​
Decode common ABI payloads

Use reflectInstruction, reflectAccount, and reflectEvent when the ABI root type is already implied by the payload.

​
Work with ABI imports

Use resolveImports and createManifest when your ABI uses imports and you want a manifest-based workflow. The manifest-aware helpers mirror the flat-ABI API:
  • reflectWithManifest
  • reflectInstructionWithManifest
  • reflectAccountWithManifest
  • reflectEventWithManifest
  • buildLayoutIrWithManifest
resolveImports currently supports on-chain imports in browser environments. Path, git, and HTTP imports are handled by the CLI bundle flow instead.

​
Formatting

formatReflection turns the raw reflection JSON into the compact tree used by the docs and CLI-style output. Call ensureWasmLoaded() first if you want to preload the WASM module, or use any reflection function before formatting. If you are running in an environment that cannot load the WASM bundle automatically, call configureWasm("/wasm/abi_reflect_wasm_bg.wasm") before the first reflection call. The package also exports the main data shapes used by the formatter and import resolver:
  • FormattedReflection
  • FormattedValue
  • FormattedValueWithByteRange
  • ByteRange
  • Manifest
  • ManifestPackageInfo
  • ResolverConfig
  • ResolutionResult
  • ResolutionError