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

nock-nock

v0.0.1

Published

A simple record and replay `nock` helper

Downloads

13

Readme

nock nock

A simple record and replay nock helper.

Example Usage

const assert = require('chai').assert;
const nocknock = require('.');

describe('Some test area', () => {

  let recorder = null;
  afterEach((done) => {
    if(recorder) {
      recorder.after(done);
    }
    else {
      done();
    }
  });

  it('should handle login failure', (done) => {
    recorder = nocknock('failed_login');
    recorder.before();

    authenticate({token: 'abc123'}, (err, returnedData) => {
      assert.equal(returnedData.type, 'error');
      assert.equal(returnedData.message, 'Invalid token');
      done();
    });
  });
});

When the above code is run and there's not yet a failed_login.js fixture saved in (by default) test/fixtures, then nock will be used to record the results of a live call to whatever service the login() function under test calls.

The resulting fixture file in test/fixtures/failed_login.js might look like this:

var nock = require('nock');

nock('https://example.com:443', {"encodedQueryParams":true})
  .post('/rest/api/v13/auth', "token=abc123")
  .reply(400, {"type":"error","message":"Invalid token","errorCode":"82"}, [ 'Max-Forwards',
  '20',
  'Via',
  '1.0 oag02-example.com ()',
  'Connection',
  'close',
  'X-CorrelationID',
  'Id-ff565c5c9a9ba52b627183f4 0',
  'Date',
  'Thu, 07 Feb 2019 16:04:15 GMT',
  'Server',
  'Apache',
  'X-Frame-Options',
  'SAMEORIGIN',
  'Content-Type',
  'application/json;charset=UTF-8' ]);

Once the fixture file exists, the next run of that test will use that nock data, with no actual call being made to the external service.

Those fixture files can then be easily modified, or duplicated to mock different endpoint behaviors. Multiple nock() calls can be included in a single fixture (e.g., if another test in this example used a successful authentication, followed by another API call).

To re-record an existing fixture, either delete the fixture file(s), or set the environment variable NOCK_RECORD to "true".