open-index/open-npm huggingface dataset:
npm package: @pacoyang/phala-sls
Description: Phat Function CLI toolkit
Author: Phala Network
Latest version: 0.1.3-dev.3

# @phala/fn

## Getting Started
```shell
# Starting a new project from a template
# Choose template `lensapi-oracle-consumer-contract`
npx @phala/fn init <your project name>

# Install dependencies
cd <your project name>
yarn install

# Compile JS code
npx @phala/fn build src/index.ts

# Test your JS code
npx @phala/fn run dist/index.js
# Test your JS code with multiple arguments
npx @phala/fn run dist/index.js -a 1 2 3

# Start a local hardhat node
yarn hardhat node

# Run the e2e test
yarn hardhat test --network localhost

# Deploy and get the contract address
yarn localhost-deploy

# Start a watching server
yarn localhost-watch <your deployed contract address> artifacts/contracts/TestLensApiConsumerContract.sol/TestLensApiConsumerContract.json dist/index.js -a https://api-mumbai.lens.dev/

# Push a request
LOCALHOST_CONSUMER_CONTRACT_ADDRESS=<your deployed contract address> yarn localhost-push-request
```
npm package: @pacoyang/taro-ui
Description: UI KIT for Taro
Author: O2Team
Latest version: 2.2.1-dev.3

# Taro UI

[![NPM][npm-version-image]][npm-version-url] [![david-dm][david-dm-image]][david-dm-url]

一款基于 `Taro` 框架开发的多端 UI 组件库

## 特性

- 基于 `Taro` 开发 UI 组件
- 一套组件可以在 `微信小程序`，`支付宝小程序`，`百度小程序`，`H5` 多端适配运行（`ReactNative` 端暂不支持）
- 提供友好的 API，可灵活的使用组件

## 关于 Taro

Taro 是由 [凹凸实验室](https://aotu.io) 倾力打造的多端开发解决方案。现如今市面上端的形态多种多样，Web、ReactNative、微信小程序等各种端大行其道，当业务要求同时在不同的端都要求有所表现的时候，针对不同的端去编写多套代码的成本显然非常高，这时候只编写一套代码就能够适配到多端的能力就显得极为需要。

使用 Taro，我们可以只书写一套代码，再通过 Taro 的编译工具，将源代码分别编译出可以在不同端（微信小程序、H5、RN等）运行的代码。

## 体验

请使用微信扫一扫以下体验码

![QRCode](https://user-images.githubusercontent.com/1240899/46650700-25a4e600-cbd0-11e8-90ff-905edb39c340.jpg)

## 相关链接

- [Taro UI 使用文档](https://taro-ui.aotu.io)
- [Taro UI 官方示例](https://github.com/NervJS/taro-ui-demo)
- [Taro](https://taro.aotu.io/)

## 安装

需要安装 `Taro` 开发工具 `@tarojs/cli`，`Taro` 版本需要在 `1.0.0-beta.18` 以上

```bash
npm install -g @tarojs/cli
```

然后在项目中安装 Taro UI

```bash
npm install taro-ui
```

## 使用

在代码中 `import` 需要的组件并按照文档说明使用

```js
import { AtButton } from 'taro-ui'
```

## 开发交流

[官方微信交流群](https://github.com/NervJS/taro-ui/issues/16)

## 开发计划

[开发计划](./PLANS.md)

## 贡献

如果你在使用 `Taro UI` 时遇到问题，或者有好的建议，欢迎给我们提 `Issue` 或 `Pull Request`。在开始之前，请阅读 [贡献指南](https://github.com/NervJS/taro-ui/blob/master/.github/CONTRIBUTING.md)

## License

MIT


[npm-version-image]: https://img.shields.io/npm/v/taro-ui.svg?style=flat-square
[npm-version-url]: https://www.npmjs.com/package/taro-ui
[david-dm-image]: https://david-dm.org/NervJS/taro-ui.svg?style=flat-square
[david-dm-url]: https://david-dm.org/NervJS/taro-ui
npm package: @pacphi/sindri-cli
Description: Sindri CLI — declarative cloud development environment manager
Latest version: 3.1.3

# @pacphi/sindri-cli

The Sindri CLI distributed as an npm package.

## Installation

```bash
npm install -g @pacphi/sindri-cli
# or
pnpm add -g @pacphi/sindri-cli
```

## Usage

```bash
sindri --help
sindri extension list --all --json
sindri profile list --json
sindri version --json
```

## How it works

This package uses the **optionalDependencies + platform packages** pattern (same as
[esbuild](https://esbuild.github.io), [Biome](https://biomejs.dev), and [SWC](https://swc.rs)).

On install, npm/pnpm selects only the platform-specific binary package that matches your OS and
CPU. The wrapper `lib/index.js` resolves the correct binary path and delegates all CLI arguments
to it.

### Supported platforms

| Platform            | Package                           |
| ------------------- | --------------------------------- |
| macOS Apple Silicon | `@pacphi/sindri-cli-darwin-arm64` |
| macOS Intel         | `@pacphi/sindri-cli-darwin-x64`   |
| Linux x64           | `@pacphi/sindri-cli-linux-x64`    |
| Linux arm64         | `@pacphi/sindri-cli-linux-arm64`  |
| Windows x64         | `@pacphi/sindri-cli-win32-x64`    |

## Programmatic usage

```javascript
const { getInstalledBinaryPath } = require("@pacphi/sindri-cli");
const bin = getInstalledBinaryPath();
// bin = "/path/to/node_modules/@pacphi/sindri-cli-linux-x64/sindri"
```

## Environment variables

| Variable               | Description                                      |
| ---------------------- | ------------------------------------------------ |
| `SINDRI_BIN_PATH`      | Override the binary path entirely                |
| `SINDRI_SKIP_DOWNLOAD` | Set to `1` to skip postinstall download fallback |

## Version alignment

The npm package version is always identical to the Rust binary version (`Cargo.toml`
is the single source of truth). Releases are automated via
[cargo-dist](https://opensource.axo.dev/cargo-dist/) on `git tag v3.x.y`.
npm package: @pacprotocol/pacprotocoljs-p2p
Description: Interface to the dash P2P network for PAC Protocol
Author: PAC Global Holdings LLC.
Latest version: 1.0.0

PAC Protocol P2P
=======

[![NPM Package](https://img.shields.io/npm/v/@pacprotocol/pacprotocoljs-p2p.svg?style=flat-square)](https://www.npmjs.org/package/@pacprotocol/pacprotocoljs-p2p)
[![Build Status](https://github.com/pacprotocol/pacprotocoljs-p2p/actions/workflows/test_and_release.yml/badge.svg)](https://github.com/pacprotocol/pacprotocoljs-p2p/actions/workflows/test_and_release.yml)

`pacprotocoljs-p2p` adds peer to peer PAC Protocol support for `pacprotocoljs`.

See [the main pacprotocoljs repo](https://github.com/pacprotocol/pacprotocoljs) for more information.

## Getting Started

```sh
npm install @pacprotocol/pacprotocoljs-p2p
```
In order to connect to the Dash network, you'll need to know the IP address of at least one node of the network, or use [Pool](/docs/pool.md) to discover peers using a DNS seed.

```javascript
var Peer = require('@pacprotocol/pacprotocoljs-p2p').Peer;

var peer = new Peer({host: '127.0.0.1'});

peer.on('ready', function() {
  // peer info
  console.log(peer.version, peer.subversion, peer.bestHeight);
});
peer.on('disconnect', function() {
  console.log('connection closed');
});
peer.connect();
```

Then, you can get information from other peers by using:

```javascript
// handle events
peer.on('inv', function(message) {
  // message.inventory[]
});
peer.on('tx', function(message) {
  // message.transaction
});
```

Take a look at the [bitcore guide](http://bitcore.io/guide/peer.html) on the usage of the `Peer` class.

## Contributing

Please send pull requests for bug fixes, code optimization, and ideas for improvement. For more information on how to contribute, please refer to our [CONTRIBUTING](https://github.com/pacprotocol/pacprotocoljs-p2p/blob/master/CONTRIBUTING.md) file.

## License

Code released under [the MIT license](https://github.com/pacprotocol/dashcore/blob/master/LICENSE).

Copyright 2013-2017 BitPay, Inc. Bitcore is a trademark maintained by BitPay, Inc.  
Copyright 2016-2017 The Dash Foundation, Inc.  
Copyright 2017-2018 Dash Core Group, Inc. 
Copyright 2018-2021 PAC Global Holdings LLC.
npm package: @pact-foundation/pact-cli
Description: Broker CLI for @pact-foundation/pact
Author: Timothy Jones
Latest version: 18.0.0

# Pact CLI

<!-- TOC -->

- [Pact CLI](#pact-cli)
  - [Pact CLI Tools](#pact-cli-tools)
  - [Installation](#installation)
    - [Do Not Track](#do-not-track)
  - [Which Library/Package should I use?](#which-librarypackage-should-i-use)
  - [Contributing](#contributing)
  - [Testing](#testing)
  - [Questions?](#questions)

<!-- /TOC -->

## Pact CLI Tools

This package wraps the [Pact CLI Tools](https://github.com/pact-foundation/pact-cli/releases) so that they are available to node scripts in package.json, and linked binaries in the [standard](https://docs.npmjs.com/files/folders#executables) NPM installation directory (e..g. `./node_modules/.bin`).

For example:

```
"scripts": {
  "pactPublish": "pact-broker publish ./pacts --consumer-app-version=$\(git describe\) --broker-base-url=$BROKER_BASE_URL --broker-username=$BROKER_USERNAME --broker-password=BROKER_PASSWORD"`
}
```

Or:

```
 
```sh
# Example can-i-deploy check
./node_modules/.bin/pact-broker can-i-deploy --pacticipant "Banana Service" --broker-base-url https://test.pact.dius.com.au --latest --broker-username dXfltyFMgNOFZAxr8io9wJ37iUpY42M --broker-password O5AIZWxelWbLvqMd8PkAVycBJh2Psyg1

Computer says no ¯\_(ツ)_/¯

CONSUMER       | C.VERSION | PROVIDER       | P.VERSION | SUCCESS?
---------------|-----------|----------------|-----------|---------
Banana Service | 1.0.0     | Fofana Service | 1.0.0     | false

The verification between the latest version of Banana Service (1.0.0) and version 1.0.0 of Fofana Service failed
```

The following are the binaries currently made available:

- `pact` (top level cli)
- `pact-broker`
- `pact-mock-server`
- `pact-verifier`
- `pact-stub-server`
- `pact-plugin`
- `pactflow`

## Installation

`npm install @pact-foundation/pact-cli --save-dev`

### Do Not Track

In order to get better statistics as to who is using Pact, we have an anonymous tracking event that triggers when Pact installs for the first time. To respect your privacy, anyone can turn it off by simply adding a 'PACT_DO_NOT_TRACK' environment variable in their shell

## Which Library/Package should I use?

`pact-js` for core contract testing functionality
`pact-cli` for broker client, stub and verifier standalone tools

## Contributing

To develop this project, simply install the dependencies with `npm install --ignore-scripts`, and run `npm run watch` to for continual development, linting and testing when a source file changes.

## Testing

Running `npm test` will execute the tests that has the `*.spec.js` pattern.

## Questions?

Please search for potential answers or post question on our [official Pact StackOverflow](https://stackoverflow.com/questions/tagged/pact).
npm package: @pact-foundation/pact-js-prettier-config
Description: Prettier config for developers working on pact-js and related repositories
Author: Timothy Jones
Latest version: 1.0.0

Pact-JS Developer Prettier config
---------------------------------

This is the prettier config for pact-js projects, used to keep consistency across the projects.
Please use these options to format any new pact projects.

It's hosted at
[https://github.com/pact-foundation/pact-js-dev-config](https://github.com/pact-foundation/pact-js-dev-config),
which contains shared config for javascript (and related) pact projects.

It's essentially default prettier settings, with single quotes added.
See this excellent documentation page on prettier's [option
philosophy](https://prettier.io/docs/en/option-philosophy.html).

### How do I use it?

Add this to your package.json:

```
  "prettier": "@pact-foundation/pact-js-prettier-config"
```

Or if you use `.prettierrc.json`: 

```
"@pact-foundation/pact-js-prettier-config"
```

See [here](https://prettier.io/docs/en/configuration.html#sharing-configurations) for details.

### Can I use this to format something that isn't a pact project?

I mean, sure, if you like. We're not the boss of you.
npm package: @pact-foundation/pact-logo
Description: It's the logo, duh
Author: Michel Boudreau
Latest version: 1.4.1

Pact Logo
------

This is the logo to be used for both Pact (the product) and Pact Foundation (the organisation).  It's better to use it with contrasting colors (black on white or white on black) for maximum impact.  It's recommended that you use the vectorized version of the logo if possible, that is the SVG format or the Pact font, which has the chain link logo on the unicode character U+F000.

![Pact Logo Black](/media/logo-black.png)

![Pact Link Logo Black](/media/link-black.png)

![Pact Foundation Logo Black](/media/foundation-black.png)

![Pact Foundation Compact Logo Black](/media/foundation-compact-black.png)

A CSS file has also been included to easily include the pact logo within HTML.  It is based on the web font available and the css must have the correct path pointing to it.  To use it within HTML, please refer to the following example:

```
<html>
  <head>
    <link href='/media/pact.css' rel='stylesheet' type='text/css'>
  </head>
  <body>
    <h1>Pact Logo</h1>
    <div class="pact pact-logo"></div>
    <div class="pact pact-chain"></div>
  </body>
<html>
```

### Trademark

The Pact Foundation has the right of trademark on its own logo.  Anyone can use the Pact and Pact Foundation logos as long as its use is withing the following guidelines:

**Awesome List**

&#x2713; Use the Pact or Pact Foundation logo to link to Pact

&#x2713; Use the Pact logo to advertise that your product was built with pact

&#x2713; User the Pact Foundation logo to advertise that you contributed to our product

&#x2713; Use the Pact or Pact Foundation logo in a blog post or news article about Pact

**Naughty List**

&times; Use the Pact or Pact Foundation logo for your application’s icon

&times; Create a modified version of the Pact or Pact Foundation logo

&times; Integrate the Pact or Pact Foundation logo into your logo

&times; Use any Pact Foundation's artwork without permission

&times; Sell any Pact Foundation's artwork without permission

&times; Change the colors, dimensions or add your own text/images

###### Please avoid naming your projects anything that implies Pact or Pact Foundation’s endorsement. This also applies to domain names.

#### Please contact us

If there's any question or you're not sure about something, don't hesitate to throw us a line.
npm package: @pact-foundation/pact-mock-service
Description: Pact mock service wrapper package. Installing this will install an executable appropriate for your platform.
Author: Beth Skurrie
Latest version: 2.1.0
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

<img src="https://github.com/pact-foundation/pact-logo/blob/master/media/logo-black.png" width="200">

# Pact Mock Service for NPM

[![Build Status](https://travis-ci.org/pact-foundation/pact-mock-service-npm.svg?branch=master)](https://travis-ci.org/pact-foundation/pact-mock-service-npm)

Installation wrapper for standalone platform-specific executables packaged from the Ruby [pact-mock-service-gem] gem.

On install, this package selects and installs the correct [pact-mock-service-standalone] executable for your environment.

This node module downloads the appropriate platform-specific and installs it alongside `pact-mock-service` inside the node_modules directory.

## Usage

    $ npm i @pact-foundation/pact-mock-service
    $ node_modules/.bin/pact-mock-service --port 1234

[pact-mock-service-standalone]: https://github.com/bethesque/pact-mock_service
npm package: @pact-foundation/pact-mock-service-darwin
Description: Pact mock service
Author: Pact Foundation
Latest version: 2.1.0

<img src="https://github.com/pact-foundation/pact-logo/blob/master/media/logo-black.png" width="200">

# Pact Mock Service for NPM

[![Build Status](https://travis-ci.org/pact-foundation/pact-mock-service-npm.svg?branch=master)](https://travis-ci.org/pact-foundation/pact-mock-service-npm)

Installation wrapper for standalone platform-specific executables packaged from the Ruby [pact-mock-service-gem] gem.

On install, this package selects and installs the correct [pact-mock-service-standalone] executable for your environment.

This node module downloads the appropriate platform-specific and installs it alongside `pact-mock-service` inside the node_modules directory.

## Usage

    $ npm i @pact-foundation/pact-mock-service
    $ node_modules/.bin/pact-mock-service --port 1234

[pact-mock-service-standalone]: https://github.com/bethesque/pact-mock_service
npm package: @pact-foundation/pact-mock-service-linux-ia32
Description: Pact mock service
Author: Pact Foundation
Latest version: 2.1.0

<img src="https://github.com/pact-foundation/pact-logo/blob/master/media/logo-black.png" width="200">

# Pact Mock Service for NPM

[![Build Status](https://travis-ci.org/pact-foundation/pact-mock-service-npm.svg?branch=master)](https://travis-ci.org/pact-foundation/pact-mock-service-npm)

Installation wrapper for standalone platform-specific executables packaged from the Ruby [pact-mock-service-gem] gem.

On install, this package selects and installs the correct [pact-mock-service-standalone] executable for your environment.

This node module downloads the appropriate platform-specific and installs it alongside `pact-mock-service` inside the node_modules directory.

## Usage

    $ npm i @pact-foundation/pact-mock-service
    $ node_modules/.bin/pact-mock-service --port 1234

[pact-mock-service-standalone]: https://github.com/bethesque/pact-mock_service
npm package: @pact-foundation/pact-mock-service-linux-x64
Description: Pact mock service
Author: Pact Foundation
Latest version: 2.1.0

<img src="https://github.com/pact-foundation/pact-logo/blob/master/media/logo-black.png" width="200">

# Pact Mock Service for NPM

[![Build Status](https://travis-ci.org/pact-foundation/pact-mock-service-npm.svg?branch=master)](https://travis-ci.org/pact-foundation/pact-mock-service-npm)

Installation wrapper for standalone platform-specific executables packaged from the Ruby [pact-mock-service-gem] gem.

On install, this package selects and installs the correct [pact-mock-service-standalone] executable for your environment.

This node module downloads the appropriate platform-specific and installs it alongside `pact-mock-service` inside the node_modules directory.

## Usage

    $ npm i @pact-foundation/pact-mock-service
    $ node_modules/.bin/pact-mock-service --port 1234

[pact-mock-service-standalone]: https://github.com/bethesque/pact-mock_service
npm package: @pact-foundation/pact-mock-service-win32
Description: Pact mock service
Author: Pact Foundation
Latest version: 2.1.0

<img src="https://github.com/pact-foundation/pact-logo/blob/master/media/logo-black.png" width="200">

# Pact Mock Service for NPM

[![Build Status](https://travis-ci.org/pact-foundation/pact-mock-service-npm.svg?branch=master)](https://travis-ci.org/pact-foundation/pact-mock-service-npm)

Installation wrapper for standalone platform-specific executables packaged from the Ruby [pact-mock-service-gem] gem.

On install, this package selects and installs the correct [pact-mock-service-standalone] executable for your environment.

This node module downloads the appropriate platform-specific and installs it alongside `pact-mock-service` inside the node_modules directory.

## Usage

    $ npm i @pact-foundation/pact-mock-service
    $ node_modules/.bin/pact-mock-service --port 1234

[pact-mock-service-standalone]: https://github.com/bethesque/pact-mock_service
npm package: @pact-foundation/pact-provider-verifier
Description: Pact provider verifier wrapper package. Installing this will install an executable appropriate for your platform.
Author: Matt Fellows
Latest version: 1.4.3

<img src="https://github.com/pact-foundation/pact-logo/blob/master/media/logo-black.png" width="200">

# Pact Provider Verifier for NPM

[![Build Status](https://travis-ci.org/pact-foundation/pact-provider-verifier-npm.svg?branch=master)](https://travis-ci.org/pact-foundation/pact-provider-verifier-npm)

Installation wrapper for standalone platform-specific executables packaged from the Ruby [pact-provider-verifier](https://github.com/pact-foundation/pact-provider-verifier) gem.

On install, this package selects and installs the correct standalone executable for your environment.

This node module downloads the appropriate platform-specific and installs it alongside `pact-provider-verifier` inside the node_modules directory.

## Usage

```
npm install @pact-foundation/pact-provider-verifier
node_modules/.bin/pact-provider-verifier <options>
```

# Known issues

The packaged binary always prints out the following message on startup. Have not yet traced the source.

```
No entry for terminal type "xterm-256color";
using dumb terminal settings.
```

On npm install, the following warnings will be displayed. They do not appear to affect the behaviour of the provider verifier.

```
npm WARN excluding symbolic link lib/ruby/lib/libcrypto.dylib -> libcrypto.1.0.0.dylib
npm WARN excluding symbolic link lib/ruby/lib/libedit.dylib -> libedit.0.dylib
npm WARN excluding symbolic link lib/ruby/lib/libffi.dylib -> libffi.6.dylib
npm WARN excluding symbolic link lib/ruby/lib/libgmp.dylib -> libgmp.10.dylib
npm WARN excluding symbolic link lib/ruby/lib/liblzma.dylib -> liblzma.5.dylib
npm WARN excluding symbolic link lib/ruby/lib/libncurses.dylib -> libncurses.5.dylib
npm WARN excluding symbolic link lib/ruby/lib/libreadline.dylib -> libedit.0.dylib
npm WARN excluding symbolic link lib/ruby/lib/libssl.dylib -> libssl.1.0.0.dylib
npm WARN excluding symbolic link lib/ruby/lib/libtermcap.dylib -> libncurses.5.dylib
npm WARN excluding symbolic link lib/ruby/lib/libyaml.dylib -> libyaml-0.2.dylib
```
npm package: @pact-foundation/pact-provider-verifier-darwin
Description: Pact provider verifier
Author: Matt Fellows
Latest version: 1.4.3

<img src="https://github.com/pact-foundation/pact-logo/blob/master/media/logo-black.png" width="200">

# Pact Provider Verifier for NPM

[![Build Status](https://travis-ci.org/pact-foundation/pact-provider-verifier-npm.svg?branch=master)](https://travis-ci.org/pact-foundation/pact-provider-verifier-npm)

Installation wrapper for standalone platform-specific executables packaged from the Ruby [pact-provider-verifier](https://github.com/pact-foundation/pact-provider-verifier) gem.

On install, this package selects and installs the correct standalone executable for your environment.

This node module downloads the appropriate platform-specific and installs it alongside `pact-provider-verifier` inside the node_modules directory.

## Usage

```
npm install @pact-foundation/pact-provider-verifier
node_modules/.bin/pact-provider-verifier <options>
```

# Known issues

The packaged binary always prints out the following message on startup. Have not yet traced the source.

```
No entry for terminal type "xterm-256color";
using dumb terminal settings.
```

On npm install, the following warnings will be displayed. They do not appear to affect the behaviour of the provider verifier.

```
npm WARN excluding symbolic link lib/ruby/lib/libcrypto.dylib -> libcrypto.1.0.0.dylib
npm WARN excluding symbolic link lib/ruby/lib/libedit.dylib -> libedit.0.dylib
npm WARN excluding symbolic link lib/ruby/lib/libffi.dylib -> libffi.6.dylib
npm WARN excluding symbolic link lib/ruby/lib/libgmp.dylib -> libgmp.10.dylib
npm WARN excluding symbolic link lib/ruby/lib/liblzma.dylib -> liblzma.5.dylib
npm WARN excluding symbolic link lib/ruby/lib/libncurses.dylib -> libncurses.5.dylib
npm WARN excluding symbolic link lib/ruby/lib/libreadline.dylib -> libedit.0.dylib
npm WARN excluding symbolic link lib/ruby/lib/libssl.dylib -> libssl.1.0.0.dylib
npm WARN excluding symbolic link lib/ruby/lib/libtermcap.dylib -> libncurses.5.dylib
npm WARN excluding symbolic link lib/ruby/lib/libyaml.dylib -> libyaml-0.2.dylib
```
npm package: @pact-foundation/pact-provider-verifier-linux-ia32
Description: Pact provider verifier
Author: Matt Fellows
Latest version: 1.4.3

<img src="https://github.com/pact-foundation/pact-logo/blob/master/media/logo-black.png" width="200">

# Pact Provider Verifier for NPM

[![Build Status](https://travis-ci.org/pact-foundation/pact-provider-verifier-npm.svg?branch=master)](https://travis-ci.org/pact-foundation/pact-provider-verifier-npm)

Installation wrapper for standalone platform-specific executables packaged from the Ruby [pact-provider-verifier](https://github.com/pact-foundation/pact-provider-verifier) gem.

On install, this package selects and installs the correct standalone executable for your environment.

This node module downloads the appropriate platform-specific and installs it alongside `pact-provider-verifier` inside the node_modules directory.

## Usage

```
npm install @pact-foundation/pact-provider-verifier
node_modules/.bin/pact-provider-verifier <options>
```

# Known issues

The packaged binary always prints out the following message on startup. Have not yet traced the source.

```
No entry for terminal type "xterm-256color";
using dumb terminal settings.
```

On npm install, the following warnings will be displayed. They do not appear to affect the behaviour of the provider verifier.

```
npm WARN excluding symbolic link lib/ruby/lib/libcrypto.dylib -> libcrypto.1.0.0.dylib
npm WARN excluding symbolic link lib/ruby/lib/libedit.dylib -> libedit.0.dylib
npm WARN excluding symbolic link lib/ruby/lib/libffi.dylib -> libffi.6.dylib
npm WARN excluding symbolic link lib/ruby/lib/libgmp.dylib -> libgmp.10.dylib
npm WARN excluding symbolic link lib/ruby/lib/liblzma.dylib -> liblzma.5.dylib
npm WARN excluding symbolic link lib/ruby/lib/libncurses.dylib -> libncurses.5.dylib
npm WARN excluding symbolic link lib/ruby/lib/libreadline.dylib -> libedit.0.dylib
npm WARN excluding symbolic link lib/ruby/lib/libssl.dylib -> libssl.1.0.0.dylib
npm WARN excluding symbolic link lib/ruby/lib/libtermcap.dylib -> libncurses.5.dylib
npm WARN excluding symbolic link lib/ruby/lib/libyaml.dylib -> libyaml-0.2.dylib
```
npm package: @pact-foundation/pact-provider-verifier-linux-x64
Description: Pact provider verifier
Author: Matt Fellows
Latest version: 1.4.3

<img src="https://github.com/pact-foundation/pact-logo/blob/master/media/logo-black.png" width="200">

# Pact Provider Verifier for NPM

[![Build Status](https://travis-ci.org/pact-foundation/pact-provider-verifier-npm.svg?branch=master)](https://travis-ci.org/pact-foundation/pact-provider-verifier-npm)

Installation wrapper for standalone platform-specific executables packaged from the Ruby [pact-provider-verifier](https://github.com/pact-foundation/pact-provider-verifier) gem.

On install, this package selects and installs the correct standalone executable for your environment.

This node module downloads the appropriate platform-specific and installs it alongside `pact-provider-verifier` inside the node_modules directory.

## Usage

```
npm install @pact-foundation/pact-provider-verifier
node_modules/.bin/pact-provider-verifier <options>
```

# Known issues

The packaged binary always prints out the following message on startup. Have not yet traced the source.

```
No entry for terminal type "xterm-256color";
using dumb terminal settings.
```

On npm install, the following warnings will be displayed. They do not appear to affect the behaviour of the provider verifier.

```
npm WARN excluding symbolic link lib/ruby/lib/libcrypto.dylib -> libcrypto.1.0.0.dylib
npm WARN excluding symbolic link lib/ruby/lib/libedit.dylib -> libedit.0.dylib
npm WARN excluding symbolic link lib/ruby/lib/libffi.dylib -> libffi.6.dylib
npm WARN excluding symbolic link lib/ruby/lib/libgmp.dylib -> libgmp.10.dylib
npm WARN excluding symbolic link lib/ruby/lib/liblzma.dylib -> liblzma.5.dylib
npm WARN excluding symbolic link lib/ruby/lib/libncurses.dylib -> libncurses.5.dylib
npm WARN excluding symbolic link lib/ruby/lib/libreadline.dylib -> libedit.0.dylib
npm WARN excluding symbolic link lib/ruby/lib/libssl.dylib -> libssl.1.0.0.dylib
npm WARN excluding symbolic link lib/ruby/lib/libtermcap.dylib -> libncurses.5.dylib
npm WARN excluding symbolic link lib/ruby/lib/libyaml.dylib -> libyaml-0.2.dylib
```
npm package: @pact-foundation/pact-provider-verifier-win32
Description: Pact provider verifier
Author: Matt Fellows
Latest version: 1.4.3

<img src="https://github.com/pact-foundation/pact-logo/blob/master/media/logo-black.png" width="200">

# Pact Provider Verifier for NPM

[![Build Status](https://travis-ci.org/pact-foundation/pact-provider-verifier-npm.svg?branch=master)](https://travis-ci.org/pact-foundation/pact-provider-verifier-npm)

Installation wrapper for standalone platform-specific executables packaged from the Ruby [pact-provider-verifier](https://github.com/pact-foundation/pact-provider-verifier) gem.

On install, this package selects and installs the correct standalone executable for your environment.

This node module downloads the appropriate platform-specific and installs it alongside `pact-provider-verifier` inside the node_modules directory.

## Usage

```
npm install @pact-foundation/pact-provider-verifier
node_modules/.bin/pact-provider-verifier <options>
```

# Known issues

The packaged binary always prints out the following message on startup. Have not yet traced the source.

```
No entry for terminal type "xterm-256color";
using dumb terminal settings.
```

On npm install, the following warnings will be displayed. They do not appear to affect the behaviour of the provider verifier.

```
npm WARN excluding symbolic link lib/ruby/lib/libcrypto.dylib -> libcrypto.1.0.0.dylib
npm WARN excluding symbolic link lib/ruby/lib/libedit.dylib -> libedit.0.dylib
npm WARN excluding symbolic link lib/ruby/lib/libffi.dylib -> libffi.6.dylib
npm WARN excluding symbolic link lib/ruby/lib/libgmp.dylib -> libgmp.10.dylib
npm WARN excluding symbolic link lib/ruby/lib/liblzma.dylib -> liblzma.5.dylib
npm WARN excluding symbolic link lib/ruby/lib/libncurses.dylib -> libncurses.5.dylib
npm WARN excluding symbolic link lib/ruby/lib/libreadline.dylib -> libedit.0.dylib
npm WARN excluding symbolic link lib/ruby/lib/libssl.dylib -> libssl.1.0.0.dylib
npm WARN excluding symbolic link lib/ruby/lib/libtermcap.dylib -> libncurses.5.dylib
npm WARN excluding symbolic link lib/ruby/lib/libyaml.dylib -> libyaml-0.2.dylib
```
npm package: @pact-foundation/pact-standalone
Description: Pact mock service and verifier wrapper package. Installing this will install an executable appropriate for your platform.
Author: Michel Boudreau
Latest version: 3.7.0
Deprecated: pact-standalone is now deprecated and merged into pact-node: please update to pact-node >= 6.12.0 or pact-js >= 5.8.0

<img src="https://github.com/pact-foundation/pact-logo/blob/master/media/logo-black.png" width="200">

# Pact Standalone Provider NPM

[![Build Status](https://travis-ci.org/pact-foundation/pact-standalone-npm.svg?branch=master)](https://travis-ci.org/pact-foundation/pact-standalone-npm)

Installation wrapper for pact [pact-standalone] executable.

On install, this package selects and installs the correct [pact-mock-service] and [pact-provider-verifier] executable for your environment. The platform-specific binaries `pact-mock-service` and `pact-provider-verifier` can be found inside the node_modules/.bin directory.

## Usage

    $ npm i @pact-foundation/pact-standalone
    $ node_modules/.bin/pact-mock-service --port 1234
    $ node_modules/.bin/pact-provider-verifier <args>

[pact-mock-service]: https://github.com/pact-foundation/pact-mock_service
[pact-provider-verifier]: https://github.com/pact-foundation/pact-provider-verifier
[pact-standalone]: https://github.com/pact-foundation/pact-ruby-standalone

## Developing

_NOTE_: If you're on OSX, you'll need [Bash 4](http://clubmate.fi/upgrade-to-bash-4-in-mac-os-x/) 
installed for the scripts to work.
npm package: @pact-foundation/pact-standalone-darwin
Description: Pact standalone service
Author: Pact Foundation
Latest version: 1.1.1
Deprecated: pact-standalone is now deprecated and merged into pact-node: please update to pact-node >= 6.12.0 or pact-js >= 5.8.0

<img src="https://github.com/pact-foundation/pact-logo/blob/master/media/logo-black.png" width="200">

# Pact Standalone Provider NPM

[![Build Status](https://travis-ci.org/pact-foundation/pact-standalone-npm.svg?branch=master)](https://travis-ci.org/pact-foundation/pact-standalone-npm)

Installation wrapper for pact [pact-standalone] executable.

On install, this package selects and installs the correct [pact-mock-service] and [pact-provider-verifier] executable for your environment. The platform-specific binaries `pact-mock-service` and `pact-provider-verifier` can be found inside the node_modules/.bin directory.

## Usage

    $ npm i @pact-foundation/pact-standalone
    $ node_modules/.bin/pact-mock-service --port 1234
    $ node_modules/.bin/pact-provider-verifier <args>

[pact-mock-service]: https://github.com/pact-foundation/pact-mock_service
[pact-provider-verifier]: https://github.com/pact-foundation/pact-provider-verifier
[pact-standalone]: https://github.com/pact-foundation/pact-ruby-standalone
npm package: @pact-foundation/pact-standalone-linux-ia32
Description: Pact standalone service
Author: Pact Foundation
Latest version: 1.1.1
Deprecated: pact-standalone is now deprecated and merged into pact-node: please update to pact-node >= 6.12.0 or pact-js >= 5.8.0

<img src="https://github.com/pact-foundation/pact-logo/blob/master/media/logo-black.png" width="200">

# Pact Standalone Provider NPM

[![Build Status](https://travis-ci.org/pact-foundation/pact-standalone-npm.svg?branch=master)](https://travis-ci.org/pact-foundation/pact-standalone-npm)

Installation wrapper for pact [pact-standalone] executable.

On install, this package selects and installs the correct [pact-mock-service] and [pact-provider-verifier] executable for your environment. The platform-specific binaries `pact-mock-service` and `pact-provider-verifier` can be found inside the node_modules/.bin directory.

## Usage

    $ npm i @pact-foundation/pact-standalone
    $ node_modules/.bin/pact-mock-service --port 1234
    $ node_modules/.bin/pact-provider-verifier <args>

[pact-mock-service]: https://github.com/pact-foundation/pact-mock_service
[pact-provider-verifier]: https://github.com/pact-foundation/pact-provider-verifier
[pact-standalone]: https://github.com/pact-foundation/pact-ruby-standalone
npm package: @pact-foundation/pact-standalone-linux-x64
Description: Pact standalone service
Author: Pact Foundation
Latest version: 1.1.1
Deprecated: pact-standalone is now deprecated and merged into pact-node: please update to pact-node >= 6.12.0 or pact-js >= 5.8.0

<img src="https://github.com/pact-foundation/pact-logo/blob/master/media/logo-black.png" width="200">

# Pact Standalone Provider NPM

[![Build Status](https://travis-ci.org/pact-foundation/pact-standalone-npm.svg?branch=master)](https://travis-ci.org/pact-foundation/pact-standalone-npm)

Installation wrapper for pact [pact-standalone] executable.

On install, this package selects and installs the correct [pact-mock-service] and [pact-provider-verifier] executable for your environment. The platform-specific binaries `pact-mock-service` and `pact-provider-verifier` can be found inside the node_modules/.bin directory.

## Usage

    $ npm i @pact-foundation/pact-standalone
    $ node_modules/.bin/pact-mock-service --port 1234
    $ node_modules/.bin/pact-provider-verifier <args>

[pact-mock-service]: https://github.com/pact-foundation/pact-mock_service
[pact-provider-verifier]: https://github.com/pact-foundation/pact-provider-verifier
[pact-standalone]: https://github.com/pact-foundation/pact-ruby-standalone
npm package: @pact-foundation/pact-standalone-win32
Description: Pact standalone service
Author: Pact Foundation
Latest version: 1.1.1
Deprecated: pact-standalone is now deprecated and merged into pact-node: please update to pact-node >= 6.12.0 or pact-js >= 5.8.0

<img src="https://github.com/pact-foundation/pact-logo/blob/master/media/logo-black.png" width="200">

# Pact Standalone Provider NPM

[![Build Status](https://travis-ci.org/pact-foundation/pact-standalone-npm.svg?branch=master)](https://travis-ci.org/pact-foundation/pact-standalone-npm)

Installation wrapper for pact [pact-standalone] executable.

On install, this package selects and installs the correct [pact-mock-service] and [pact-provider-verifier] executable for your environment. The platform-specific binaries `pact-mock-service` and `pact-provider-verifier` can be found inside the node_modules/.bin directory.

## Usage

    $ npm i @pact-foundation/pact-standalone
    $ node_modules/.bin/pact-mock-service --port 1234
    $ node_modules/.bin/pact-provider-verifier <args>

[pact-mock-service]: https://github.com/pact-foundation/pact-mock_service
[pact-provider-verifier]: https://github.com/pact-foundation/pact-provider-verifier
[pact-standalone]: https://github.com/pact-foundation/pact-ruby-standalone