@orpc/client 0.0.0-next.4a31e17

@orpc/client@0.0.0-next.4a31e17 was published on 2025-01-03. Its manifest declares 2 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 @orpc/client versions · Permanent reference to 0.0.0-next.4a31e17 · Latest release

Package specifications

Version0.0.0-next.4a31e17
License declarationMIT
Published2025-01-03T13:00:39.218Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count2
Peer requirement count1
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size9.89 KiB
Published file count11
Package typemodule
ES module entryNot declared
Default entryNot declared
Side effects declarationNot declared
Direct advisories1
Resolved graph dependencies8
Repository stars5723
Repository forks174

Install @orpc/client 0.0.0-next.4a31e17

npm install @orpc/client@0.0.0-next.4a31e17
pnpm add @orpc/client@0.0.0-next.4a31e17
yarn add @orpc/client@0.0.0-next.4a31e17

Runtime dependencies

Peer requirements

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.

Known direct advisories

Evidence and freshness