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

reverse-service

v0.1.0

Published

Downstream interceptor to fake calls

Downloads

4

Readme

Dependencies Faker

Useful to mock responses or perform reverse engineering of REST services. Powered by express.

const { Server, Handler, responseRandomizer } = require('reverse-service');

// initialize a server in port 3000
const testServer = new Server(3000);

// listen for errors
testServer.on('error', (err) => {
	console.error(err);
});

// listen for unknown calls
testServer.on('unhandled_endpoint', endpoint => {
	console.log(`Unhandled: ${JSON.stringify(endpoint)}`);
});

testServer.on('ready', () => {
	console.log('fake server is up and running');
});

testServer.setHandlers(app => {
	// create a response handler, passing what is consider a 'valid payload'
	const somethingHandler = createHandler({ hello: 'world' });

	// set handlers for known endpoints, the express way
	app.get('/something', (_, res) => {
		
		// from the handler, allow a 30% of random errors (i.e. different payload, timeouts, etc)
		const { caseName, handler } = responseRandomizer(somethingHandler, .3);
		
		// printing the selected case from the randomizer
		console.log(`/something ${caseName}`);

		// execute the handler
		handler().then(r => {
			res.send(r); // if is a valid response return it
		}).catch(e => {
			res.status(500).send(e); // if the handler fails, return an error
		});
	});
});

testServer.start();

Included handler responses

  • Bad payload: Returns a simple string (bad_payload)
  • Empty: Returns nothing
  • Null: Returns null
  • Slow: Returns a response in 100ms
  • Error: Plain promise rejection with the text err
  • Timeout: Returns a response in 1s
  • Valid: Returns the valid payload as defined in the first argument of the createHandler function