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

@nielsen-oss/pact-manifest

v1.0.0

Published

Pact Manifest is a Node.js library to publish pact contracts to a broker using a manifest

Downloads

3

Readme

Pact Manifest

Pact Manifest is a Node.js library to publish pact contracts to a broker using a manifest.

Context

Pact is a collection of frameworks that implement the Consumer-Driven Contracts pattern to enable lean testing of API contracts between consumers and providers.

Why

When working in a CI/CD-enabled workflow, the consumer and provider are deploying their artifacts quite often and any dependency on providers's API that isn't ready is hidden behind feature flags, api versioning or other means. This ensures that the consumer can deploy his version without waiting with a long-lived branch for the entire API contract to be implemented by its provider.

How

The library collects the pact contract files and creates or updates a manifest file with the path to the file, and a default tag. With the manifest file ready, the library can be instructed to publish the contracts to a broker based on their tags.

To accompany the manifest file, a suggested workflow is to use a default tag of develop and publish these pacts to the broker. Once the provider implements the contract, it is required on the consumer side to manually edit the manifest file and update the relevant contract file(s) to specify a production flag instead of develop.

Installation

yarn add --dev pact-manifest

Usage

Manifest Manager

const ManifestManager = require('./src/manifestManager')

const manifestManager = new ManifestManager({
  basePath: '/Users/lirantal/projects/forks/myGitProject',
  manifestFile: '/tmp/pact_manifest.json',
  pactFilesPath: 'test/pacts/*.json',
  pactDefaultTag: 'develop'
})

const manifest = await manifestManager.createManifest()

Manifest Publisher

const ManifestPublisher = require('./src/manifestPublisher')

const pactBroker = 'https://test.pact.dius.com.au'
const pactBrokerUsername = 'username'
const pactBrokerPassword = 'password'
const consumerVersion = '1.0.0' // should ideally get this package.json

// Obtain the pacts manifest that ManifestManager creates
// and use the `getManifestsByTag` method to get an object tree
// representation that can be easily iterated to publish the pacts
const manifestByTag = manifestManager.getManifestsByTag(manifest)

let publishedPacts = []

// Iterate on each tag and publish the pact files for it to the broker
for (let [tag, pactFiles] of Object.entries(manifest)) {
  const manifestPublisher = new ManifestPublisher({
	pactFiles: pactFiles,
	broker: {
	  pactBroker: pactBroker,
	  pactBrokerUsername: pactBrokerUsername,
	  pactBrokerPassword: pactBrokerPassword
	},
	consumerVersion: consumerVersion,
	tags: [tag]
  })

  publishedPacts.push(manifestPublisher.publish())
}

const res = await Promise.all(publishedPacts)

Related resources

Tests

Project tests:

yarn run test

Project linting:

yarn run lint

Coverage

yarn run test:coverage

Contributing

Commit Guidelines

The project uses the commitizen tool for standardizing changelog style commit messages which you can follow by running yarn run commit instead of just git commit

git add <file1> <file2>
yarn run commit