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

pact-js-provider

v1.1.5

Published

A JS implementation of Provider Pact

Downloads

4

Readme

Node Provider for Pact

Matches pact for Providers. See Pacts for more information on Pact.

Setup

Requirements

  • You will need Ruby 2+. You can install this via ruby-install, rvm or chruby.
  • bundler
  • node (tested on version 4.2.1)
  • npm

Install bundler with:

gem install bundler
bundle --version

Should print something like:

Bundler version 1.11.2

Any project using Pact will then on preinstall run 'bundle install' to install the ruby dependencies.

Using pact-js-provider

See test repo

provider_states_for('Animal Service', 'Zoo App', './pacts/zoo_app-animal_service.json', 'http://localhost:5000', (done) => {
  providerState('there is an alligator named Mary', (done) => {
    setUp( (done) => {
      switchMary(true, done)
    })

    it( () => {})

    tearDown( (done) => {
      done()
    })
  })
)}

Pact-js-provider uses mocha under the hood. As a result currently to run the test you need an it method. The provider_states_for method needs the following parameters:

  • provider name
  • consumer name
  • pact file
  • base url

The providerState requires the name of the providerState to be tested. Currently this will just output the content from the ruby implementation. There is no error code returned on failure.

Links

Pacts - ruby reference implementation

[Pacts js consumer] (https://github.com/DiUS/pact-consumer-js-dsl)

Simplifying microservices testing with pacts - Ron Holshausen (one of the original pact authors)

Pact specification

Integrated tests are a scam - J.B. Rainsberger

Consumer Driven Contracts - Ian Robinson

Integration Contract Tests - Martin Fowler

Roadmap

See ROADMAP.md.

Contributing

See CONTRIBUTING.md.