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

@nialloc9/pact-provider

v1.1.4

Published

An abstraction over pact.io's provider tests to hide away any complexities with integrating pact into your pipeline

Downloads

2

Readme

pact-provider

An abstraction over pact.io's provider tests to hide away any complexities with integrating pact into your pipeline.

To help with the buy in from other teams and to get them to integrate contract testing it is important to make it as easy as possible. To do this pact-provider is a reusable abstraction over the provider tests to allow data sources to run just 1 function inside their pipeline to run against our consumer contracts in the broker.

This allows us to update the contract versions without having the data source update their code. Instead we can just ask them to update their version of the package (or have them always install latest).

Usage CLI

$ npm i -g @nialloc9/pact-provider

$ pact-provider --contractName=NameOfContract --pactBrokerUrl=https://MY_BROKER.pact.dius.com.au/ --pactBrokerToken=XXXX

| Parameter | Required | Type | Description | | --------------------------- | :------: | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | applicationUrl | false | string | Running API provider host endpoint. e.g --applicationUrl=XXXX | | contractName | false | string | Name of the provider contract. Overrides global variable PACT_BROKER_CONTRACT_NAME. e.g --contractName=XXXX
| pactBrokerUrl | false | string | URL of the Pact Broker to retrieve pacts from. Required if not using pactUrls. e.g --pactBrokerUrl=XXXX
| contractTags | false | array of strings | Array of tags, used to filter pacts from the Broker. e.g --contractTags={"dev", "prod"} | | pactBrokerToken | false | string | Bearer token for Pact Broker authentication. If using Pactflow, you likely need this option. e.g --pactBrokerToken=XXXX | | publishVerificationResult | false | boolean | Publish verification result to Broker --pactBrokerToken=true | boolean | | contractVersion | false | string | Provider version, required to publish verification results to a broker --contractVersion=XXXX

Usage Progmatically

// my-pact-provider-tests.js
const { onRunPactTests } = require("@nialloc9/pact-provider");

onRunPactTests();


$ PACT_BROKER_CONTRACT_NAME=NameOfContract PACT_BROKER_TOKEN=XXXX PACT_BROKER_URL=https://MY_BROKER.pact.dius.com.au/ mocha -t 10000 my-pact-provider-tests.js

The global variables are required.

Config Progmatically

A config object can also be passed to the pact tests.

// my-pact-provider-tests.js
const { onRunPactTests } = require("@nialloc9/pact-provider");

const config = {};

onRunPactTests(config);

| Parameter | Required | Type | Description | | --------------------------- | :------: | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | applicationUrl | false | string | Running API provider host endpoint. | | contractName | false | string | Name of the provider contract. Overrides global variable PACT_BROKER_CONTRACT_NAME.
| pactBrokerUrl | false | string | URL of the Pact Broker to retrieve pacts from. Required if not using pactUrls. | | contractTags | false | array of strings | Array of tags, used to filter pacts from the Broker. | | pactBrokerToken | false | string | Bearer token for Pact Broker authentication. If using Pactflow, you likely need this option. | | publishVerificationResult | false | boolean | Publish verification result to Broker | boolean | | contractVersion | false | string | Provider version, required to publish verification results to a broker