tla-ts Brings TLA+ Model Checking and Interpretation to TypeScript and JavaScript Environments

Introduction to tla-ts

A new open-source project named tla-ts provides a TLA+ interpreter and model checker written entirely in TypeScript. Designed as a drop-in replacement for the traditional Java-based TLC model checker, tla-ts is capable of running in any environment that executes JavaScript, including web browsers, Node.js, and Bun.

Traditional TLA+ workflows rely heavily on the Java Virtual Machine (JVM) to execute TLC. By implementing the tool in TypeScript, tla-ts eliminates JVM dependencies for developers working in JavaScript-centric environments, aiming to broaden accessibility for formal system modeling.

Core Features and Compatibility

The utility accepts standard TLC options and configuration formats while attempting to mirror its output behavior and exit codes. Configuration files are read from standard `Spec.cfg` paths placed alongside specifications, and multiple paths or glob patterns (such as `specs/*.tla`) can be passed for sequential evaluation.

Key functional aspects include:

• Command Line Interface: Supports standard flags such as `-config`, `-dump` (for state graphs and reachable states), `-lncheck`, `-seed`, and `-workers`.
• Worker Threads: Multi-threaded execution is supported across Node, Bun, Deno, and cross-origin isolated browser pages via `SharedArrayBuffer`.
• Prover Integration: Through its `prove` command, tla-ts interfaces with tlapm options to handle proof obligations, supporting flags like `--toolbox`, `--line`, and `--summary`.
• Module Interoperability: Reads Java-based operator replacements if matching `.class` files with public static methods are present in the specification's directory.

Practical Implications and Technical Boundaries

For software engineers and researchers utilizing formal methods, tla-ts offers a streamlined execution path without requiring Java installations. Benchmarks provided by the project authors indicate performance benefits in specific execution environments, though users must account for environment-specific constraints.

Certain advanced or impure operations—such as `Print`, specific configuration directives like `VIEW`, `POSTCONDITION`, or `_POSSIBLE`, and environments lacking `SharedArrayBuffer` support—will cause execution to fall back to a single thread on the calling process. Additionally, while the tool parses standard TLA+ modules and configuration files, it throws specific errors (`TlaSyntaxError`, `TlaConfigError`, `TlaEvaluationError`, and `TlaUnsupportedError`) when encountering invalid inputs, unknown references, or unsupported language features.

Verification and Further Reading

Readers interested in examining the source code, running benchmarks, or testing the playground environment can review the official repository and documentation.

Official Source: [GitHub - aidenybai/tla-ts](https://github.com/aidenybai/tla-ts)