@clerk/clerk-react 4.26.7-staging.v3bf6410

Clerk React library

@clerk/clerk-react@4.26.7-staging.v3bf6410 was published on 2023-10-18. Its manifest declares 3 runtime dependencies and 1 peer requirement. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=14.

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

All @clerk/clerk-react versions · Permanent reference to 4.26.7-staging.v3bf6410 · Latest release

Package specifications

Version4.26.7-staging.v3bf6410
License declarationMIT
Published2023-10-18T10:26:59.486Z
Node.js requirement>=14
Type declarationsBundled declarations
Runtime dependency count3
Peer requirement count1
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size599.41 KiB
Published file count331
Package typeNot declared
ES module entry./dist/esm/index.js
Default entry./dist/cjs/index.js
Side effects declaration["./dist/cjs/index.js","./dist/cjs/polyfills.js","./dist/esm/index.js","./dist/esm/polyfills.js"]
Direct advisories0
Resolved graph dependencies8
Repository stars1774
Repository forks484

Install @clerk/clerk-react 4.26.7-staging.v3bf6410

npm install @clerk/clerk-react@4.26.7-staging.v3bf6410
pnpm add @clerk/clerk-react@4.26.7-staging.v3bf6410
yarn add @clerk/clerk-react@4.26.7-staging.v3bf6410

Runtime dependencies

Peer requirements

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