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

@contract-kit/server

v1.0.0

Published

Framework-agnostic HTTP server runtime for contract-kit - extracted from @contract-kit/app

Readme

@contract-kit/server

Framework-agnostic HTTP server runtime for Contract Kit.

Use this package when you are building a server adapter or running Contract Kit outside a framework-specific package. For Next.js apps, prefer @contract-kit/next.

Install

bun add @contract-kit/server @contract-kit/core @contract-kit/ports

Minimal setup

import { createServer, defineRoutes } from "@contract-kit/server";
import { definePorts } from "@contract-kit/ports";
import { getTodo } from "@/contracts/todos";

const ports = definePorts({});

export const server = await createServer({
  ports,
  createContext: ({ ports }) => ({
    requestId: crypto.randomUUID(),
    ports,
  }),
  routes: defineRoutes([
    {
      contract: getTodo,
      handle: async ({ path }) => ({
        status: 200,
        body: { id: path.id, title: "Example", completed: false },
      }),
    },
  ]),
});

createServer(...) returns a framework-agnostic server instance. Framework adapters convert their native request/response objects into Contract Kit's HttpRequestLike and HttpResponse shapes.

Core exports

| Export | Purpose | | --- | --- | | createServer(options) | Create a framework-agnostic Contract Kit server | | defineRoutes(routes) | Preserve route handler inference for route arrays | | createHealthContract(options?) | Define a standard health endpoint contract | | createHealthRoute(contract, handler?) | Create a standard health route | | createOpenAPIContract(options?) | Define a standard OpenAPI endpoint contract | | createRateLimitHooks(options?) | Enforce contract metadata-driven rate limits | | createRequestLoggerHook(options?) | Add request logging around handlers | | HttpRequestLike | Adapter-facing request interface | | HttpResponse | Adapter-facing response shape | | RouteDef | Route registration type | | ServerInstance | Created server instance type |

Request lifecycle

The runtime owns route matching, request parsing, request validation, context creation, hook execution, handler execution, response validation, and error mapping. Route handlers should return { status, body, headers? } or a native Response when the adapter supports it.

Providers

Servers can install Contract Kit providers during startup:

export const server = await createServer({
  ports,
  providers: [loggerPinoProvider, redisProvider],
  createContext: ({ ports }) => ({ ports }),
  routes,
});

Provider-installed ports are available to later providers, createContext, hooks, handlers, use cases, and server.ports.

Error handling

Declared AppError instances are mapped to Contract Kit's standard error envelope. Unknown failures are passed to mapUnhandledError when provided. Use onCaughtError hooks for logging, tracing, and metrics without changing response behavior.

Read next

  • Docs site server guide: https://contract-kit.dev/server
  • Request lifecycle: https://contract-kit.dev/request-lifecycle
  • Hooks: https://contract-kit.dev/hooks
  • Providers: https://contract-kit.dev/providers

License

MIT