boxlang-runtime-matchbox

Compile and execute BoxLang bytecode on the native Rust runtime without the JVM.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/ortus-boxlang/skills --skill boxlang-runtime-matchbox-ortus-boxlang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: boxlang-runtime-matchbox
Source: https://github.com/ortus-boxlang/skills/tree/main/boxlang-developer/runtime-matchbox
Command: npx skills add https://github.com/ortus-boxlang/skills --skill boxlang-runtime-matchbox-ortus-boxlang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

BoxLang code traditionally requires the JVM; MatchBox offers a native Rust-based runtime to execute BoxLang programs without a JVM, enabling smaller binaries, faster startup, and deployment in environments where the JVM is unavailable.

Core Features & Use Cases

  • Native runtime that compiles BoxLang to bytecode and executes without the JVM.
  • Supports multiple targets: native, wasm, js, esp32 for CLI tools, edge deployments, browser WASM, and embedded devices.
  • Clear guidance on when to use MatchBox vs JVM BoxLang and an overview of the architecture (parser, compiler, VM).

Quick Start

Install MatchBox and run your BoxLang script with the appropriate target to deploy without the JVM.

Frequently Asked Questions about boxlang-runtime-matchbox

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

FAQPage Schema
How do I run BoxLang without a JVM?

You can run BoxLang without a JVM by using MatchBox, a native Rust runtime that compiles BoxLang to bytecode and executes via a Rust VM. This enables faster startup and smaller binaries for your applications.

Can I compile BoxLang to WebAssembly for browser execution?

Yes, you can compile BoxLang to WebAssembly using MatchBox. The runtime supports multi-target output including wasm, allowing you to deploy BoxLang programs directly in browser environments without a JVM.

What is the best way to deploy BoxLang on embedded devices like ESP32?

MatchBox is the best way to deploy BoxLang on embedded devices. It supports the esp32 target natively, allowing you to execute BoxLang bytecode on hardware where a traditional JVM environment is unavailable.

How does the MatchBox native runtime architecture work?

The MatchBox native runtime architecture works by using a parser, a bytecode compiler, and a Rust VM. It processes BoxLang code into bytecode and executes it directly without the JVM.

When should I use MatchBox instead of the standard JVM BoxLang runtime?

You should use MatchBox instead of the JVM BoxLang runtime for CLI tools, edge deployments, browser WASM, and embedded devices. MatchBox provides a JVM-free execution environment for smaller binaries and faster startup.