@lit-protocol/contracts-sdk 2.1.83

ContractsSDK is a bundled package that allows you to make calls to Lit Protocol smart contracts. Some contracts come with additional abstracted functions that can be accessed by appending `Util` to the contract variable name, for example, `pkpNftContract`

@lit-protocol/contracts-sdk@2.1.83 was published on 2023-03-16. Its manifest declares 9 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

Deprecated: This package targets a retired Lit Protocol network and is no longer maintained. See https://developer.litprotocol.com for the current SDK.

All @lit-protocol/contracts-sdk versions · Permanent reference to 2.1.83 · View npm registry JSON · Latest release

Package specifications

Version2.1.83
License declarationMIT
Published2023-03-16T17:03:30.894Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count9
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size458.00 KiB
Published file count71
Package typecommonjs
ES module entryNot declared
Default entry./src/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependenciesUnknown
Repository stars157
Repository forks88

Install @lit-protocol/contracts-sdk 2.1.83

npm install @lit-protocol/contracts-sdk@2.1.83
pnpm add @lit-protocol/contracts-sdk@2.1.83
yarn add @lit-protocol/contracts-sdk@2.1.83

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