@clerk/ui 1.25.6-snapshot.v20260720201619

Internal package that contains the UI components for the Clerk frontend SDKs

@clerk/ui@1.25.6-snapshot.v20260720201619 was published on 2026-07-20. Its manifest declares 16 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/ui versions · Permanent reference to 1.25.6-snapshot.v20260720201619 · Latest release

Package specifications

Version1.25.6-snapshot.v20260720201619
License declarationMIT
Published2026-07-20T20:18:25.407Z
Node.js requirement>=20.9.0
Type declarationsBundled declarations
Runtime dependency count16
Peer requirement count2
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size16470.58 KiB
Published file count2924
Package typemodule
ES module entryNot declared
Default entryNot declared
Side effects declaration["./src/utils/setWebpackChunkPublicPath.ts","./register/*"]
Direct advisories0
Resolved graph dependencies194
Repository stars1774
Repository forks484

Install @clerk/ui 1.25.6-snapshot.v20260720201619

npm install @clerk/ui@1.25.6-snapshot.v20260720201619
pnpm add @clerk/ui@1.25.6-snapshot.v20260720201619
yarn add @clerk/ui@1.25.6-snapshot.v20260720201619

Runtime dependencies

Peer requirements

  • react ^18.0.0 || ~19.0.3 || ~19.1.4 || ~19.2.3 || ~19.3.0-0
  • react-dom ^18.0.0 || ~19.0.3 || ~19.1.4 || ~19.2.3 || ~19.3.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