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

@re-shell/contracts

v0.2.0

Published

Shared TypeScript contracts for Re-Shell UI and CLI integration.

Readme

@re-shell/contracts

Shared zod schemas and TypeScript types that define every shape crossing a process boundary between the Re-Shell CLI and the UI. This package is the single source of truth: each contract is authored as a zod schema and its TS type is derived via z.infer, so validators and types cannot drift.

Part of the Re-Shell monorepo. The wire contract is documented end-to-end in docs/CLI-CONTRACTS.md.

Install

pnpm add @re-shell/contracts

ESM-only. Requires zod (^4).

What it exports

Everything is re-exported from the package root (@re-shell/contracts).

The JSON wire envelope

The canonical envelope every --json CLI command emits:

import type { JsonResponse, JsonSuccess, JsonError } from '@re-shell/contracts';
import { jsonResponseSchema } from '@re-shell/contracts';

// success: { ok: true,  data: T,                     warnings: string[] }
// error:   { ok: false, error: JsonErrorBody,         warnings: string[] }
  • jsonResponseSchema, jsonErrorBodySchema — runtime validators.
  • JsonSuccess<T>, JsonError, JsonResponse<T>, JsonErrorBody — types.

ErrorCode

A closed set of error codes (zod enum) the CLI is allowed to emit, e.g. NOT_IN_MONOREPO, WORKSPACE_NOT_FOUND, TEMPLATE_NOT_FOUND, INVALID_VARIABLES, DOCTOR_ERROR, ANALYZE_ERROR, HEALTH_CHECK_ERROR. Typos cannot leak into output.

import { errorCodeSchema } from '@re-shell/contracts';
import type { ErrorCode } from '@re-shell/contracts';

Domain schemas

Workspace and catalog shapes, each with a schema + inferred type:

  • Enums: packageManagerSchema, workspaceNodeStatusSchema, workspaceAppTypeSchema, workspaceServiceTypeSchema, templateDomainSchema, healthStatusSchema, healthCheckLevelSchema, jobStatusSchema.
  • Workspace: gitSummarySchema, workspaceAppSchema, workspaceServiceSchema, templateSummarySchema, healthCheckSchema, healthSummarySchema, workspaceSummarySchema.
  • Jobs: jobRecordSchema.
  • Command spec: commandSpecSchema, commandSpecInputSchema.

Matching types: PackageManager, WorkspaceNodeStatus, JobStatus, GitSummary, WorkspaceApp, WorkspaceService, TemplateSummary, HealthCheck, HealthSummary, WorkspaceSummary, JobRecord, CommandSpec, CommandSpecInput.

Hub transport (SSE / WS)

Wire messages for the dashboard's token-authed hub-server, validated on both the emit side (hub) and consume side (browser) against one schema:

  • sseEventSchema / SseEvent
  • wsClientMessageSchema / WsClientMessage
  • wsServerMessageSchema / WsServerMessage
  • hubServerConfigSchema / HubServerConfig

Scripts

pnpm --filter @re-shell/contracts build      # tsc -> dist/
pnpm --filter @re-shell/contracts typecheck