meerkat-wasm

Build, bundle, and run Rust crates as wasm32 modules with the Meerkat embedded runtime.

19|5|Updated Jan 22, 2026

Search Tags:#tooling #rust #browser #wasm-bindgen #wasm32 #embedded-runtime #mobpack

Ready to run

npx skills add https://github.com/lukacf/meerkat --skill meerkat-wasm

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: meerkat-wasm
Source: https://github.com/lukacf/meerkat/tree/main/.claude/skills/meerkat-wasm
Command: npx skills add https://github.com/lukacf/meerkat --skill meerkat-wasm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Guides developers to build, bundle, and run Rust crates as wasm32 modules using the Meerkat embedded runtime, enabling browser- and Node-based deployments for mobpacks.

Core Features & Use Cases

Guidance for wasm32 compilation and platform gating patterns (target_arch cfgs) to keep crates portable.
Tok io aliasing, cfg-gating strategies, and override-first resource injection patterns for embedded runtimes.
Embedded runtime bootstrap, mobpack integration, and browser/WebAssembly debugging workflows for practical projects.

Quick Start

Initialize a wasm32 build of the Meerkat runtime and bootstrap it in a browser or headless environment.

Frequently Asked Questions about meerkat-wasm

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

FAQPage Schema

How do I compile Rust crates to wasm32 for an embedded browser runtime?▼

To compile Rust crates to wasm32 for an embedded browser runtime, apply platform-specific dependency gating and tokio aliasing strategies. This ensures modules run correctly within the Meerkat runtime environment.

What is cfg-gating and how does it keep Rust wasm32 modules portable?▼

cfg-gating uses target_arch configuration flags to conditionally compile code based on the wasm32 architecture. This keeps Rust crates portable across browser and Node-based deployments by excluding platform-specific dependencies during WebAssembly compilation.

How do I bootstrap a mobpack in a browser or headless WebAssembly environment?▼

To bootstrap a mobpack in a browser or headless WebAssembly environment, initialize a wasm32 build of the Meerkat embedded runtime and apply override-first resource injection patterns to properly supply required dependencies during the runtime bootstrap process.

Does tokio work with wasm32 or do I need aliasing for WebAssembly runtimes?▼

Tokio requires aliasing for wasm32 WebAssembly runtimes because native async features are incompatible with the browser environment. Applying tokio aliasing strategies ensures async Rust crates function correctly within the embedded Meerkat runtime.

What are the limitations when debugging WebAssembly modules in an embedded runtime?▼

Debugging WebAssembly modules in an embedded runtime is limited by browser and headless environment constraints. Platform-specific dependency gating and cfg-gating patterns must be strictly enforced to prevent compatibility issues during cross-platform deployment.