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

@wireio/cluster-tool-shared

v0.1.1

Published

The shared **data contract** for WIRE test clusters — the plain-TypeScript shapes that describe a cluster's persisted layout, consumed by both the harness (`@wireio/cluster-tool`) and the debugging surface (`@wireio/debugging-shared`, `debugging-server`,

Downloads

108

Readme

@wireio/cluster-tool-shared

The shared data contract for WIRE test clusters — the plain-TypeScript shapes that describe a cluster's persisted layout, consumed by both the harness (@wireio/cluster-tool) and the debugging surface (@wireio/debugging-shared, debugging-server, the TUI). Types only — no runtime behavior lives here. Hydration/resolution of these shapes is owned by cluster-tool's provider namespaces (ClusterConfigProvider, BindConfigProvider).

Why this package exists

cluster-tool depends on debugging-shared, so debugging-shared cannot import the harness's types without forming a cycle. Historically that forced hand-maintained structural mirrors of the config shapes — a drift hazard. This package sits below both: each shape is declared exactly once, and every other expression of it (caller options, runtime providers) is derived from or typed against these declarations.

Contents

| Path | Contents | |---|---| | src/cluster/ClusterFiles.ts | ClusterFiles — the on-disk filenames (cluster-config.json, cluster-state.json, cluster-keys.json) | | src/cluster/ClusterState.ts | ClusterState / ClusterStateNode / ClusterStateNodePorts / ClusterStateNodeRole — the secret-free post-bootstrap snapshot (cluster-state.json) | | src/config/BindConfig.ts | BindConfig + the BindConfig* shape family, BindOverrides<T> (the derived caller-options projection), Bind*Options, ClusterTopologyOptions | | src/config/ClusterConfig.ts | ClusterConfig (the cluster-config.json shape) + ClusterConfig* nested family, CollateralRequirement, ClusterExecutablePaths | | src/types/ChainTokenAmount.ts | ChainTokenAmount — harness-local (chain, token) amount tuple |

Design rules

  • Data only. No I/O, no process state, no resolution logic — those live in cluster-tool's providers. This package depends only on @wireio/opp-typescript-models.
  • Derivations over mirrors. Caller-option shapes are derived from the resolved shapes via BindOverrides<T> (recursive all-optional projection with pin-whole atoms) — never hand-written in parallel.
  • Enum→literal assignability. Fields that project identity string enums (Report.Format, Level, LogFileAppender.Format) are typed as literal unions; the enum values satisfy them structurally, so producers need no mapping code.
  • Secret hygiene. cluster-state.json shapes here are secret-free by design; key material (cluster-keys.json) is cluster-tool-private and has no type here.

Consuming

// package.json
"dependencies": { "@wireio/cluster-tool-shared": "workspace:*" }
import {
  ClusterConfig,
  ClusterFiles,
  ClusterState
} from "@wireio/cluster-tool-shared"

Add a project reference to ../cluster-tool-shared/tsconfig.json in the consumer's tsconfig.cjs.json; the root tsconfig paths map and each jest moduleNameMapper already resolve the alias to source.

Build & test

pnpm build   # tsc -b + hybrid ESM/CJS output fixup
pnpm test    # jest (tests/ mirrors src/)