Add support for Rune programming language

[hatemhosny]

https://rune-rs.github.io/

Playground: https://rune-rs.github.io/play/

[pullfrog]

Plan: Add support for Rune programming language (#991)

Rune is a dynamic, Rust-like programming language that compiles to WASM. The official site provides a playground with a WASM runtime at https://rune-rs.github.io/js/rune.js and a WASM binary at https://rune-rs.github.io/js/assets/rune_wasm-*.wasm.

Implementation checklist

Files to create (3)

#	File	Notes
1	src/livecodes/languages/rune-wasm/index.ts	Barrel: export * from './lang-rune-wasm';
2	src/livecodes/languages/rune-wasm/lang-rune-wasm.ts	LanguageSpecs with name: 'rune-wasm', title: 'Rune', scriptType: 'text/rune', editorLanguage: 'rust', compiledCodeLanguage: 'rust', extensions: ['rune', 'rn'], liveReload: true, editor: 'script'. Compiler is pass-through (factory returns async (code) => code).
3	src/livecodes/languages/rune-wasm/lang-rune-wasm-script.ts	IIFE runtime script. Reads code from <script type="text/rune"> tags. Loads the Rune WASM runtime, calls rune.module.compile(code, {}), and prints output/errors to console. Exposes livecodes.runeWasm.run() for live reload support.

Files to edit (6)

#	File	Change
4	src/livecodes/vendors.ts	Add CDN URL for Rune WASM runtime. Two approaches: (A) bundle in @live-codes/browser-compilers (like php-wasm) — upload rune.js and rune_wasm-*.wasm to a CDN path under the project's control; or (B) use jsDelivr-proxied GitHub Pages URLs. The challenge: the bundled WASM binary path must match or be configurable via the serverPath option passed to the Rune wasm() init function. Recommend approach A for reliability.
5	src/sdk/models.ts	Add 'rune-wasm' to Language union type and TemplateName union type. Add aliases: 'rune', 'rn'.
6	src/livecodes/models.ts	Add 'text/rune' to Compiler.scriptType union type.
7	src/livecodes/languages/languages.ts	Import runeWasm and add to languages array (in alphabetical position near ruby-wasm).
8	scripts/build.js	Add 'languages/rune-wasm/lang-rune-wasm-script.ts' to iifeBuild() entry points.
9	src/livecodes/html/language-info.html	Add <section data-lang="rune-wasm"> with i18n-bound name, description, links (official site, docs, GitHub repo), and "Load starter template" button.

Editor language mappings (0 new files — map Rune to Rust)

#	File	Change
10	src/livecodes/editor/monaco/monaco.ts	Map 'rune-wasm' → 'rust'
11	src/livecodes/editor/codemirror/codemirror.ts	Map 'rune-wasm' → 'rust'
12	src/livecodes/editor/codejar/codejar.ts	Map 'rune-wasm' → 'rust'

Post-implementation steps

#	Step
13	Run npm run i18n-export to generate i18n translation keys for the new language-info:runeWasm.* entries.
14	Run npm run test:unit and npm run typecheck:app to verify no regressions.

Key design decisions

Language name: rune-wasm (with aliases rune, rn), following the convention of python-wasm, ruby-wasm, etc.

Script type: 'text/rune' — a custom MIME type used to inject code into the result iframe's DOM, consistent with other WASM languages.

Editor language: Mapped to rust since Rune has Rust-like syntax. No dedicated Rune syntax mode exists in Monaco/CodeMirror/Prism.

Live reload: true — the runtime script will expose livecodes.runeWasm.run() so incremental code changes don't require a full page reload, consistent with python-wasm and ruby-wasm.

WASM CDN challenge: The Rune WASM runtime currently loads its .wasm binary from a hardcoded relative path (/js/assets/rune_wasm-*.wasm). When hosted via CDN cross-origin, this breaks. The runtime's internal wasm() function accepts a serverPath option, but the public rune.init() does not forward it. Resolution during implementation: either (a) bundle the Rune runtime JS + WASM in the @live-codes/browser-compilers package (matching the php-wasm pattern), or (b) call wasm() directly with a serverPath if the runtime exposes it, or (c) fork/patch the Rune playground runtime to accept configuration.

Estimated scope

• ~3 new files, ~9 files touched
• No new dependencies
• Moderate complexity due to WASM binary path resolution

Task list (3/4 completed)

• Gather context: issue comments, existing WASM language examples, key files to understand patterns
• Analyze Rune WASM runtime requirements (find CDN URL, supported features)
• Produce structured plan with file changes and implementation steps
• Report plan via pullfrog_report_progress

  ^{｜ Implement plan ➔ ｜ View workflow run ｜ via Pullfrog ｜ Using DeepSeek Pro (free via Pullfrog for OSS) ｜ 𝕏}

[hatemhosny]

Implement it.

For WASM CDN challenge:
for now (to validate it works) let's choose option (c) fork/patch the Rune playground runtime to accept configuration. Import it from src/livecodes/languages/rune-wasm/lang-rune-wasm-script.ts. We can later move it to @live-codes/browser-compilers once we confirm it works.

[pullfrog]

This run was cancelled 🛑

The workflow was cancelled before completion. Please check the link below for details.

  ^{｜ View workflow run ｜ via Pullfrog ｜ 𝕏}

[hatemhosny]

Implement it.

For WASM CDN challenge: for now (to validate it works) let's choose option (c) fork/patch the Rune playground runtime to accept configuration. Import it from src/livecodes/languages/rune-wasm/lang-rune-wasm-script.ts. We can later move it to @live-codes/browser-compilers once we confirm it works.

@pullfrog

[pullfrog]

PR #992 created: feat(languages): add Rune WASM language support

Implemented Rune language support with a patched runtime that uses a fetch intercept to redirect the WASM binary to a CDN URL, solving the WASM CDN cross-origin challenge. All typechecks, lint, and unit tests pass.

Task list (5/5 completed)

• Understand the current state of rune-wasm implementation and the WASM CDN challenge
• Create new files: index.ts, lang-rune-wasm.ts, lang-rune-wasm-script.ts
• Edit vendors.ts, sdk/models.ts, livecodes/models.ts, languages.ts, build.js, language-info.html
• Verify build, lint, and typecheck pass
• Create PR with the changes

  ^{｜ View workflow run ｜ via Pullfrog ｜ Using DeepSeek Pro (free via Pullfrog for OSS) ｜ 𝕏}