open-index/open-npm huggingface dataset:
npm package: @goodcastle/api-plugin-analytics
Description: Plugin analytics to tracking events
Author: GoodCastle
Latest version: 1.5.10

# api-plugin-segment


# Tracking plan
Each event defined here should be tracked [GoodCommerce Tracking Plan](https://docs.google.com/spreadsheets/d/16j-64CfQjBTIVI0_E47c68-KJeYqdyeq0VQlZ8elG1g/edit#gid=1164785081)

* segment docs [here](https://segment.com/docs/connections/spec/b2b-saas/)
npm package: @goodcastle/api-plugin-epayco-credit
Description: Plugin for Reaction API to support epayco payments with credit card
Author: GoodCastle
Latest version: 1.3.7

# api-plugin-example

## Summary

This plugin provides a Boilerplate for creating an `npm` plugin for the [Reaction API](https://github.com/reactioncommerce/reaction).

The `Developer Certificate of Origin` and `License` sections can stay as they are, assuming `Apache 2` license is used (our preferred license). All other sections of this README should be updated to reflect your plugin.

## Included in this example plugin

### `./gitlab-ci.yml`

CI script that enable Gitlab to run tests, lint, and semantic release your package. 

### `src/`

The `src` folder is where you'll put all the plugin files. An `index.js` with a bear-bones `registerPlugin` is included.

### `.gitignore`

A basic `gitignore` file

### `.nvmrc`

`.nvmrc` sets your plugin to use Node v12.14.1

### `babel.config.cjs`

If your plugin includes linting and tests, this file is required to allow esmodules to run correctly.

### `jest.config.cjs`

If your plugin includes tests, this file is required to allow esmodules to run correctly. You'll need to update the `transformIgnorePatterns` and `moduleNameMapper` sections to include any esmodule `npm` packages used in your plugin.

### `License.md`

If your plugin uses `Apache 2` licensing, you can leave this file as-is. If another type of licensing is used, you need to update this file, and the README, accordingly.

### `package.json`

The provided `package.json` is set up to install all needed packages and config for linting, testing, and semantic-release. You'll need to update the `name`, `description`, and add any new dependencies your plugin files use.

### `index.js`

The entrypoint file for your npm package, will most likely just export your plugin registration from the `src` folder.
npm package: @goodcastle/api-plugin-epayco-debit
Description: Reaction API Plugin for epayco-debit, supports payments with PSE
Author: GoodCastle
Latest version: 1.2.6

# api-plugin-example

## Summary

This plugin provides a Boilerplate for creating an `npm` plugin for the [Reaction API](https://github.com/reactioncommerce/reaction).

The `Developer Certificate of Origin` and `License` sections can stay as they are, assuming `Apache 2` license is used (our preferred license). All other sections of this README should be updated to reflect your plugin.

## Included in this example plugin

### `./gitlab-ci.yml`

CI script that enable Gitlab to run tests, lint, and semantic release your package. 

### `src/`

The `src` folder is where you'll put all the plugin files. An `index.js` with a bear-bones `registerPlugin` is included.

### `.gitignore`

A basic `gitignore` file

### `.nvmrc`

`.nvmrc` sets your plugin to use Node v12.14.1

### `babel.config.cjs`

If your plugin includes linting and tests, this file is required to allow esmodules to run correctly.

### `jest.config.cjs`

If your plugin includes tests, this file is required to allow esmodules to run correctly. You'll need to update the `transformIgnorePatterns` and `moduleNameMapper` sections to include any esmodule `npm` packages used in your plugin.

### `License.md`

If your plugin uses `Apache 2` licensing, you can leave this file as-is. If another type of licensing is used, you need to update this file, and the README, accordingly.

### `package.json`

The provided `package.json` is set up to install all needed packages and config for linting, testing, and semantic-release. You'll need to update the `name`, `description`, and add any new dependencies your plugin files use.

### `index.js`

The entrypoint file for your npm package, will most likely just export your plugin registration from the `src` folder.
npm package: @goodcastle/api-plugin-hydra-client
Description: Plugin for Reaction API to support nequi payments
Author: GoodCastle
Latest version: 1.3.0

# How do you can publish this package?

* make the changes you want
* Prapare your commit and tag the new version. Follow the example below
* git add . && git commit -m "message commit" && npm version 1.0.4
* The new tag is created automatically when you run "npm version 1.0.4" so you have to change the version.
npm package: @goodcastle/api-plugin-nequi
Description: Plugin for Reaction API to support nequi payments
Author: GoodCastle
Latest version: 0.8.3

# api-plugin-example

## Summary

This plugin provides a Boilerplate for creating an `npm` plugin for the [Reaction API](https://github.com/reactioncommerce/reaction).

The `Developer Certificate of Origin` and `License` sections can stay as they are, assuming `Apache 2` license is used (our preferred license). All other sections of this README should be updated to reflect your plugin.

## Included in this example plugin

### `./gitlab-ci.yml`

CI script that enable Gitlab to run tests, lint, and semantic release your package. 

### `src/`

The `src` folder is where you'll put all the plugin files. An `index.js` with a bear-bones `registerPlugin` is included.

### `.gitignore`

A basic `gitignore` file

### `.nvmrc`

`.nvmrc` sets your plugin to use Node v12.14.1

### `babel.config.cjs`

If your plugin includes linting and tests, this file is required to allow esmodules to run correctly.

### `jest.config.cjs`

If your plugin includes tests, this file is required to allow esmodules to run correctly. You'll need to update the `transformIgnorePatterns` and `moduleNameMapper` sections to include any esmodule `npm` packages used in your plugin.

### `License.md`

If your plugin uses `Apache 2` licensing, you can leave this file as-is. If another type of licensing is used, you need to update this file, and the README, accordingly.

### `package.json`

The provided `package.json` is set up to install all needed packages and config for linting, testing, and semantic-release. You'll need to update the `name`, `description`, and add any new dependencies your plugin files use.

### `index.js`

The entrypoint file for your npm package, will most likely just export your plugin registration from the `src` folder.
npm package: @goodcastle/api-plugin-search-mongo
Description: API plugin for search product and tags with mongoDB
Author: GoodCastle
Latest version: 0.2.0

# api-plugin-example

## Summary

This plugin provides a Boilerplate for creating an `npm` plugin for the [Reaction API](https://github.com/reactioncommerce/reaction).

The `Developer Certificate of Origin` and `License` sections can stay as they are, assuming `Apache 2` license is used (our preferred license). All other sections of this README should be updated to reflect your plugin.

## Included in this example plugin

### `./gitlab-ci.yml`

CI script that enable Gitlab to run tests, lint, and semantic release your package. 

### `src/`

The `src` folder is where you'll put all the plugin files. An `index.js` with a bear-bones `registerPlugin` is included.

### `.gitignore`

A basic `gitignore` file

### `.nvmrc`

`.nvmrc` sets your plugin to use Node v12.14.1

### `babel.config.cjs`

If your plugin includes linting and tests, this file is required to allow esmodules to run correctly.

### `jest.config.cjs`

If your plugin includes tests, this file is required to allow esmodules to run correctly. You'll need to update the `transformIgnorePatterns` and `moduleNameMapper` sections to include any esmodule `npm` packages used in your plugin.

### `License.md`

If your plugin uses `Apache 2` licensing, you can leave this file as-is. If another type of licensing is used, you need to update this file, and the README, accordingly.

### `package.json`

The provided `package.json` is set up to install all needed packages and config for linting, testing, and semantic-release. You'll need to update the `name`, `description`, and add any new dependencies your plugin files use.

### `index.js`

The entrypoint file for your npm package, will most likely just export your plugin registration from the `src` folder.
npm package: @goodcastle/api-plugin-taxes
Description: Taxes plugin for the Reaction API
Author: GoodCastle
Latest version: 1.0.0

# api-plugin-example

## Summary

This plugin provides a Boilerplate for creating an `npm` plugin for the [Reaction API](https://github.com/reactioncommerce/reaction).

The `Developer Certificate of Origin` and `License` sections can stay as they are, assuming `Apache 2` license is used (our preferred license). All other sections of this README should be updated to reflect your plugin.

## Included in this example plugin

### `./gitlab-ci.yml`

CI script that enable Gitlab to run tests, lint, and semantic release your package. 

### `src/`

The `src` folder is where you'll put all the plugin files. An `index.js` with a bear-bones `registerPlugin` is included.

### `.gitignore`

A basic `gitignore` file

### `.nvmrc`

`.nvmrc` sets your plugin to use Node v12.14.1

### `babel.config.cjs`

If your plugin includes linting and tests, this file is required to allow esmodules to run correctly.

### `jest.config.cjs`

If your plugin includes tests, this file is required to allow esmodules to run correctly. You'll need to update the `transformIgnorePatterns` and `moduleNameMapper` sections to include any esmodule `npm` packages used in your plugin.

### `License.md`

If your plugin uses `Apache 2` licensing, you can leave this file as-is. If another type of licensing is used, you need to update this file, and the README, accordingly.

### `package.json`

The provided `package.json` is set up to install all needed packages and config for linting, testing, and semantic-release. You'll need to update the `name`, `description`, and add any new dependencies your plugin files use.

### `index.js`

The entrypoint file for your npm package, will most likely just export your plugin registration from the `src` folder.