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

@bonjourjohn/fixture-manager

v1.0.1

Published

Simple class allowing to manage fixture easily

Downloads

12

Readme

FIXTURE MANAGER

Purpose

This module provides a Fixture Loader class designed to manage fixtures easily: backuping collections, loading fixtures, restoring data.

Quick start

const MongoClient = require('mongodb').MongoClient;
const Mclient = new MongoClient(SERVER, OPTIONS).connect();
const MDB = Mclient.db(DBNAME);

const fixtureLoaderClass = require('@bonjourjohn/fixture-manager');
const fixtureLoader = new fixtureLoaderClass(MDB);

//load fixtures, execute before test script
await fixtureLoader.load(__dirname + '/fixtures/', ["bikers", "old_ladies"]);

//access objects in loader
fixtureLoader.get("foo", 0); //get the first foo object in list
fixtureLoader.get("bar"); //get the while bar list

//restore, execute after test script
await fixtureLoader.restore();

Usage

Fixtures files

Your fixtures must be stored in files following this structure:

'use strict';

let ObjectId = require('mongodb').ObjectId; //only if you need to set id and access it from your tests

_structure:_
module.exports = {
  "collection": "bikers",
  "objects": [
    {
      "_id": ObjectId(),
      "field1": "Jackson",
      "field2": "Teller",
      ...
    },
    ...
  ]
}

example file: bikers.js

'use strict';

let ObjectId = require('mongodb').ObjectId; //only if you need to set id and access it from your tests


module.exports = {
  "collection": "bikers",
  "objects": [
    {
      "_id": ObjectId(),
      "firstname": "Jackson",
      "lastname": "Teller",
      "email": "[email protected]"
    },
    {
      "_id": ObjectId(),
      "firstname": "Clay",
      "lastname": "Morrow",
      "email": "[email protected]"
    }
  ]
}

example file: old_ladies.js

'use strict';

let ObjectId = require('mongodb').ObjectId; //only if you need to set id and access it from your tests


module.exports = {
  "collection": "wives",
  "objects": [
    {
      "_id": ObjectId(),
      "firstname": "Tara",
      "lastname": "Knowles",
      "email": "[email protected]"
    },
    {
      "_id": ObjectId(),
      "firstname": "Gemma",
      "lastname": "Morrow",
      "email": "[email protected]"
    }
  ]
}

Testing

Requirements

You need a MongoDB and a Redis server running.

My choice is to use Docker to easy things. I recommend these images:

docker run --name database -p 27017:27017 -d mongo
docker run --name cache -p 6379:6379 -d redis:3.0.6-32bit

If you already have a MongoDB server and a Redis server running localy then you don't need anything from Docker and you can ignore the instructions above.

Once everything is running, just run the tests:

npm test