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

mocky

v0.1.11

Published

http mocking server with simple config written on nodejs

Downloads

2,425

Readme

mocky

mocky - http mocking server with simple config written on nodejs

Build Status

Installation

npm install mocky

Examples

Create new mock.js file with content

var mocky = require('mocky');

mocky.createServer([{
// simple GET route without request body to match
	url: '/someurl1?a=b&c=d',
	method: 'get',
	res: 'response for GET request'
}, {
// POST route with request body to match and respose with status, headers and body
	url: '/someurl2?a=b&c=d',
	method: 'post',
	req: 'POST request body to match',
	res: {
		status: 202,
		headers: {'Content-type': 'text/html'},
		body: '<div>response to return to client</div>'
	}
}, {
// PUT route with dynamic response body
	url: '/someurl3?a=b&c=d',
	method: 'put',
	req: 'PUT request body to match',
	res: function(req, res) {
		return 'PUT response body';
	}
}, {
// GET route with regexp url and async response with status, headers and body
	url: /\/someurl4\?a=\d+/,
	method: 'get',
	res: function(req, res, callback) {
		setTimeout(function() {
			callback(null, {
				status: 202,
				headers: {'Content-type': 'text/plain'},
				body: 'async response body'
			});
		}, 1000);
	}
}]).listen(4321);

That's all now you can run mock server node mock.js, after that if you send GET request to http://127.0.0.1:4321/someurl1?a=b&c=d and get response for GET request to the client, send POST request to http://127.0.0.1:4321/someurl?a=b&c=d with body POST request body to match ... and so on, just try it.

Requests recording

It's very handy to auto record requests, do it somewhere at start of your main app file

mocky.recorder.start({print: true});

After that all http/https requests will be logged into console immediately after execution.

You also can manually control recorder - start recorder then after some requests occures you can manually process recorder outputs e.g.

console.log(mocky.recorder.outputs)

You also can stop recorder and clear outputs.

mocky.recorder.stop();
mocky.recorder.clean();

Running test

Into cloned repository run

npm test

TODO

  • improve server logging
  • support request headers matching