@clerk/clerk-sdk-node 5.0.53-canary.v9d34d4f

Clerk server SDK for usage with node

@clerk/clerk-sdk-node@5.0.53-canary.v9d34d4f was published on 2024-10-18. Its manifest declares 4 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=18.17.0.

Deprecated: January 10 2025 marks the end of support for @clerk/clerk-sdk-node as previously announced in our October 2024 deprecation notice. Express users can migrate to the @clerk/express package. For more information, you can find our changelog here: https://clerk.com/changelog/2025-01-10-node-sdk-eol

All @clerk/clerk-sdk-node versions · Permanent reference to 5.0.53-canary.v9d34d4f · View npm registry JSON · Latest release

Package specifications

Version5.0.53-canary.v9d34d4f
License declarationMIT
Published2024-10-18T16:07:42.628Z
Node.js requirement>=18.17.0
Type declarationsBundled declarations
Runtime dependency count4
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size73.02 KiB
Published file count9
Package typeNot declared
ES module entryNot declared
Default entry./dist/index.js
Side effects declarationNot declared
Direct advisoriesUnknown
Resolved graph dependenciesUnknown
Repository starsUnknown
Repository forksUnknown

Install @clerk/clerk-sdk-node 5.0.53-canary.v9d34d4f

npm install @clerk/clerk-sdk-node@5.0.53-canary.v9d34d4f
pnpm add @clerk/clerk-sdk-node@5.0.53-canary.v9d34d4f
yarn add @clerk/clerk-sdk-node@5.0.53-canary.v9d34d4f

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

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