golem-build

Build and package Golem components into WASM artifacts with metadata and bridge generation.

Updated May 17, 2026
One-click install
npx skills add https://github.com/Rust-soham/golem-claw --skill golem-build-rust-soham
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: golem-build
Source: https://github.com/Rust-soham/golem-claw/tree/main/packages/golem/.agents/skills/golem-build
Command: npx skills add https://github.com/Rust-soham/golem-claw --skill golem-build-rust-soham

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates slow, error-prone setup and rebuild cycles when you need to compile and package a Golem application into WASM artifacts from your source components.

Core Features & Use Cases

  • One-command build pipeline: Runs prerequisite checks, builds each component, adds component metadata into WASM, and generates inter-component bridge code when applicable.
  • Multi-language component support: Handles Rust (cargo to wasm32-wasip2), TypeScript (typecheck, typegen, rollup, QuickJS WASM injection, optional JS preinitialization), and Scala (Scala.js compilation, linking, QuickJS injection, wrapper generation, WASM composition).
  • Incremental build optimization: Skips unchanged steps via source/target hash tracking, with an option to force full rebuilds.
  • Use case: You’ve modified a Rust and a TypeScript component in a Golem app and need updated WASM outputs in golem-temp quickly while ensuring bridge/SDK glue stays consistent.

Quick Start

Run golem build --yes from the application root directory containing golem.yaml to build all components and produce updated WASM artifacts.

Frequently Asked Questions about golem-build

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build and package Golem application components into WASM?

To build Golem components into WASM, run golem build --yes from your application root. This pipeline compiles Rust, TypeScript, or Scala sources, injects them into QuickJS WASM, and generates necessary bridge code.

What is the best way to compile TypeScript for a Golem WASM project?

Compiling TypeScript for Golem WASM involves typechecking, typegen, and rollup bundling before injecting the JavaScript into QuickJS. The golem build pipeline handles these cross-language steps automatically and generates required SDK glue.

Does the Golem build pipeline support incremental builds for Rust and TypeScript?

Yes, the Golem build pipeline supports incremental builds by skipping unchanged steps via source and target hash tracking. You can also force a full rebuild if needed to ensure all WASM artifacts are completely refreshed.

Can I use cargo to compile Rust components for Golem WASM?

Yes, Rust components are compiled using cargo targeting wasm32-wasip2. The build pipeline automates this compilation step and adds component metadata directly into the resulting WASM artifacts.

Why does my Golem build fail when generating inter-component bridge code?

Golem build bridge code generation requires successful compilation of all multi-language components first. Ensure your Rust, TypeScript, or Scala components compile without errors before the pipeline can generate the inter-component bridges.

How to force a full rebuild of Golem WASM artifacts?

To force a full rebuild of Golem WASM artifacts and bypass incremental step skipping, run the golem build pipeline with the full rebuild option enabled. This ensures all compilation and QuickJS injection steps are executed unconditionally.