npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@xemahq/distribution-resolver

v0.1.1

Published

This package belongs to **Layer 1** — a pure, framework-agnostic runtime SDK that depends only on `@xemahq/kernel-contracts` (Layer 0) + Node built-ins (no NestJS, no filesystem, no network).

Downloads

389

Readme

@xemahq/distribution-resolver

This package belongs to Layer 1 — a pure, framework-agnostic runtime SDK that depends only on @xemahq/kernel-contracts (Layer 0) + Node built-ins (no NestJS, no filesystem, no network).

It is the resolver behind the Xema PACKAGING plane: it turns a declarative xema-distribution.json (Distribution) plus the set of available biomes into a deterministic distribution.lock.json (DistributionLock) — the single artifact every downstream consumer (deploy-roster generator, test-suite mapping, biome-host boot filter, appliance build) reads. No consumer re-applies the distribution rules; the lockfile is the hard boundary.

Usage

import {
  resolveDistribution,
  type AvailableBiome,
} from '@xemahq/distribution-resolver';
import { type Distribution } from '@xemahq/kernel-contracts/distribution';

const lock = resolveDistribution(distribution, availableBiomes, {
  // optional: a parent Distribution when `distribution.extends` is set
  parents: { [parent.id]: parent },
  // optional: caller-stamped fields (the resolver holds no clock / randomness)
  resolvedAt: new Date().toISOString(),
  inputHash: '<sha256-of-inputs>',
});

resolveDistribution(distribution, availableBiomes, opts?) is a pure function (no IO, no clock, no randomness). It is fail-fast: an absent parent, a missing requires, an attempt to exclude a kernel-tier biome, or an origin disallowed by trustPolicy.allow throws.

Resolution rules (enforced, fail-fast)

  • extends composes parent → child (parent include/exclude/platformServices first, child overrides; child include appended, child exclude applied last).
  • include selectors: { tier } | { origin } | { biome, version? }. Tier/origin selectors NEVER pull audience: operator biomes; only an explicit { biome } selector may.
  • exclude removes biomes by id; excluding a kernel-tier biome is an error.
  • Kernel-tier biomes are ALWAYS included (a platform invariant) and are mandatory: true regardless of selectors.
  • An included biome whose requires are not all present in the resolved set → error.
  • trustPolicy.allow gates by BiomeOrigin; a disallowed origin → error.
  • Output biomes are sorted by id for stable, deterministic output. The result is parseDistributionLock-validated before return.