Rip

Rip is a zero-build, full-stack language for reactive UI, schemas, ORM, and server code. It runs directly under Bun, emits clean JavaScript, type-checks through TypeScript 7, and ships a full LSP.

Repository scope

This repository owns the complete Rip product:

• the lexer, grammar, parser generator, and compiler;
• precise bidirectional mappings between Rip and generated artifacts;
• reactive, schema, ORM, component, and standard-library runtimes;
• package and application infrastructure, including rip/sites (Agent, edge, demos);
• VS Code/Cursor, Vim, and highlight.js integrations;
• language, mapping, type, runtime, corpus, and editor test contracts.

Every capability must preserve the compiler's mapping architecture and carry correctness tests at the surfaces it affects.

Open product work is tracked in docs/ROADMAP.md and package-local TODO.md files (for example packages/sites/TODO.md).

Documentation

Working docs (read / rewrite while shipping):

• AGENTS.md — mandatory repository rules and invariants
• packages/AGENTS.md — first-party package mold and earned shapes

Understanding (permanent contracts under docs/):

• docs/SERVER.md — Sites, Janus, manager, worker architecture
• docs/WORKSPACE.md — browser publication / apply contract
• docs/TYPES.md — type-system and editor architecture
• docs/HMR.md — hot-module-replacement design
• docs/FRAME.md — Rip-native hypermedia design
• docs/ROADMAP.md — current open product work
• docs/CLEANROOM.md — clean-room engine rewrite plan

Core commands

bun run test:rip       # language suite (PR code check)
bun run test           # fast compiler/runtime suite
bun run test:all       # exhaustive: extended tier + every package
rip check [paths...]   # headless TypeScript checking over Rip source
bun run parser         # regenerate src/parser.js
bun run corpus
bun run audit

Package work: bun run test from that package directory (for example packages/sites). Browser smoke: bun run test:browser.

test:all needs janus on PATH for the Sites integration lane. Install Janus, or put a Janus build on PATH. The lane exercises that binary and rejects a local Go module replacement; it does not build a separate edge.

REPL

rip on a TTY (or rip -r) starts the interactive REPL: reactive bindings persist across lines, input is syntax-highlighted live from the real lexer, themes auto-detect the terminal background (.theme to override), imports resolve against the session cwd, and -e evaluates one entry. .help inside the session lists the commands.

Two conveniences worth knowing by heart:

• A trailing ; suppresses the echo. The entry still evaluates and still sets _ — only the display goes quiet. The companion of anything that already printed its own answer: show User; prints the table without the REPL then dumping the returned instances.

• A repl.rip in your cwd is the project's own console. It auto-loads at startup and states only what cannot be guessed — usually one line, import './api/db.rip'. Its exports, every schema the app registered, and the rip/db toolkit (sql, findAll, findOne, transaction, show) become your starting bindings, announced by provenance:

  schemas → User, Patient, Order, … · rip/db → sql, findAll, findOne, transaction, show
  rip> show User.where(lastName: /pat/i);
  

Sites (local HTTPS)

janus autostart               # once: the edge, as a service
rip sites add packages/sites/demos/hello
rip sites start hello
# https://hello.via.rip/

Postures and LAN/local trust: packages/sites/README.md.