nlcst-is-literal

nlcst utility to check whether a node is meant literally

nlcst-is-literal@3.0.0 was published on 2023-07-17. Its manifest declares 3 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.

All nlcst-is-literal versions · Permanent reference to 3.0.0

Package specifications

Version3.0.0
License declarationMIT
Published2023-07-17T12:50:55.342Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count3
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size13.39 KiB
Published file count7
Package typemodule
ES module entryNot declared
Default entryNot declared
Side effects declarationfalse
Direct advisories0
Resolved graph dependencies3
Repository starsUnknown
Repository forksUnknown

Install nlcst-is-literal 3.0.0

npm install nlcst-is-literal@3.0.0
pnpm add nlcst-is-literal@3.0.0
yarn add nlcst-is-literal@3.0.0

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