Home

Language

Pattern Matching Exhaustive match with guards and destructuring. Type System Inference, unions, null safety, Result types. Generics Monomorphized generics with trait bounds. Traits Shared behaviour without inheritance. Error Handling Errors as values, propagated with try.

Systems

Memory Model Ownership and borrowing, no collector. Comptime Run real code during compilation. Concurrency Async, await, channels and tasks. FFI Call C without a binding generator.

Toolchain

TypeScript Compiler home tsc checks and emits TypeScript. Macros Hygienic macros over the real AST. Editor & CLI Tooling LSP, formatter, test runner, package manager.
Every language, codegen and tooling row, with status. Capability matrix

Build with Home

Systems Programming Native binaries with predictable latency. Game Development Frame budgets without collector pauses. Operating Systems Freestanding builds, no runtime required.

Ship with the toolchain

Web Services HTTP servers and databases in one binary. CLI Tools Single-file distribution, fast start. TypeScript Migration Type-check today, move code when ready.
Guide
Standard LibraryArchitectureCompiler PipelineConfigurationDX CommandsPackage Management
Capability MatrixTypeScriptNode.jsBunRoadmap

Home repository-tool runtime

Copy page
Copy page as Markdown for LLMs
View as Markdown
View this page as plain text
Open in ChatGPT
Copy content and open ChatGPT
Open in Claude
Copy content and open Claude
Open in Perplexity
Search with Perplexity AI

home-tool runs standalone JavaScript and TypeScript repository utilities on Home's own TypeScript frontend and a native JavaScript engine. It does not delegate parsing or execution to Node, Bun, or Python.

Build it with zig-js (the default when the conventional checkout and archive exist):

zig build home-tool \
  -Dtool-js-engine=zig-js \
  -Dzig-js-root="$HOME/Code/Libraries/zig-js"

The checkout may instead be selected with HOME_ZIG_JS_ROOT. The zig-js backend links only zig-js's public JavaScriptCore-shaped C API. Home's private WebKit/Bun ABI remains confined to the production runtime and is not part of the repository-tool contract.

On macOS, the system JavaScriptCore backend remains available for differential testing:

zig build home-tool -Dtool-js-engine=jsc

Run TypeScript without a separate transpilation step:

zig-out/bin/home-tool run path/to/tool.ts --tool-argument
zig-out/bin/home-tool eval 'const answer: number = 40 + 2; answer' --print

Tools receive console, process, and a deliberately small Home host API:

  • Home.engine reports zig-js or jsc.
  • Home.readTextFile, Home.writeTextFile, and Home.fileExists provide synchronous repository-file access.
  • Home.readFileHex and Home.writeFileHex preserve arbitrary binary bytes through an engine-neutral lowercase hexadecimal transport.
  • Home.spawnSync(argv) resolves the executable through PATH and returns { exitCode, stdout, stderr }.

The runner resolves relative and absolute modules plus offline node_modules packages. TypeScript/JavaScript modules emit to CommonJS, JSON modules load directly, package main/module entries and index.* fallbacks are supported, and the cache is populated before evaluation so CommonJS cycles terminate.

Use zig build home-tool-smoke with either engine selection to verify TypeScript emission, module loading, filesystem access, process execution, and argument setup.

Edit this page on GitHub

Released under the MIT License.

Copyright © 2026 Home Programming Language