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 🙏

© 2025 – Pkg Stats / Ryan Hefner

nanowizz-flightsearch-jest-example

v1.0.0

Published

NanoWizz FlightSearch Pact example using Jest

Readme

NanoWizz FlightSearch Pact example project using Jest

This example is a really simple demonstration of the use of Pact in Jest tests.

Places where you need to make changes are marked with TODO comments

To run the tests:

npm install
npm test

The important files in this project:

nanowizz-flightsearch.js - This is the consumer code that will access your provider. You should replace this with your actual consumer code.

__tests__/nanowizz-flightsearch.spec.js - This is the Pact consumer test that invokes the consumer code.

Comments about Jest

To avoid race conditions if you have multiple pact specs, we recommend running Jest 'in band'. If you are running a large unit test suite you may want to run that separately as a result to take advantage of the concurrency of jest (although this is not always faster). To achieve this you can get your pact tests to have a suffix of '.pact.js' and add the following Jest argument to your pact task in npm:

--testRegex \"/*(.test.pact.js)\""

This example uses jest-pact

Publishing the pact file

Running the tests ( if they pass ;-) ) will generate a pact file pacts/nanowizz_flightsearch-acl.json. You can publish this to your broker by running npm run test:publish.

Generally, you would do this from your CI server.

REMEMBER to set the PACTFLOW_TOKEN environment variable with a valid token before running this!

The script in test/publish.js needs to be updated to set the correct version and branch environment variables for your CI system.