Getting Wasm files

To add an action step to Betty Blocks, you need its Wasm file. Action steps are published as components on GitHub, so this guide walks through installing the wash CLI and pulling the Wasm file from there.

Installing the wash CLI

wash is the command-line tool for the wasmCloud stack, and it's what you'll use to fetch Wasm files.

Install it with Cargo:

cargo install wash

If you don't have Cargo yet, follow the Cargo installation guide first.

To confirm the install worked, run:

wash --version

You should see something like:

wash          v0.43.0
├ nats-server v2.11.3
├ wadm        v0.21.1
└ wasmcloud   v1.9.1.  

Any extra lines or warnings are fine – you can ignore them. 

Pulling a Wasm file

With wash installed, you can fetch the Wasm file for any published component (the action step you want to add).

1. Go to the component's GitHub page, for example: https://github.com/wasco-dev/glyphic-api.

2. On the right-hand side of the repo, find the Packages section. 

3. Click Packages to open the list of available components — usually one per page.

4. If it says "No packages published", the component hasn't been uploaded to the GitHub package registry. Ask the component author to publish it.

5. Click the component you want. You'll see its versions and a suggested pull command.

The command GitHub shows won't give you a .wasm file directly. Use wash pull instead:

wash pull ghcr.io/wasco-dev/glyphic-api:1.0.0

The file downloads into whatever directory your terminal is currently in. For the example above, you'll end up with a file called glyphic-api.wasm.