@clerk/elements 0.23.85-canary.v20251121094130

Clerk Elements

@clerk/elements@0.23.85-canary.v20251121094130 was published on 2025-11-21. Its manifest declares 11 runtime dependencies and 3 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 see the Core 3 release for more information: https://clerk.com/changelog/2026-03-03-core-3

All @clerk/elements versions · Permanent reference to 0.23.85-canary.v20251121094130 · Latest release

Package specifications

Version0.23.85-canary.v20251121094130
License declarationMIT
Published2025-11-21T09:42:57.886Z
Node.js requirement>=18.17.0
Type declarationsBundled declarations
Runtime dependency count11
Peer requirement count3
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size1489.38 KiB
Published file count39
Package typeNot declared
ES module entryNot declared
Default entryNot declared
Side effects declarationfalse
Direct advisories0
Resolved graph dependencies27
Repository stars1774
Repository forks484

Install @clerk/elements 0.23.85-canary.v20251121094130

npm install @clerk/elements@0.23.85-canary.v20251121094130
pnpm add @clerk/elements@0.23.85-canary.v20251121094130
yarn add @clerk/elements@0.23.85-canary.v20251121094130

Runtime dependencies

Peer requirements

  • next ^13.5.7 || ^14.2.25 || ^15.2.3 || ^16 (optional peer)
  • react ^18.0.0 || ^19.0.0 || ^19.0.0-0
  • react-dom ^18.0.0 || ^19.0.0 || ^19.0.0-0

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