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 🙏

© 2024 – Pkg Stats / Ryan Hefner

express-fixturer

v0.1.0

Published

Easily manage your API fixtures

Downloads

22

Readme

Express-fixturer

Express middleware that save the response payload (fixtures) of each http request against a hash and reply with those fixtures when you turn it into fixture mode.

The name of the file is the hash created from the request so you get the right mocked data for each of your request.

It should help you mocking endpoints so you don't have to bother updating fixtures.

How to get started

Install the middleware:

npm install express-fixturer

Plug it to express:

const app = express();
app.use(expressFixturer({ fixtureBasePath: './fixtures' }));

API

middlewareFactory

Description

Create a unique hash for each http request and use this hash as a filename to save the response payload.

How to import:

import middlewareFactory from 'express-fixturer';

Parameters of the factory function:

  • saveRoutes (optional, default: true) boolean | string[]: If true, it will create fixtures for each of your express endpoints. You can also pass an array of routes and it will only create fixtures for those routes.
  • fixtureRoutes (optional, default: false) boolean | string[]: If true, it will use the fixtures if it find them or will trigger your handler and save the response payload as a fixture.
  • fixtureBasePath (optional, default: ./) string: Define the path to the folder of your fixtures.
  • hashFn (optional) (req: express.Request) => object: Define how to generate your hash used to identify the fixture to the right request. The default hash function will include req.body, req.cookies, req.params, req.query and req.path
  • logging (optional, default: verbose) verbose | quiet: If set to verbose it will log.

Example

This will save fixtures to the fixtures folder.

const app = express();
app.use(expressFixturer({ fixtureBasePath: './fixtures' }));

TODO

  • Implement string[] routes to save fixtures or not
  • Implement string[] for using fixtures or not
  • Handle nested folder structure for fixtureBasePath