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

@feelai/contract

v1.0.7

Published

An object-only type-safe contract definition library for sharing input/output schemas between client and server, preventing circular dependency issues.

Readme

@feelai/contract

An object-only type-safe contract definition library for sharing input/output schemas between client and server, preventing circular dependency issues.

Features

  • Type Safety: Uses typebox to define schemas.
  • Contract Definition: Define API, Stream, and Socket contracts in a central place.
  • Static Type Inference: Extract static TypeScript types from your runtime contract definitions.
  • Separation of Concerns: Keep your API definitions separate from implementation details.

Installation

bun add @feelai/contract
# or
npm install @feelai/contract
# or
yarn add @feelai/contract

Usage

1. Define your Contract

Create a file (e.g., todoListContract.ts) to define your API structure. It is recommended to define core schemas separately to reuse them. Every schemas are defined using typebox, must be object schema or undefined.

import { Contract, defineApiMap, defineSocketMap, defineStreamMap } from "@feelai/contract";
import { Type } from "typebox";

// -------------------------------------------------------------------------
// 1. Define Schemas
// -------------------------------------------------------------------------

export const TaskSchema = Type.Object({
  id: Type.String(),
  title: Type.String(),
  completed: Type.Boolean(),
  createdAt: Type.Number(),
});

// -------------------------------------------------------------------------
// 2. Define Maps
// -------------------------------------------------------------------------

// Define HTTP API Endpoints
const api = defineApiMap({
  getTasks: {
    output: Type.Array(TaskSchema),
  },
  createTask: {
    input: Type.Object({
      title: Type.String(),
    }),
    output: TaskSchema,
  },
});

// Define Stream Events
const stream = defineStreamMap({
  generateTask: {
    input: Type.Object({ content: Type.String() }),
    events: {
      chunk: Type.Partial(TaskSchema),
      error: Type.Object({ message: Type.String() }),
      end: Type.Object(TaskSchema),
    },
  },
});

// Define Socket Events
const socket = defineSocketMap({
  taskUpdates: {
    client: {
      subscribe: Type.Object({}),
    },
    server: {
      taskCreated: TaskSchema,
      taskUpdated: TaskSchema,
    },
  },
});

// -------------------------------------------------------------------------
// 3. Create and Export Contract
// -------------------------------------------------------------------------

export const todoListContract = new Contract().api(api).socket(socket);

// Export types for use in frontend and backend
export type TodoListContract = typeof todoListContract;

2. Infer Types

You can infer the static types for use in your application code using the helper types provided (StaticApiMap, StaticSocketMap, etc.).

import { StaticApiMap, StaticSocketMap } from "@feelai/contract";
import { todoListContract, TaskSchema } from "./todoListContract";
import { Static } from "typebox";

// Type for API implementation or usage
export type ApiTypes = StaticApiMap<typeof todoListContract>;

// Type for Socket implementation or usage
export type SocketTypes = StaticSocketMap<typeof todoListContract>;

// Re-export static types from schemas
export type Task = Static<typeof TaskSchema>;

3. Socket Client Usage

The package also includes a Socket client wrapper.

import { Socket } from "@feelai/contract";

// ... usage example needed

API Reference

defineApiMap(map)

Helper to define HTTP API endpoints validation schemas. Inputs and outputs can be any valid TypeBox schema (Object, Array, etc.).

defineStreamMap(map)

Helper to define Stream events validation schemas.

defineSocketMap(map)

Helper to define WebSocket events (client-to-server and server-to-client) validation schemas.

Contract class

The main builder class to compose your definition.

  • .api(apiMap)
  • .stream(streamMap)
  • .socket(socketMap) a