boxlang-runtime-desktop-electron

Name: boxlang-runtime-desktop-electron
Availability: InStock
Author: BoxLang

Embed a local BoxLang MiniServer inside an Electron shell with Java 21+.

Updated Apr 10, 2026

Search Tags:#packaging #electron #lifecycle #desktop #boxlang #miniserver

Ready to run

npx skills add https://github.com/ortus-boxlang/skills --skill boxlang-runtime-desktop-electron-ortus-boxlang

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: boxlang-runtime-desktop-electron
Source: https://github.com/ortus-boxlang/skills/tree/main/boxlang-developer/runtime-desktop-electron
Command: npx skills add https://github.com/ortus-boxlang/skills --skill boxlang-runtime-desktop-electron-ortus-boxlang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Desktop applications using BoxLang often require embedding a local MiniServer, managing Electron's desktop lifecycle, and ensuring consistent runtime packaging across platforms. This skill provides a blueprint for Electron-based BoxLang runtime that hosts a local MiniServer and handles lifecycle, packaging, and configuration.

Core Features & Use Cases

Electron-based desktop lifecycle management with a BoxLang MiniServer process.
Clear separation of development vs production runtime via miniserver.json, runtime/Package.bx, and .boxlang-dev.json/.boxlang.json files.
Cross-platform defaults and predictable startup for desktop apps.

Quick Start

Set up the Electron-based BoxLang runtime by aligning your project with the structure described here and run the development workflow to launch the desktop app.

Frequently Asked Questions about boxlang-runtime-desktop-electron

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

FAQPage Schema

How do I embed a BoxLang MiniServer inside an Electron desktop application?▼

You can embed a BoxLang MiniServer inside an Electron shell by configuring the desktop lifecycle and packaging a local runtime. This approach ensures a stable BoxLang runtime with predictable startup across platforms.

What configuration files are needed for a BoxLang Electron desktop runtime?▼

A BoxLang Electron desktop runtime requires miniserver.json and .boxlang.json files for deterministic startup. It also uses runtime/Package.bx and .boxlang-dev.json to separate development from production environments.

Do I need Java to run a BoxLang desktop app with Electron?▼

Yes, building a BoxLang desktop app requires Java 21+ to be present. The runtime enforces this prerequisite to ensure the packaged MiniServer operates with deterministic behavior across platforms.

How does desktop lifecycle management work for BoxLang apps?▼

Desktop lifecycle management for BoxLang apps works by orchestrating a local MiniServer process within an Electron shell. This configuration controls startup, runtime behavior, and stable process lifecycle across platforms.

What's the best way to separate development and production runtimes for BoxLang desktop apps?▼

The best way to separate environments is using .boxlang-dev.json for development and .boxlang.json for production, alongside runtime/Package.bx. This configuration ensures predictable startup behavior for each context.

Can I use Electron to package a BoxLang MiniServer for cross-platform desktop deployment?▼

Yes, Electron can package a BoxLang MiniServer for cross-platform desktop deployment. This setup provides controlled lifecycle management and enforces runtime configuration for consistent behavior across operating systems.