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

@dac-cloud/manifests

v0.1.0

Published

Per-chain protocol manifest types and HTTP loader for the DAC Cloud SDK.

Readme

@dac-cloud/manifests

Per-chain protocol manifest types and HTTP loader for the DAC Cloud SDK.

A protocol manifest is a JSON document that maps a single EVM chain to the deployed addresses of every DAC Cloud contract (factories, implementations, evaluators, modules, plus shared addresses like permit2).

Install

npm install @dac-cloud/manifests

Usage

import { fetchManifest, type ProtocolManifest } from "@dac-cloud/manifests";

const protocol: ProtocolManifest = await fetchManifest(31337, "https://api.dac.cloud");
// protocol.dacFactory, protocol.coreModuleFactory, protocol.permit2, ...

fetchManifest(chainId, apiUrl) issues GET ${apiUrl}/manifest/${chainId}, validates required fields, and returns the typed manifest. Throws on missing manifest, network error, or schema violation.

What's in a Manifest

interface ProtocolManifest {
  chainId: number;

  // Required core (3):
  dacFactory: `0x${string}`;
  coreModuleFactory: `0x${string}`;
  permit2: `0x${string}`;

  // 40 optional address fields — factories and implementations for every
  // DAC component (DAC cell, deal cell, deal, evaluators, modules, ...).
  // Plus optional metadata: blockNumber, deployer.
}

Exported helpers:

  • PROTOCOL_MANIFEST_CORE_ADDRESS_KEYS — the 3 required core keys
  • PROTOCOL_MANIFEST_ADDRESS_KEYS — all 43 address keys
  • isProtocolAddress(value) — type guard for 0x... 20-byte hex
  • requireProtocolAddress(manifest, key) — typed getter that throws if a field is missing

Loader Behavior

  • Network-only: no local-file loader, no bundled manifest. Always fetched from a running backend.
  • Per-chain: one fetch per chain. Multi-chain consumers call fetchManifest once per chain.
  • Validation: chainId is an integer, all 3 core addresses are valid hex; optional fields are validated only when present.

Used By

  • @dac-cloud/corecreateDacCoreClient and createDacTransactionBuilder require a ProtocolManifest in their options.
  • @dac-cloud/cli — the CLI runtime fetches a manifest per command via --api-url + --chain-id.

Documentation

Manifests — full schema, multi-chain patterns, integration.

Build

npm install
npm run build
npm run typecheck