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

fake-data-repository

v1.0.0

Published

a fake data repository for unit testing

Downloads

14

Readme

fake-data-repository

Provides access to fake data file system repository to help with testing.

Using FakeData Repository

The FakeData Repository class is a useful class for locating a fake response file based on the endpoint you provide.

Example:

const fakeDataRepo = new FakeDataRepository('test/fakedata/data/api')
const fakeDataResponse = fakeDataRepo.responses().get('/v1/Toronto')

The FakeDataRepository constructor takes a base path where it expects to find fake data.

To get fake response data from a GET request the method responses() is first called to tell the object to look in the responses folder, then the method get() is called taking a path as an argument to find the fakedata file. Other supported methods are put(), post(), and delete().

Look at unit tests for more example usages.

examples

| file | resquest | | ------------------------------- | -------------------- | | /index.get.json | GET / | | /any.get.json | GET /:id | | /any.get.specific.json | GET /:id {specific} | | /_search.get.json | GET /search | | /_comments.get.json | GET /comments | | /comments/index.get.json | GET /comments/ | | /comments/any.get.json | GET /comments/:id | | /comments/_search.get.json | GET /comments/search | | /comments/any/index.get.json | GET /comments/:id/ |

example queries

| file | resquest | | ---------------------------------- | ------------------------------- | | /index?name=Superman.get.json | GET /?name=Superman | | /any?name=Batman.get.json | GET /:id?name=Batman | | /any?name=Batman.get.specific.json | GET /:id?name=Batman {specific} |

*Queries must be an exact match /any?name=Batman&villain=Joker.get.json will NOT match GET /:id?name=Batman