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

@wellvillage/api-server-mockery

v1.0.0-rc.2

Published

A server used to mock out 3rd party API servers

Readme

@wellvillage/api-server-mockery

last commit badge package.json version badge license badge vulnerabilities badge

This is a simple HTTP server that is concerned with Mocking out an API server. Clients of this component can setup any mock response for a target endpoint through a special endpoint 'POST /mocking', and when the clients send the request to the target endpoint, the mocked response before will be sent back to the client. This can be very helpful in integrating test where an automated test suite is the master of controlling the whole process. The test suite can setup mock response in advance and then trigger the whole solution who may later send requests to the mocked API server.

Installation

You can install this module via NPM with npm install @wellvillage/api-server-mockery.

Contributing

Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.

Configuration

This application's configuration is specified via environment variables. Here is a table of the supported configuration parameters:

| Name | Format | Default Value | | :------------------- | :------------------------------------ | :------------ | | LOGGING_LEVEL | silent, fatal, error, warn, info, debug, trace | info | | LISTENING_PORT | 1025-65534 | 8080 | | MOCK_BASE_URI | Any valid URI | http://localhost:1227 |

Development

This is a Node.JS JavaScript project and as such it relies heavily on the Node.JS ecosystem. Package dependencies are defined via NPM and should be installed before seeking to develop. ESLint and Prettier are used to enforce code styling and best practices, so make sure to utilize them when contributing code changes. Tests are defined with Jest and should be made sure to be kept in sync with any new feature development.

Source code bootstrapping starts in bootstrap.js and should be the first place to look when trying to understand this code base, besides the test modules of course.

Dependencies can be installed by running npm install and tests can be run with npm test.

You can run this application in your development environment by running npm serve from this directory. Make sure to have the configuration environment variables properly set when running it this way.

Building

You can build this application via Docker the normal way or by running npm run image (which builds the image with a fixed tag of api-server-mockery.)