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

fixture-middleware

v1.0.1

Published

Use fixture data in your express app!

Downloads

3

Readme

fixture-middleware — Use fixture data in your express app!

Motivation

Sometimes I want to mock certain paths of my API made with Express. Therefore, I created fixture-middleware which will use fixture data (mock) for any URL that matches a file inside the configured fixture directory.

Installation

npm install fixture-middleware --save-dev
yarn add fixture-middleware --dev

Usage

const path = require('path')
const express = require('express')
const fixtureMiddleware = require('fixture-middleware')

const app = express()
const fixtureDirectory = path.resolve(__dirname, './fixtures')

app.use(fixtureMiddleware(fixtureDirectory))

Matching URLs with fixture files

All URLs are normalized (all / will be replaced by --) and if a Accept headers is present it will be used to determine the file extension, otherwise the first matching file will be returned.

Example

Suppose we have the following files in the configured fixture directory:

`-- fixtures
    |-- users.json
    |-- users.html
    `-- users--active.json

The following request will match those files as follows

| Request | Response | --- | --- | URL: /users Headers: (no accept header) | File: users.html | URL: /users Headers: accept=application.json | File: users.json | URL: /users Headers: accept=application.html | File: users.html | URL: /users/active Headers: (no accept header) | File: users--active.json | URL: /users/active Headers: accept=application.json | File: users--active.json

Important: Any unmatched request will be delegated to the next middleware.

Development

  1. Clone and fork this repo.
  2. Install dependencies: yarn or npm install.
  3. Run tests.
  4. Prepare a pull request.

Test

  • yarn test – to run all tests.
  • yarn test -- --watch – to run all tests in watch mode.

Publish

  1. Bump package version: yarn version --new-version x.x.x -m 'Version %s.'.
  2. Publish to NPM registry: npm publish.
  3. Push new tag: git push origin --tags.

Made with :heart: by Rubens Mariuzzo.

MIT license