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

icedfrisby-nock

v2.1.0

Published

Concise support for mock requests in IcedFrisby

Downloads

4,194

Readme

icedfrisby-nock

version license build coverage code style

Concise support for mock requests in IcedFrisby.

Usage

Compose icedfrisby with icedfrisby-nock.

const frisby = require('icedfrisby-nock')(require('icedfrisby'))

or, more semantically, using the delightful mixwith:

const { mix } = require('mixwith')

const frisby = mix(require('icedfrisby')).with(require('./icedfrisby-nock'))

Allow connections to localhost, but simulate failure for any other HTTP connections.

await frisby.create(...)
  .get(...)
  .networkOff()
  .expectJSON(...)
  .run()

Mock one request, and simulate failure for any other HTTP connection.

intercept() automatically invokes networkOff().

await frisby.create(...)
  .get(...)
  .intercept(nock => nock('http://example.com')
    .get('/foobar')
    .reply(200))
  .expectJSON(...)
  .run()

Mock one request and allow all other HTTP connections.

await frisby.create(...)
  .get(...)
  .intercept(nock => nock('http://example.com')
    .get('/foobar')
    .reply(200))
  .networkOn()
  .expectJSON(...)
  .run()

Mock one request only if a condition is truthy.

const someCondition = true
await frisby.create(...)
  .get(...)
  .interceptIf(someCondition, nock => nock('http://example.com')
    .get('/foobar')
    .reply(200))
  .expectJSON(...)
  .run()

When using intercept(), interceptIf() or networkOff(), the plugin restores network access when the test finishes.

To check if a Frisby object has an intercept set, inspect the hasIntercept property.

To skip the test if an intercept is present, invoke .skipIfIntercepted() on the chain. This is useful with when invoked from a shared setup function or when performing conditional intercepts.

For the Nock API, refer to the Nock docs.

For the IcedFrisby API, refer to the IcedFrisby docs.

Installation

npm install --save-dev icedfrisby nock icedfrisby-nock

Who's using this

This project was developed for testing Shields.io.

Contribute

  • Issue Tracker: https://github.com/paulmelnikow/icedfrisby-nock/issues
  • Source Code: https://github.com/paulmelnikow/icedfrisby-nock

Pull requests welcome!

Support

If you are having issues, please let me know.

License

The project is licensed under the MIT license.