open-index/open-npm huggingface dataset:
npm package: @nodenv/nodenv-man
Description: [![Build Status](https://travis-ci.org/nodenv/nodenv-man.svg?branch=master)](https://travis-ci.org/nodenv/nodenv-man)
Latest version: 1.1.0

[![Build Status](https://travis-ci.org/nodenv/nodenv-man.svg?branch=master)](https://travis-ci.org/nodenv/nodenv-man)

# Man pages for nodenv Node versions

nodenv-man is a plugin for [nodenv] to easily access the man pages for the
currently set node version, e.g. `node(1)` and `npm(1)`.

Technically, nodenv-man is a wrapper for `man(1)` that takes care of using the
correct manpath.

## Installation

To install nodenv-man, clone this repository into your `$(nodenv root)/plugins`
directory.

    ```sh
    $ mkdir -p "$(nodenv root)/plugins"
    $ git clone https://github.com/nodenv/nodenv-man.git "$(nodenv root)/plugins/nodenv-man"
    ```

## Usage

Simply use nodenv-man in the same way as your system's `man(1)` program. All
command-line options are passed through to it.

Some examples:

* Show `node(1)` manual:

    ```sh
    $ nodenv man node
    ```

* Show `npm(1)` manual:

    ```sh
    $ nodenv man 1 npm
    ```

* Print location of `node(1)` manual:

    ```sh
    $ nodenv man -w node
    /usr/local/var/nodenv/versions/4.2.1/share/man/man1/node.1
    ```

* Change node version and print new location of man page:

    ```sh
    $ NODENV_VERSION=5.0.0 nodenv man -w node
    /usr/local/var/nodenv/versions/5.0.0/share/man/man1/node.1
    ```


[nodenv]: https://github.com/nodenv/nodenv
npm package: @nodenv/nodenv-npm-migrate
Description: Migrate npm packages from one Node version to another
Latest version: 0.1.1

# nodenv-npm-migrate

nodenv-npm-migrate is a [nodenv](https://github.com/nodenv/nodenv) plugin
that provides a `nodenv migrate` command to migrate npm packages from one Node
version to another.

This plugin was forked from
[pyenv-pip-migrate](https://github.com/yyuu/pyenv-pip-migrate).

## Installation

### Installing as a nodenv plugin

Installing nodenv-npm-migrate as a nodenv plugin will give you access to the
`nodenv migrate` command.

    $ git clone git://github.com/nodenv/nodenv-npm-migrate.git "$(nodenv root)/plugins/nodenv-npm-migrate"

This will install the latest development version of nodenv-npm-migrate into
the `$(nodenv root)/plugins/nodenv-npm-migrate` directory. From that directory, you
can check out a specific release tag. To update nodenv-npm-migrate, run `git
pull` to download the latest changes.


### Installing with Homebrew (for OS X users)

Mac OS X users can install nodenv-npm-migrate with the
[Homebrew](http://brew.sh) package manager.
This will give you access to the `nodenv-migrate` command. If you have nodenv
installed, you will also be able to use the `nodenv migrate` command.

*This is the recommended method of installation if you installed nodenv
 with Homebrew.*

```
$ brew install nodenv/nodenv/nodenv-npm-migrate
```

Or, if you would like to install the latest development release:

```
$ brew install --HEAD nodenv/nodenv/nodenv-npm-migrate
```

## Usage

### Using `nodenv migrate` with nodenv

nodenv-npm-migrate uses `npm ls --global --depth=0` to dump all installed
packages in a Node version, and then tries to `npm install` them into another
version.

Let's say if you have following two versions in nodenv.

    $ nodenv versions
    * 0.12.0 (set by /home/jawshooah/.nodenv/version)
      iojs-1.6.2
    $ npm ls --global --depth=0
    /home/jawshooah/.nodenv/versions/0.12.0/lib
    ├── csslint@0.10.0
    ├── eslint@0.17.1
    ├── git-guilt@0.0.7
    ├── grunt@0.4.5
    ├── grunt-cli@0.1.13
    └── npm@2.7.4

To migrate installed packages from `0.12.0` to `iojs-1.6.2`, use `nodenv
migrate`.

    $ nodenv migrate 0.12.0 iojs-1.6.2
    $ nodenv global iojs-1.6.2
    $ npm ls --global --depth=0
    /home/jawshooah/.nodenv/versions/iojs-1.6.2/lib
    ├── csslint@0.10.0
    ├── eslint@0.17.1
    ├── git-guilt@0.0.7
    ├── grunt@0.4.5
    ├── grunt-cli@0.1.13
    └── npm@2.7.4

## Credits

Forked from [Yamashita, Yuu][yyuu]'s [pyenv-pip-migrate][] by [Josh Hagins][jawshooah] and modified for [nodenv][].

[yyuu]: https://github.com/yyuu
[pyenv-pip-migrate]: https://github.com/yyuu/pyenv-pip-migrate
[jawshooah]: https://github.com/jawshooah
[nodenv]: https://github.com/nodenv/nodenv
npm package: @nodenv/nodenv-package-json-engine
Description: Activate a nodenv node version from package.json engines
Author: Adam Hull
Latest version: 3.0.3

# nodenv-package-json-engine

This is a plugin for [nodenv](https://github.com/nodenv/nodenv)
that detects the Node version based on the [`engines`](https://docs.npmjs.com/files/package.json#engines) field of the current tree's `package.json` file. The `$NODENV_VERSION` environment variable (set with `nodenv shell`) and `.node-version` files still take precedence.

When `engines` is configured with a range this plugin chooses the greatest installed version matching the range, or exits with an error if none match.

[![Build Status](https://travis-ci.org/nodenv/nodenv-package-json-engine.svg?branch=master)](https://travis-ci.org/nodenv/nodenv-package-json-engine)

## Installation

### Installing with Git

```sh
$ git clone https://github.com/nodenv/nodenv-package-json-engine.git $(nodenv root)/plugins/nodenv-package-json-engine
```

### Installing with Homebrew

Mac OS X users can install [many nodenv plugins](https://github.com/nodenv/homebrew-nodenv) with [Homebrew](http://brew.sh).

*This is the recommended method of installation if you installed nodenv with
Homebrew.*

```sh
$ brew tap nodenv/nodenv
$ brew install nodenv-package-json-engine
```

## Usage

Once you've installed the plugin you can verify that it's working by `cd`ing into a project that has a `package.json` file with `engines` and does not have a `.node-version` file.  From anywhere in the project's tree, run `nodenv which node`.

## Contributing

`npm install` and `npm test` from within the project.

## Credits

`package.json` inspection and SemVer integration heavily inspired by nvmish [[1]](https://github.com/goodeggs/homebrew-delivery-eng/blob/master/nvmish.sh) [[2]](https://gist.github.com/assaf/ee377a186371e2e269a7) and [rbenv-bundler-ruby-version](https://github.com/aripollak/rbenv-bundler-ruby-version).

Shell semver range support provided by [sh-semver](https://github.com/qzb/sh-semver).

`package.json` parsing provided by [JSON.sh](https://github.com/dominictarr/JSON.sh).
npm package: @nodenv/nodenv-update
Description: nodenv plugin for updating nodenv and all nodenv plugins
Latest version: 1.0.0

# nodenv-update

A [nodenv][] plugin that provides the
`nodenv update` command to update nodenv as well as all installed nodenv plugins.

## Installation

To install nodenv-update, clone this repository into your `$(nodenv root)/plugins` directory
(you'll need a recent version of nodenv that supports plugin bundles).

    $ mkdir -p "$(nodenv root)"/plugins
    $ git clone https://github.com/nodenv/nodenv-update.git "$(nodenv root)"/plugins/nodenv-update

## Usage

    nodenv update

## Credits

Forked from [Konstantin Haase](https://github.com/rkh)'s
[rbenv-update][] by 
[Charlie Johnson](https://github.com/charlesbjohnson) and modified for [nodenv][].

[rbenv-update]: https://github.com/rkh/rbenv-update
[nodenv]: https://github.com/nodenv/nodenv
npm package: @nodenv/nodenv-vars
Description: A nodenv plugin that safely sets global and per-project environment variables
Latest version: 1.2.0

# nodenv-vars

This is a plugin for [nodenv](https://github.com/nodenv/nodenv)
that lets you set global and project-specific environment variables
before spawning Node processes.

## Installation

To install nodenv-vars, clone this repository into your
`$(nodenv root)/plugins` directory. (You'll need a recent version of nodenv
that supports plugin bundles.)

    $ mkdir -p $(nodenv root)/plugins
    $ cd $(nodenv root)/plugins
    $ git clone https://github.com/nodenv/nodenv-vars.git

## Usage

Define environment variables in an `.nodenv-vars` file in your project,
one variable per line, in the format `VAR=value`. For example:

    HUBOT_CAMPFIRE_ACCOUNT=nodenv
    HUBOT_CAMPFIRE_TOKEN=somerandomtoken
    HUBOT_CAMPFIRE_ROOMS=some,campfire,rooms

You can perform variable substitution with the traditional `$`
syntax. For example, to append to `HUBOT_CAMPFIRE_ROOMS`:

    HUBOT_CAMPFIRE_ROOMS=$HUBOT_CAMPFIRE_ROOMS:some,extra,rooms

You may also have conditional variable assignments, such that a
variable will **only** be set if it is not already defined or is blank:

    USER_ID?=OiNutter

In the above case, `USER_ID` will only be set if `$USER_ID` is
currently empty (i.e., if `[ -z "$USER_ID" ]` is true).

Spaces are allowed in values; quoting is not necessary. Expansion and
command substitution are not allowed. Lines beginning with `#` or any
lines not in the format VAR=value will be ignored.

Variables specified in the `$(nodenv root)/vars` file will be set
first. Then variables specified in `.nodenv-vars` files in any parent
directories of the current directory will be set. Variables from the
`.nodenv-vars` file in the current directory are set last.

Use the `nodenv vars` command to print all environment variables in the
order they'll be set.

### Credits

Forked from [Sam Stephenson](https://github.com/sstephenson)'s
[rbenv-vars](https://github.com/rbenv/rbenv-vars) by [Will
McKenzie](https://github.com/oinutter) and modified for nodenv.
npm package: @nodeonjs/nodeonjs
Description: NodeonJS is a library/boilerplate for NodeJS project 
Author: mgrec
Latest version: 1.1.4

# nodeonjs-project

![npm](https://img.shields.io/npm/v/@nodeonjs/nodeonjs.svg)

![npm bundle size](https://img.shields.io/bundlephobia/min/@nodeonjs/nodeonjs.svg)
npm package: @nodepack/babel-preset-nodepack
Description: Babel preset for Nodepack
Author: Guillaume Chau
Latest version: 0.9.0

# babel-preset-backpack

This package includes the [Babel](https://babeljs.io) preset used by [nodepack](https://github.com/Akryum/nodepack)

## Usage in Nodepack Projects

The easiest way to use this configuration is with Nodepack, which includes it by default. **You don’t need to install it separately in Nodepack projects.**

## Usage Outside of Nodepack

If you want to use this Babel preset in a project not built with Nodepack, you can install it with following steps.

First, [install Babel](https://babeljs.io/docs/setup/).

Then create a file named `.babelrc` with following contents in the root folder of your project:

```js
{
  "presets": ["@nodepack/service"]
}
```

This preset uses the `useBuiltIns` option with [transform-object-rest-spread](http://babeljs.io/docs/plugins/transform-object-rest-spread/), which assumes that `Object.assign` is available or polyfilled.
npm package: @nodepack/conventional-changelog
Description: conventional-changelog nodepack preset
Author: Guillaume Chau
Latest version: 0.1.0

# @nodepack/conventional-changelog

Custom preset for [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog/) which groups changes by package (`packages/@nodepack/xxx`). It works by getting the package which has the highest number of changed files in each commit.

```bash
yarn add -D @nodepack/conventional-changelog
```

Example usage:

```js
const execa = require('execa')
const cc = require('conventional-changelog')
const config = require('@nodepack/conventional-changelog')

const gen = module.exports = version => {
  const fileStream = require('fs').createWriteStream(`CHANGELOG.md`)

  cc({
    config,
    releaseCount: 0,
    pkg: {
      transform (pkg) {
        pkg.version = `v${version}`
        return pkg
      }
    }
  }).pipe(fileStream).on('close', async () => {
    delete process.env.PREFIX
    await execa('git', ['add', '-A'], { stdio: 'inherit' })
    await execa('git', ['commit', '-m', `chore: ${version} changelog [ci skip]`], { stdio: 'inherit' })
  })
}

if (process.argv[2] === 'run') {
  const version = require('../lerna.json').version
  gen(version)
}
```

[Result example](https://gist.github.com/Akryum/3cc2e3afaf5f7e730a3b9648b7ce4133)
npm package: @nodepit/jest-mongodb-downloader
Description: Script which simply downloads MongoDB as configured in `jest-mongodb-config.js`; useful for Docker caching.
Author: nodepit.com
Latest version: 1.0.0
Deprecated: No longer needed. Please see: https://github.com/NodePit/jest-mongodb-downloader#deprecation-note

# jest-mongodb-downloader

When being run, this script simply downloads the MongoDB version defined in `jest-mongodb-config.js`.

## Why?

But [`jest-mongodb`](https://github.com/shelfio/jest-mongodb) does this automatically upon start, so why would you want to do this? -- When explicitly triggering the download, you can make use of Docker’s caching, and avoid downloading MongoDB again and again if you just modified some source code.

## Usage

1. Install with `yarn add @nodepit/jest-mongodb-downloader -D`

2. Add the following line to your Dockerfile **before** running the tests and copying the source code (make sure that `jest-mongodb-config.js` is already in the image).

   Add `MONGOMS_DISABLE_POSTINSTALL` to prevent downloading the default version of MongoDB and only install the version which is specified in the `jest-mongodb-config.js`.

   ```Dockerfile
   ENV MONGOMS_DISABLE_POSTINSTALL=1
   RUN yarn
   COPY jest-mongodb-config.js ./
   RUN yarn run jest-mongodb-downloader
   ```

3. Give a GitHub star to say “Thank you, NodePit!”

- - -

Copyright [nodepit.com](https://nodepit.com), 2020.
npm package: @nodepit/mailchimp
Description: Node.js client for managing Mailchimp subscriptions
Author: nodepit.com
Latest version: 2.1.4
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

# Mailchimp Node.js Library

[![Run Status](https://api.shippable.com/projects/5cd6aee6b875100006629f27/badge?branch=master)]()
[![Coverage Badge](https://api.shippable.com/projects/5cd6aee6b875100006629f27/coverageBadge?branch=master)]()
[![npm version](https://badge.fury.io/js/%40nodepit%2Fmailchimp.svg)](https://badge.fury.io/js/%40nodepit%2Fmailchimp)

The [Mailchimp API](http://apidocs.mailchimp.com) allows you to sync email activity and campaign stats with your database, manage lists/audiences, view and control automation workflows, and test calls and endpoints before pushing to production.

This Node.js library provides a simple wrapper implementation for the [Mailchimp API](http://apidocs.mailchimp.com) that currently supports basic functionality around creating, editing and deleting members.

## Installation

```shell
$ yarn add @nodepit/mailchimp
```

## Usage

```javascript
import { Mailchimp } from '@nodepit/mailchimp';

const yourApiKey = 'Your Mailchimp API key';
const yourListId = 'Your Mailchimp list id';

const mailChimp = new Mailchimp(yourApiKey);
await mailChimp.createMember(yourListId, 'mail@example.com', {
  status: MemberStatus.SUBSCRIBED,
  merge_fields: { FNAME: 'Daniel' },
  // more parameters
});
```

## Development

Install NPM dependencies with `yarn`.

To execute the tests, run the `test` task.

For the best development experience, make sure that your editor supports [ESLint](https://eslint.org/docs/user-guide/integrations), [markdownlint](https://github.com/DavidAnson/markdownlint) and [EditorConfig](http://editorconfig.org).

## Releasing to NPM

Commit all changes and run the following:

```shell
$ npm login
$ npm version <update_type>
$ npm publish --access public
```

… where `<update_type>` is one of `patch`, `minor`, or `major`. This will update the `package.json`, and create a tagged Git commit with the version number.

## Contributing

Pull requests are very welcome. Feel free to discuss bugs or new features by opening a new [issue](https://github.com/NodePit/node-mailchimp/issues).

- - -

Copyright [nodepit.com](https://nodepit.com), 2018 – 2022.
npm package: @nodeplusplus/xregex-context
Description: Manage context of XRegex
Author: Tuan Nguyen
Latest version: 1.1.1

# @nodeplusplus/xregex-context

> Manage context of XRegex

[![Coverage Status](https://coveralls.io/repos/github/nodeplusplus/xregex-context/badge.svg)](https://coveralls.io/github/nodeplusplus/xregex-context)
[![CircleCI](https://circleci.com/gh/nodeplusplus/xregex-context.svg?style=svg)](https://circleci.com/gh/nodeplusplus/xregex-context)
npm package: @nodeplusplus/xregex-filter
Description: Filter your data by JSON schema
Author: Tuan Nguyen
Latest version: 1.3.0

# @nodeplusplus/xregex-filter

> Filter your data by JSON schema

[![Coverage Status](https://coveralls.io/repos/github/nodeplusplus/xregex-filter/badge.svg)](https://coveralls.io/github/nodeplusplus/xregex-filter)
[![CircleCI](https://circleci.com/gh/nodeplusplus/xregex-filter.svg?style=svg)](https://circleci.com/gh/nodeplusplus/xregex-filter)
npm package: @nodeplusplus/xregex-helpers
Description: Utility functions of XRegex Platform
Author: Tuan Nguyen
Latest version: 1.1.0

# @nodeplusplus/xregex-helpers

> Utility functions of XRegex Platform

[![Coverage Status](https://coveralls.io/repos/github/nodeplusplus/xregex-helpers/badge.svg)](https://coveralls.io/github/nodeplusplus/xregex-helpers)
[![CircleCI](https://circleci.com/gh/nodeplusplus/xregex-helpers.svg?style=svg)](https://circleci.com/gh/nodeplusplus/xregex-helpers)
npm package: @nodeplusplus/xregex-json
Description: Another way to work with json string and object
Author: Tuan Nguyen
Latest version: 1.0.1

# @nodeplusplus/xregex-json

> Another way to work with json string and object

[![Coverage Status](https://coveralls.io/repos/github/nodeplusplus/xregex-json/badge.svg)](https://coveralls.io/github/nodeplusplus/xregex-json)
[![CircleCI](https://circleci.com/gh/nodeplusplus/xregex-json.svg?style=svg)](https://circleci.com/gh/nodeplusplus/xregex-json)
npm package: @nodeplusplus/xregex-logger
Description: Just a simple logger with attention at performance
Author: Tuan Nguyen
Latest version: 1.0.0

# @nodeplusplus/xregex-logger

> Just a simple logger with attention at performance

[![Coverage Status](https://coveralls.io/repos/github/nodeplusplus/xregex-logger/badge.svg)](https://coveralls.io/github/nodeplusplus/xregex-logger)
[![CircleCI](https://circleci.com/gh/nodeplusplus/xregex-logger.svg?style=svg)](https://circleci.com/gh/nodeplusplus/xregex-logger)
npm package: @nodeplusplus/xregex-parser
Description: Extract your data from any source
Author: Tuan Nguyen
Latest version: 1.1.3

# @nodeplusplus/xregex-parser

> Extract your data from any source

[![Coverage Status](https://coveralls.io/repos/github/nodeplusplus/xregex-parser/badge.svg)](https://coveralls.io/github/nodeplusplus/xregex-parser)
[![CircleCI](https://circleci.com/gh/nodeplusplus/xregex-parser.svg?style=svg)](https://circleci.com/gh/nodeplusplus/xregex-parser)
npm package: @nodeplusplus/xregex-provider
Description: Provide your resource with quota
Author: Tuan Nguyen
Latest version: 1.1.5

# @nodeplusplus/xregex-provider

> Provide resource base on quota

[![Coverage Status](https://coveralls.io/repos/github/nodeplusplus/xregex-provider/badge.svg)](https://coveralls.io/github/nodeplusplus/xregex-provider)
[![CircleCI](https://circleci.com/gh/nodeplusplus/xregex-provider.svg?style=svg)](https://circleci.com/gh/nodeplusplus/xregex-provider)
npm package: @nodeplusplus/xregex-template
Description: Provide template functions of XRegex Platform
Author: Tuan Nguyen
Latest version: 1.0.8

# @nodeplusplus/xregex-template

> Provide template functions of XRegex Platform

[![Coverage Status](https://coveralls.io/repos/github/nodeplusplus/xregex-template/badge.svg)](https://coveralls.io/github/nodeplusplus/xregex-template)
[![CircleCI](https://circleci.com/gh/nodeplusplus/xregex-template.svg?style=svg)](https://circleci.com/gh/nodeplusplus/xregex-template)
npm package: @nodeplusplus/xregex-yml
Description: Parse YAML file with some defined types
Author: Tuan Nguyen
Latest version: 1.0.0

# @nodeplusplus/xregex-yml

> Extract your data from any source

[![Coverage Status](https://coveralls.io/repos/github/nodeplusplus/xregex-yml/badge.svg)](https://coveralls.io/github/nodeplusplus/xregex-yml)
[![CircleCI](https://circleci.com/gh/nodeplusplus/xregex-yml.svg?style=svg)](https://circleci.com/gh/nodeplusplus/xregex-yml)