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

node-http-mock

v0.5.2

Published

A HTTP mock server for node.js

Downloads

173

Readme

node-http-mock

A HTTP mock server for node.js

Usage

Install it:

npm install node-http-mock -g

And run this command in your termial:

mock -t [api host] -p [local port] -c [config file]

Config File

You can use config file instead of command line options:

// mock.config.js
module.exports = {
  port: 5000,
  verbose: true,
  proxy: {
    target: 'api host',
    changeOrigin: true,
  },
  mock: {
    '/url_a': {},
    '/url_b': {},
  },
}

Run this command to use the config file:

mock -c # default config file mock.config.js
mock -c my.mock.config.js # customize config file

Record & Replay

node-http-mock can construct mock data from real HTTP streams.It identify APIs according to request url, request method and query strings.

[method] [url] ? [query string]

Use -r option to recording these responses as ordinary JSON files in .mock/:

mock -r [directory path]

Press Crtl-C will terminate recording and create index.js tracing the JSON files.After that you can import the index.js into your config file manually:

module.exports = {
  // ...
  mock: require('./.mock/index.js'),
}

Options

Run this command to see a list of all available options:

mock --help

License

MIT © BinRui.Guan