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

@yoyo-org/mockr

v0.4.8

Published

Endpoints are named data holders. Define a URL, attach data, and get a mock API server.

Downloads

155

Readme

mockr

npm

Mock API server for frontend prototyping. Declare a typed mockGroup() builder — it infers each handler's body, req.params, and ctx from one endpoint map — seed an in-memory store for full CRUD, and compose groups across files. Mock the routes you're building, proxy the rest to a real backend with ctx.forward(), or seed a store from the real backend once with .data(url, loader) and mutate it locally. zod body/query validation, per-endpoint scenarios, WebSocket endpoints, and a Chrome extension that records traffic and maps it to local files.

Docs: https://yoyo-67.github.io/mockr/

Install

npm install @yoyo-org/mockr zod

Add "type": "module" to package.json. Run with npx tsx mock.ts — no build step.

Quick example

import { mockr, mockGroup } from '@yoyo-org/mockr';
import { z } from 'zod';

type Todo = { id: number; title: string; done: boolean };
type Endpoints = {
  '/api/todos': Todo[];
  '/api/todos/:id': Todo;
};

const todos = mockGroup<Endpoints>()
  .data('/api/todos', [{ id: 1, title: 'Buy milk', done: false }])
  .post('/api/todos', {
    body: z.object({ title: z.string() }),
    fn: (req, ctx) => {
      ctx.endpoint('/api/todos').insert({ id: Date.now(), title: req.body.title, done: false });
      return ctx.endpoint('/api/todos').data;
    },
  })
  .patch('/api/todos/:id', {
    body: z.object({ done: z.boolean() }),
    fn: (req, ctx) => ctx.endpoint('/api/todos').update(Number(req.params.id), req.body),
  })
  .done();

await mockr({ port: 4000, groups: [todos] });

GET /api/todos returns the array, POST inserts, PATCH updates, DELETE removes — no glue code.

The old handler() / endpoints() functions are deprecated in favor of mockGroup() — see MIGRATION.md.

Where to next

  • Concepts — the data-driven mental model
  • Tutorial — eleven chapters, each a runnable example
  • Reference — full API surface (handlers, WebSocket, recorder, CLI)
  • Examples — copy-pasteable working servers

License

MIT