context 2.0.0-next-8ba989

Simple utility for context propagation within Javascript applications and libraries. Loosely based on the ideas behind React's context, allows you to achieve the same goals (and more) without actually using react. It allows you to keep reference for share

context@2.0.0-next-8ba989 was published on 2021-12-17. Its manifest declares 0 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 context versions · Permanent reference to 2.0.0-next-8ba989 · Latest release

Package specifications

Version2.0.0-next-8ba989
License declarationMIT
Published2021-12-17T15:49:12.656Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count0
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size21.65 KiB
Published file count21
Package typeNot declared
ES module entry./dist/es/context.production.js
Default entry./dist/cjs/context.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies0
Repository starsUnknown
Repository forksUnknown

Install context 2.0.0-next-8ba989

npm install context@2.0.0-next-8ba989
pnpm add context@2.0.0-next-8ba989
yarn add context@2.0.0-next-8ba989

Runtime dependencies

  • None declared

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