@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-cli — api + 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:

Options

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.
• If xl1 exits before its API answers, the thrown error carries the tail of its stderr, even with logXl1: false.