@lit-protocol/lit-node-client-nodejs 2.1.162

This `LitNodeClientNodeJs` is created solely to run on Node.js.

@lit-protocol/lit-node-client-nodejs@2.1.162 was published on 2023-05-10. Its manifest declares 22 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/lit-node-client-nodejs versions · Permanent reference to 2.1.162 · View npm registry JSON · Latest release

Package specifications

Version2.1.162
License declarationMIT
Published2023-05-10T18:45:08.231Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count22
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size159.56 KiB
Published file count8
Package typecommonjs
ES module entryNot declared
Default entry./src/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies228
Repository stars157
Repository forks88

Install @lit-protocol/lit-node-client-nodejs 2.1.162

npm install @lit-protocol/lit-node-client-nodejs@2.1.162
pnpm add @lit-protocol/lit-node-client-nodejs@2.1.162
yarn add @lit-protocol/lit-node-client-nodejs@2.1.162

Runtime dependencies

Peer requirements

  • None declared

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