@trpc/client 11.0.0-alpha-tmp-01-26-rootconfigtypes.261

The tRPC client library

@trpc/client@11.0.0-alpha-tmp-01-26-rootconfigtypes.261 was published on 2024-01-26. Its manifest declares 0 runtime dependencies and 1 peer requirement. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All @trpc/client versions · Permanent reference to 11.0.0-alpha-tmp-01-26-rootconfigtypes.261 · Latest release

Package specifications

Version11.0.0-alpha-tmp-01-26-rootconfigtypes.261
License declarationMIT
Published2024-01-26T09:18:39.102Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count0
Peer requirement count1
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size231.43 KiB
Published file count125
Package typeNot declared
ES module entrydist/index.mjs
Default entrydist/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies0
Repository starsUnknown
Repository forksUnknown

Install @trpc/client 11.0.0-alpha-tmp-01-26-rootconfigtypes.261

npm install @trpc/client@11.0.0-alpha-tmp-01-26-rootconfigtypes.261
pnpm add @trpc/client@11.0.0-alpha-tmp-01-26-rootconfigtypes.261
yarn add @trpc/client@11.0.0-alpha-tmp-01-26-rootconfigtypes.261

Runtime dependencies

  • None declared

Peer requirements

  • @trpc/server 11.0.0-alpha-tmp-01-26-rootconfigtypes.261+de5f0b670

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

    How to interpret the specifications

    Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

    Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

    Evidence and freshness