debug-cross-platform

Debug cross-platform issues between Erlang and JavaScript targets in Gleam projects.

Updated Aug 27, 2026

Search Tags:#testing #debugging #javascript #cross-platform #erlang #ffi #runtime-differences

Ready to run

npx skills add https://github.com/tylerbutler/birch --skill debug-cross-platform

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debug-cross-platform
Source: https://github.com/tylerbutler/birch/tree/main/.claude/skills/debug-cross-platform
Command: npx skills add https://github.com/tylerbutler/birch --skill debug-cross-platform

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debug cross-platform issues that occur on one target (Erlang or JavaScript) and not the other.

Core Features & Use Cases

Provides a structured, step-by-step diagnostic workflow to identify cross-target discrepancies between Erlang and JavaScript runtimes.
Helps diagnose FFI mismatches, platform API differences, and asynchronous behavior to align behavior across targets.
Use case: When tests pass on one target but fail on the other, follow this guide to reproduce, isolate, and fix the root cause.

Quick Start

Run tests on both targets and compare outputs to identify discrepancies.

Frequently Asked Questions about debug-cross-platform

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

FAQPage Schema

Why do my Gleam tests pass on Erlang but fail on JavaScript?▼

Gleam tests passing on Erlang but failing on JavaScript often stem from cross-target runtime differences, FFI mismatches, or asynchronous behavior variations. Use a structured debugging workflow to compare outputs and isolate the target-specific discrepancy.

How do I debug FFI mismatches between Erlang and JavaScript targets?▼

Debug FFI mismatches between Erlang and JavaScript by running tests on both targets and comparing outputs to identify discrepancies. Follow a structured diagnostic workflow to isolate external function interface differences and align platform APIs.

What causes cross-platform runtime differences in Gleam projects?▼

Cross-platform runtime differences in Gleam projects are typically caused by FFI mismatches, platform API variations, and asynchronous behavior between Erlang and JavaScript targets. A structured debugging workflow helps diagnose these specific cross-target discrepancies.

How do I isolate asynchronous behavior discrepancies between Erlang and JavaScript?▼

Isolate asynchronous behavior discrepancies between Erlang and JavaScript by running tests on both targets and comparing their outputs. Apply a structured debugging workflow to reproduce, isolate, and identify the root cause of the cross-target inconsistency.

What is the best way to diagnose cross-target consistency issues in Gleam?▼

The best way to diagnose cross-target consistency issues in Gleam is to run tests on both Erlang and JavaScript targets, compare outputs to identify discrepancies, and follow a structured debugging workflow to check FFI mismatches and platform APIs.