@clerk/shared 4.40.1-canary.v20261014175017

Internal package utils used by the Clerk SDKs

@clerk/shared@4.40.1-canary.v20261014175017 was published on 2026-10-14. Its manifest declares 4 runtime dependencies and 2 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=20.9.0.

All @clerk/shared versions · Permanent reference to 4.40.1-canary.v20261014175017 · Latest release

Package specifications

Version4.40.1-canary.v20261014175017
License declarationMIT
Published2026-10-14T17:57:02.184Z
Node.js requirement>=20.9.0
Type declarationsBundled declarations
Runtime dependency count4
Peer requirement count2
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size4616.00 KiB
Published file count1090
Package typeNot declared
ES module entryNot declared
Default entryNot declared
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies4
Repository starsUnknown
Repository forksUnknown

Install @clerk/shared 4.40.1-canary.v20261014175017

npm install @clerk/shared@4.40.1-canary.v20261014175017
pnpm add @clerk/shared@4.40.1-canary.v20261014175017
yarn add @clerk/shared@4.40.1-canary.v20261014175017

Runtime dependencies

Peer requirements

  • react ^18.0.0 || ~19.0.3 || ~19.1.4 || ~19.2.3 || ~19.3.0-0 (optional peer)
  • react-dom ^18.0.0 || ~19.0.3 || ~19.1.4 || ~19.2.3 || ~19.3.0-0 (optional peer)

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