# Packages and stability

> Every package and entry point, what each is for and where its docs are, and what experimental_ and @stability promise.

Everything server- and client-side is one package, `@trpc12/trpc`. The other packages fit it into a framework or a tool:

| Package                                                                  | For                                                                |
| ------------------------------------------------------------------------ | ------------------------------------------------------------------ |
| `@trpc12/trpc` ([entry points](#trpc12trpc-entry-points))                | Routers, handlers, clients, links, middleware and adapters         |
| [`@trpc12/tanstack-query`](https://v12.trpc.io/v12/docs/integrations/tanstack-query.md)             | TanStack Query options, keys and filters, for any framework        |
| [`@trpc12/tanstack-react-query`](https://v12.trpc.io/v12/docs/integrations/tanstack-query/react.md) | React: context, `useSubscription`, and server components in `/rsc` |
| [`@trpc12/upgrade`](https://v12.trpc.io/v12/docs/migrations/from-v11/codemod.md)                    | The v11 to v12 codemod                                             |

The TanStack packages re-export `@trpc12/tanstack-query`, so an app installs one of them with TanStack's adapter for its framework.

`effect` is a peer dependency of `@trpc12/trpc`, so every install adds both, and the app's own Effect code shares the same copy. No schema library is a dependency: `.input()` takes zod, Valibot, ArkType or any other Standard Schema, or an Effect Schema ([Input and output](https://v12.trpc.io/v12/docs/server/procedures.md#input-and-output)).

## `@trpc12/trpc` entry points

| Entry                     | For                                                                                                                |
| ------------------------- | ------------------------------------------------------------------------------------------------------------------ |
| `@trpc12/trpc/server`     | `initTrpc`, routers, handlers, callers ([The server](https://v12.trpc.io/v12/docs/server/overview.md))                                        |
| `@trpc12/trpc/client`     | `createTrpcClient`, links, `safe` ([The client](https://v12.trpc.io/v12/docs/client/overview.md), [Links](https://v12.trpc.io/v12/docs/client/links.md))                 |
| `@trpc12/trpc/middleware` | `onStart`, `onSuccess`, `onError`, `onFinish` ([Built-in middleware](https://v12.trpc.io/v12/docs/middleware/overview.md))                    |
| `@trpc12/trpc/effect`     | `createEffectClient` ([The Effect client](https://v12.trpc.io/v12/docs/client/effect.md))                                                     |
| `@trpc12/trpc/serializer` | `jsonSerializer`, danSON, `createSyncSerializer` ([Serializers](https://v12.trpc.io/v12/docs/server/serializers.md))                          |
| `@trpc12/trpc/http`       | `serve`, `toHttpEffect` on Effect's `HttpServer` ([Adapters](https://v12.trpc.io/v12/docs/adapters/overview.md))                              |
| `@trpc12/trpc/aws-lambda` | `toLambdaHandler` for API Gateway, ALB and Lambda@Edge ([AWS Lambda](https://v12.trpc.io/v12/docs/adapters/aws-lambda.md))                    |
| `@trpc12/trpc/actions`    | `experimental_createAction`, `experimental_createCallable` ([Server Actions](https://v12.trpc.io/v12/docs/integrations/server-actions.md))    |
| `@trpc12/trpc/interop`    | `createV11Handler`, `fromV11Link` for v11 code ([Serving v11 clients](https://v12.trpc.io/v12/docs/migrations/from-v11/serve-v11-clients.md)) |
| `@trpc12/trpc/extend`     | building blocks for integrations ([Extensions](https://v12.trpc.io/v12/docs/server/extensions.md#building-integrations))                      |

## Stability

An export whose name starts with `experimental_` (such as `experimental_createAction`) may still change in a minor release, and so may every export of a package whose name starts with `experimental-`, whose exports have no prefix. When one becomes stable, it gets its name without the prefix, and the `experimental_` name stays as a deprecated alias until the next major. `npx @trpc12/upgrade` rewrites those imports.

Every export's JSDoc carries `@stability` (`stable` or `experimental`) and `@since`. Until 12.0.0, prereleases promise nothing; `@stability` says how the export is planned to ship.

## Versions

Each package has its own version. When a package releases, every package that depends on it releases too, built against the new version, so the newest version of each `@trpc12/*` package works with the newest of the others. Update them together.

## Internal entry points

`@trpc12/trpc/internal` holds types that declaration emit refers to. Don't import it; it has no semver. `@trpc12/trpc/internal/testing` is a semi-public `TestServer` Effect layer for real-server tests (with `@effect/vitest`'s `it.layer`); it has no compatibility promise either. Test in process with `createRouterClient` or `localLink` ([Server-side calls](https://v12.trpc.io/v12/docs/server/server-side-calls.md)).