start-http-registry

Launch a local HTTP registry server for infrastructure script testing.

72|602|Updated Dec 13, 2021
One-click install
npx skills add https://github.com/hyperlane-xyz/hyperlane-monorepo --skill start-http-registry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: start-http-registry
Source: https://github.com/hyperlane-xyz/hyperlane-monorepo/tree/main/.claude/skills/start-http-registry
Command: npx skills add https://github.com/hyperlane-xyz/hyperlane-monorepo --skill start-http-registry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Start the local HTTP registry server for development and testing infra scripts that require private RPC URL overrides.

Core Features & Use Cases

  • Start the http-registry server in the background to support development workflows.
  • Provide a local registry with configurable RPC URLs for testing Abacus/infrastructure scripts.
  • Use in scenarios like integration tests, dry runs, and local development without impacting production endpoints.

Quick Start

cd <MONOREPO_ROOT> && pnpm -C typescript/infra start:http-registry After starting, note the shell ID and use KillShell to stop it later. The registry will listen on http://localhost:<port> as logged.

Frequently Asked Questions about start-http-registry

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I start a local HTTP registry for testing infrastructure scripts?

To start a local HTTP registry, navigate to your monorepo root and run pnpm -C typescript/infra start:http-registry. This launches a background server on a localhost port, providing a local registry for testing infrastructure scripts.

Why do I need a local HTTP registry for monorepo development?

A local HTTP registry is needed to provide configurable RPC URL overrides for testing Abacus and infrastructure scripts. It allows you to perform integration tests and dry runs locally without impacting production endpoints.

How do I stop the http-registry server after testing?

To stop the http-registry server, use the shell ID outputted when you initially started the process. You must use the KillShell command with that specific ID to terminate the background registry server.

Can I use this local registry setup without pnpm?

No, this local registry setup requires pnpm to execute the start:http-registry script within the typescript/infra directory. You also need access to the monorepo root to run the command properly.

Does the local HTTP registry support custom RPC URLs for dry runs?

Yes, the local HTTP registry supports configurable RPC URLs specifically for testing infrastructure scripts. This enables safe local development, dry runs, and integration tests without affecting production endpoints.