@devcycle/bucketing-assembly-script 1.17.2

This package contains the shared logic used by DevCycle products to evaluate a user's information against a set of segmentation filters and determine eligibility for a given feature. It also makes decisions about which variation to serve a user in a multi

@devcycle/bucketing-assembly-script@1.17.2 was published on 2024-04-09. Its manifest declares 1 runtime dependency and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All @devcycle/bucketing-assembly-script versions · Permanent reference to 1.17.2 · Latest release

Package specifications

Version1.17.2
License declarationMIT
Published2024-04-09T18:14:11.847Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count1
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size6391.74 KiB
Published file count19
Package typeNot declared
ES module entryNot declared
Default entryindex.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies13
Repository starsUnknown
Repository forksUnknown

Install @devcycle/bucketing-assembly-script 1.17.2

npm install @devcycle/bucketing-assembly-script@1.17.2
pnpm add @devcycle/bucketing-assembly-script@1.17.2
yarn add @devcycle/bucketing-assembly-script@1.17.2

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