Skip to main content

​
Pre-v0.0.1 program

This is the active product program for scripty before the v0.0.1 tag. scripty is a Zig-native JavaScript runtime and package manager (own VM — not V8, JSC, or SpiderMonkey), embedded by hosts such as yappy. Pre-v0.0.1 reorders the work so the language engine is complete against the latest ECMAScript edition first, then the runtime surfaces that only Bun or only Deno ship natively.
Linux only, permanently. scripty builds, CI, and first-party dogfood are Linux-only. Desktop UI never lives in scripty (no webview / Chromium). Hosts such as yappy embed scripty from separate repositories.

​
The three initiatives

See Initiatives for the dependency graph and Roadmap for phases and exit criteria.

​
Why this order

  1. Language first. Frameworks, Node-compat, and host embeds all assume a correct ES engine. Shipping adapters on a partial language subset produces silent lies in the matrices.
  2. Exclusive surfaces next. Shared Node-shaped APIs are large and already tracked elsewhere. Bun-only and Deno-only surfaces are the differentiators for a multi-runtime product story — and they are finite inventories you can matrix honestly.
  3. Hosts and frameworks after the language gate. DX, yappy, and Next/Nuxt/Nest/Solid dogfood remain real goals, but they are not the pre-v0.0.1 gate. See Relationship to the v1 plan.

​
What “v0.0.1” means

Exact definitions of “fully compatible” live in Principles and ES scope.

​
Status at a glance

Never claim “ES2026 complete” or “Bun/Deno compatible” until the matrices say supported or dogfooded.

Principles

How we define compatible, honest, and Linux-only.

Initiatives

I1 / I2 / I3 summary and ordering.

ES Engine

Full ECMAScript compatibility roadmap.

Roadmap

Phases and exit criteria for the program.

Related topics

Pre-v0.0.1 programIntroductionInitiativesRoadmapPrinciples