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

@ariestools/chain-serve-local-s3

v0.1.18

Published

One-call local XL1 test harness: published-chain S3 layout (s3rver) + xl1-cli (api/producer/finalizer/mempool/indexer)

Readme

@ariestools/chain-serve-local-s3

Dev/test only. Boots an ephemeral local XL1 environment for integration and e2e tests. Not for production.

One function call starts:

  1. @ariestools/aries-chain-serve — S3-compatible published-chain layout (/blocks, /state, /indexes) via s3rver
  2. @xyo-network/xl1-cliapi + producer + finalizer + mempool + indexer, publishing finalized blocks and index into that layout

Install

pnpm add -D @ariestools/chain-serve-local-s3

Pulls in @ariestools/aries-chain-serve, @xyo-network/xl1-cli, and @xyo-network/xl1-sdk as runtime dependencies.

Single-call usage

import { startLocalS3Chain } from '@ariestools/chain-serve-local-s3'

const chain = await startLocalS3Chain()

// chain.rpcUrl              http://127.0.0.1:<port>/rpc
// chain.apiPort
// chain.chainId
// chain.blockProducerWallet // path 0 of the insecure test mnemonic
// chain.s3Endpoint          s3rver origin
// chain.s3ReadUrls          { finalized, chainState, index }

await chain.stop()

Vitest setupFile (lifehash-style globals)

// test/setup/api-local-s3.ts
import { afterAll, beforeAll } from 'vitest'
import { registerLocalS3Chain } from '@ariestools/chain-serve-local-s3'

registerLocalS3Chain(
  { beforeAll, afterAll },
  { assignGlobals: true },
)

With assignGlobals: true, specs can read:

| Global | Description | | -------------------- | ------------------------------------------------ | | apiPort | XL1 API port | | rpcUrl | http://127.0.0.1:<port>/rpc | | chainId | Local chain id | | blockProducerWallet| Genesis / producer path-0 account | | s3ReadUrls | { finalized, chainState, index } read base URLs| | s3Endpoint | s3rver base URL |

Options

| Option | Default | | ----------------- | -------------------------------------------- | | apiPort | 8080 + VITEST_WORKER_ID (or free fallback) | | chainId | local-dev fixture id | | mnemonic | insecure test test … junk phrase | | healthTimeoutMs | 120_000 | | assignGlobals | false | | silent | true (s3rver) | | logXl1 | true (child logs → stderr) |

Notes

  • The local API serves /rpc only (no REST datalake). Writers typically run in inline mode; body resolution on the read side is up to the test.
  • S3 credentials accepted by the layout: S3RVER / S3RVER (exported as S3_CREDENTIALS).
  • Parallel vitest workers get distinct preferred API ports via VITEST_WORKER_ID; Prometheus and health-check ports are disabled in the child config to avoid clashes.