Shipped, and what is next

Read from the checklist in the repository README, so it cannot fall behind it.

Monorepo + shared tooling (pnpm · Changesets · CI gates)
typefetch runtime instrumentation & overrides (the devtools seam)
typefetch-query-core + typefetch-react
the React-Query-like layer
type-devtools-core + type-devtools
the cross-transport inspector
type-permission
framework-less capability permissions + optional contract link (NestJS guard)
Pluggable transports
the open TransportRegistry, typefetch-grpc, typefetch-graphql, and a core at zero dependencies
typewire-cli
typewire.config.ts, the project-detecting init wizard, multi-API projects
typewire-nestjs beyond HTTP
gRPC (Connect JSON), GraphQL, and typesocket WS gateways, all from the same contract file
query-core seams
gate · sources · updatedAt · reason: four additive hooks, no behaviour change, that unblock the two packages below. docs/SYNC.md §9
YOU ARE HERE
12 of 12 packages on npm
typewire-syncnext up
cross-tab coordination: mirrored cache writes, cross-tab single-flight, and one leader tab owning the socket. Design in docs/SYNC.md
Standard Schema
accept any Standard Schema validator (Zod 4, Valibot, ArkType, Effect) wherever a contract takes a schema, with zod still the default. Design in docs/SCHEMA.md
typefetch-sse
typed Server-Sent Events and HTTP streaming: a schema per event name, AsyncIterable responses, resume by Last-Event-ID. Design in docs/SSE.md
typewire-offline
a persisted cache and a durable mutation outbox that survives a reload and replays in order on reconnect. Design in docs/OFFLINE.md
typewire snapshot + diff
breaking-change detection against a committed API-surface lockfile
typewire lint · doctor · explain · mock · generate openapi
typewire generate mcp
the same contracts as an MCP tool server, so an agent calls the validated endpoint instead of a hand-written wrapper. Design in docs/MCP.md
type-permission client pre-flight middleware + Vue/React binding recipes
typewire-vue / typewire-angular query adapters
Connect conformance runner in CI
see docs/ROADMAP.md for why it is still open

typewire diffPROPOSED

$ npx typewire diff v1.4.0 v2.0.0
+ user.getUser.response.email
- user.getUser.response.name
~ user.listUsers.request.page → cursor
3 changes · 1 breaking
→ 2 call sites will fail typecheck

Not a shipped command. The CLI ships init, list, test and release-doc today; diff and lint are designed in docs/CLI.md and are what the roadmap above is heading towards.

Honest gaps

type-permission is 0.1.0 on npm but 0.1.1 in this workspace — the repo is behind its own release.
typefetch is 2.0.0 on npm but 2.0.1 in this workspace — the repo is behind its own release.
typesocket is 2.2.0 on npm but 2.2.1 in this workspace — the repo is behind its own release.
type-devtools is 1.1.0 on npm but 1.1.1 in this workspace — the repo is behind its own release.
type-devtools-core is 1.2.0 on npm but 1.2.1 in this workspace — the repo is behind its own release.
typewire-nestjs is 4.0.0 on npm but 4.0.1 in this workspace — the repo is behind its own release.
typefetch-query-core is 1.2.0 on npm but 1.2.1 in this workspace — the repo is behind its own release.
typefetch-react is 1.1.1 on npm but 1.1.2 in this workspace — the repo is behind its own release.
typewire-cli is 0.1.0 on npm but 0.1.1 in this workspace — the repo is behind its own release.
typefetch-encryption is 0.1.0 on npm but 0.1.1 in this workspace — the repo is behind its own release.
typefetch-graphql is 0.1.0 on npm but 0.1.1 in this workspace — the repo is behind its own release.
typefetch-grpc is 0.1.0 on npm but 0.1.1 in this workspace — the repo is behind its own release.
Size budgets are asserted ceilings, not published measurements — CI fails when one is exceeded, but no measured figure is shown.

Full sequencing, including the gaps that are still open ↗