Skip to content
TypeWire

// ROADMAP

Shipped, and what is next

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

  1. Monorepo + shared tooling (pnpm · Changesets · CI gates)

  2. typefetch runtime instrumentation & overrides (the devtools seam)

  3. typefetch-query-core + typefetch-react

    the React-Query-like layer

  4. type-devtools-core + type-devtools

    the cross-transport inspector

  5. type-permission

    framework-less capability permissions + optional contract link (NestJS guard)

  6. Pluggable transports

    the open TransportRegistry, typefetch-grpc, typefetch-graphql, and a core at zero dependencies

  7. typewire-cli

    typewire.config.ts, the project-detecting init wizard, multi-API projects

  8. typewire-nestjs beyond HTTP

    gRPC (Connect JSON), GraphQL, and typesocket WS gateways, all from the same contract file

  9. YOU ARE HERE

    12 of 12 packages on npm

  10. typewire snapshot + diffnext up

    breaking-change detection against a committed API-surface lockfile

  11. typewire lint · doctor · explain · mock · generate openapi

  12. Connect conformance runner in CI

    see docs/ROADMAP.md for why it is still open

  13. type-permission client pre-flight middleware + Vue/React binding recipes

  14. type-opengraph

    typed OpenGraph/metadata client

  15. typewire-vue / typewire-angular query adapters

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

  • 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 ↗