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

generate-nocks-from-requests

v0.1.0

Published

Automatically generate Nock mocks from requests made with Request

Downloads

3

Readme

Generate Nocks from Requests – 0.1.0

Automatically generate Nock mocks from requests made with Request.

Usage

First, let's install it. Since you normally don't want GNFR (too lazy to type "Generate Nocks from Requests"[^1]) installed permanently, we'll install it like this:

npm i generate-nocks-from-requests

Now lets hook it up:

/* ... code */
const request = require('request')
require('generate-nocks-from-requests')(request)
/* ... more code */

Now run you're thing and trigger the requests you want to mock. After you'll probably need to kill the process. Now there should be a mock.js file in the directory you ran the server from. It contains you're nock mocks 🎉.

API

default (Request, Options) => Flush

The default export is a function taking a Request object and Options as a parameter and returns the Flush function.

Options object

The default arguments are as follows:

{
  repeat = 999,
  delay = 200,
  output = 'mocks.js',
  flushOnExit = true
}
  • repeat: Controls the argument that is passed to Nocks #times().
  • delay: Controls the argument passed to Nocks #delay().
  • output: The file to save the mocks to.
  • flushOnExit: Wether or not to flush when the process exits. (see Flush)

Flush () => void

Writes all the buffered mocks to the file defined in options.output. The Flush function is called automatically when the process exits regularly, or it receives one of this signals SIGTERM, SIGHUP, 'SIGBREAK'. To disable this behaviour, set flushOnExit: false.

[^1]: Yes, I did not type it again, but just copy-pasted it over from the header.