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 🙏

© 2025 – Pkg Stats / Ryan Hefner

fakeserver

v0.3.0

Published

A fake server that runs entirely client-side.

Readme

fakeserver

Introduction

fakeserver is a little framework that lets you implement a web server while you really do not: the fake server runs in the browser and no real server is involved. It does this by replacing XMLHTTPRequest with an object that completely handles your requests on the client.

In addition there is a FakeFetch implementation which can be used to create a simple mock version of the new Fetch API by calling its getFetch method. It does override the browser's fetch implementation at this point, just gives you a fake fetch you can use instead.

fakeserver is built on more-router and mock-xhr.

Usage

  import {FakeServer, Response,
          methodNotAllowedHandler, notFoundHandler} from 'fakeserver';

  // when looking up a handler we do it by using
  // last bit of the URL that wasn't handled
  // by the router (the viewName, set by fakeserver, may also be empty),
  // and by request.method
  let keySpec = [
    {
        name: 'name',
        defaultKey: '',
        extract: request => request.viewName,
        fallback: notFoundHandler
    },
    {
        name: 'method',
        defaultKey: 'GET',
        fallback: methodNotAllowedHandler
    }
  ];

  let fakeserver = new FakeServer(keySpec);

  function handler(variables, request) {
      // construct a Response object with a JSON content-type and 200 OK
      // This is the default: you can pass in the status and response headers
      // as extra arguments to the Response constructor
      return new Response(JSON.stringify({animal: animals.id}));
  }

  // register it for a path, and for GET and empty view name by default
  fakeserver.register('animals/{id}', handler);

  // this is how to handle a PUT request:
  // fakeserver.register('animals/{id}', handler, { method: 'PUT'});

  // override default XMLHTTPRequest
  fakeserver.start();

  // now all XMLHTTPRequests are handled by fakeserver

  // go back to the original XMLHTTPRequest, disable fake server again
  fakeserver.stop();