Repository navigation
v1.66.0
1.66.0 (2026-10-16)
A prompt to paste into an agent beside the hero (#70)
A prompt to paste into an agent on the home page
The home page now offers a ready-made prompt that builds Battleship against the computer with
Trax and React, with a copy link.
The Trax book, and a roadmap back to 1.0 (#72)
- The docs' Tutorials section is now the Trax book. Chapter 1 builds a shop's order as a train.
- A train's folder holds its contract at the top, its junctions in
Junctions/and every other
type inModels/. - The roadmap lists each release since 1.0 with its version and month.
🤖 Generated with Claude Code
🟦⬛🟥 A page fetches only what it asks for, and entity answers no longer stop the host (#73)
A train answering with entities that refer back to each other starts again
A host exposing a train whose answer has a back-reference (an order's customer, and that customer's orders) refused
to start since 1.64. The generated document now leaves the field that leads back out, and the host logs each one.
A generated document past the host's own MaxExecutionDepth or operation cap now refuses the start, naming its
train, instead of failing every call.
Fetch only what a page needs
Write a .graphql document that selects part of a train's answer, run trax client --documents 'src/**/*.graphql',
and call the typed function it writes, whose result type holds exactly the fields you selected. Name the
trax.documents.json it writes in UsePersistedOperations(p => p.ClientDocuments(path)); the host checks and
registers every document when it starts. See "Fetch only what a component needs" in the docs.
Generated types follow the document
A generated train function now returns <Train>Result, the fields its document selects. types.g.ts keeps only
enums and inputs: code that imported an answer's type from the client imports the result type instead.
All changes
Bug Fixes
- 🟨🟧🟦 stored JSON nests 64 deep, one-offs keep their time, extensions keep Trax's fields (#71) (a7d7ca9)