@clerk/ui 1.30.2-canary.v20260812192545

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

@clerk/ui@1.30.2-canary.v20260812192545 was published on 2026-08-12. Its manifest declares 17 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.30.2-canary.v20260812192545 · Latest release

Package specifications

Version1.30.2-canary.v20260812192545
License declarationMIT
Published2026-08-12T19:29:14.159Z
Node.js requirement>=20.9.0
Type declarationsBundled declarations
Runtime dependency count17
Peer requirement count2
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size17316.92 KiB
Published file count3134
Package typemodule
ES module entryNot declared
Default entryNot declared
Side effects declaration["./src/utils/setWebpackChunkPublicPath.ts","./dist-mosaic/styles.css","./register/*"]
Direct advisories0
Resolved graph dependencies199
Repository stars1774
Repository forks484

Install @clerk/ui 1.30.2-canary.v20260812192545

npm install @clerk/ui@1.30.2-canary.v20260812192545
pnpm add @clerk/ui@1.30.2-canary.v20260812192545
yarn add @clerk/ui@1.30.2-canary.v20260812192545

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