@clerk/types 4.0.1-snapshot.v71dda29

Typings for Clerk libraries.

@clerk/types@4.0.1-snapshot.v71dda29 was published on 2024-01-30. Its manifest declares 1 runtime dependency and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=18.17.0.

Deprecated: This package is no longer supported. Please import types from @clerk/shared/types instead. See the upgrade guide for more info: https://clerk.com/docs/guides/development/upgrading/upgrade-guides/core-3

All @clerk/types versions · Permanent reference to 4.0.1-snapshot.v71dda29 · Latest release

Package specifications

Version4.0.1-snapshot.v71dda29
License declarationMIT
Published2024-01-30T20:45:55.304Z
Node.js requirement>=18.17.0
Type declarationsBundled declarations
Runtime dependency count1
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size360.48 KiB
Published file count9
Package typeNot declared
ES module entrydist/esm/index.js
Default entrydist/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies1
Repository starsUnknown
Repository forksUnknown

Install @clerk/types 4.0.1-snapshot.v71dda29

npm install @clerk/types@4.0.1-snapshot.v71dda29
pnpm add @clerk/types@4.0.1-snapshot.v71dda29
yarn add @clerk/types@4.0.1-snapshot.v71dda29

Runtime dependencies

Peer requirements

  • None declared

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