open-index/open-npm huggingface dataset:
npm package: @nodemodules/create-boilerplate
Description: boilerplate for [common-boilerplate](https://github.com/node-modules/common-boilerplate), use `npm init @nodemodules/boilerplate`
Author: TZ
Latest version: 0.2.0
Deprecated: use create-common-boilerplate instead, https://github.com/node-modules/create-common-boilerplate

# @nodemodules/create-boilerplate

boilerplate for [common-boilerplate](https://github.com/node-modules/common-boilerplate)

[![NPM version](https://img.shields.io/npm/v/@nodemodules/create-boilerplate.svg?style=flat-square)](https://npmjs.org/package/@nodemodules/create-boilerplate)
[![NPM quality](http://npm.packagequality.com/shield/@nodemodules/create-boilerplate.svg?style=flat-square)](http://packagequality.com/#?package=@nodemodules/create-boilerplate)
[![NPM download](https://img.shields.io/npm/dm/@nodemodules/create-boilerplate.svg?style=flat-square)](https://npmjs.org/package/@nodemodules/create-boilerplate)

[![Continuous Integration](https://github.com/node-modules/boilerplate-boilerplate/actions/workflows/nodejs.yml/badge.svg)](https://github.com/node-modules/boilerplate-boilerplate/actions/workflows/nodejs.yml)
[![Test coverage](https://img.shields.io/codecov/c/github/node-modules/boilerplate-boilerplate.svg?style=flat-square)](https://codecov.io/gh/node-modules/boilerplate-boilerplate)

## Usage

```bash
$ npm init @nodemodules/boilerplate
```
npm package: @nodemvc/node-mvc-cli
Description: NodeMVC CLI tool
Author: Alessandro D'Antoni
Latest version: 1.1.5

# node-mvc-cli

[NodeMVC](https://github.com/alexdant91/node-mvc) CLI tool to auto generate a new project.

## ❌ ATTENTION ❌

NodeMVC and NodeMVC CLI are on active developing process and under maintenance but also expterimental at the time of writing, install and use it at your risk!

## Install

Type ```yarn add -G @nodemvc/node-mvc-cli``` or ```npm install -g @nodemvc/node-mvc-cli``` to install the cli tool. Then you'll have global access to `node-mvc` command.

## Get started

Simply run ```node-mvc init``` on your projects directory and follow the instruction.

## Commands

To initialize new NodeMVC project:

```cmd
node-mvc init
```

You can install plugins to provide new functionalities:

```cmd
node-mvc add -n [PLUGIN_NAME]
```

To remove an installed plugin:

```cmd
node-mvc remove -n [PLUGIN_NAME]
```

To get the list of available plugins:

```cmd
node-mvc --available-plugins
```

or

```cmd
node-mvc --ap
```

## Available plugins

| Name            | Status      | Install command                                         |
|-----------------|-------------|---------------------------------------------------------|
| Stripe Payments | Development | ```node-mvc add -n @nodemvc/stripe-payments-provider``` |
| Paypal Payments | Development | ```node-mvc add -n @nodemvc/paypal-payments-provider``` |

More plugins comming soon.

## To do

- [ ] Add remote repository for plugins, based on db;
- [ ] Add possibility to register custom plugins;
npm package: @nodenet/cli
Description: A nodeJS based server framework for building simple and fast server applications
Author: Mario Bertsch
Latest version: 0.3.1
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

# NodeNet CLI

### DevelopmentStatus

CLI: **v0.3.0** | JWT Auth Update  
Core: **v0.3.0** | JWT Auth Update

Please feel free to submit ideas or bugs, just create an Issue.

---

## Installation

`npm install @nodenet/cli --global`  

---

## Documentation

https://www.nodenet.wiki

## Usage

After installation, you can use the CLI by typing `nodenet` in your terminal. \
From there, you will get a list of all available commands.

With `nodenet new MyProject` you can create a new Project  
With `nodenet --version` you get the current version  
With `nodenet --help` you get a list of all commands available

After a new Project is created, open the project and start the server with:  
`npm run start`

---
npm package: @nodenet/core
Description: NodeNet Core Library
Author: Mario Bertsch
Latest version: 0.3.12
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

# NodeNetCore

This is the core package for NodeNet.  
It contains the core functionality of the NodeNet framework.  
  
For the best experience, it is **recommended** to use the **NodeNetCLI**  
`npm install @nodenet/cli --global` to create a new project.  
  
All needed packages and dependencies will be installed automatically.  
By default, NodeNet will not work by itself and needs other packages to work.


## Installation

```bash
npm install @nodenet/cli --global

nodenet new MyProject
```
npm package: @nodenv/nodenv-aliases
Description: Create aliases for nodenv Node versions
Latest version: 2.1.1

# nodenv-aliases

[![Latest GitHub Release](https://img.shields.io/github/v/release/nodenv/nodenv-aliases?logo=github&sort=semver)](https://github.com/nodenv/nodenv-aliases/releases/latest)
[![Latest npm Release](https://img.shields.io/npm/v/@nodenv/nodenv-aliases)](https://www.npmjs.com/package/@nodenv/nodenv-aliases/v/latest)
[![Test](https://img.shields.io/github/workflow/status/nodenv/nodenv-aliases/Test?label=tests&logo=github)](https://github.com/nodenv/nodenv-aliases/actions?query=workflow%3ATest)

Aliases for nodenv Node versions

Invoke `nodenv alias <name> <version>` to make a symbolic link from `<name>` to
`<version>` in the [nodenv][] versions directory, effectively creating an
alias. The cool part is that if you pass in a major or major.minor release as the name, you
can give `--auto` to link to the latest installed minor or patch level (respectively). For example,
`nodenv alias 4.4 --auto` will automatically create an alias from `4.4` to
`4.4.7` (or to whatever is the most recent version you have installed). Similarly,
`nodenv alias 6 --auto` will automatically create an alias from `6` to
`6.10.3` (or to whatever is the most recent version you have installed).

Plus, if you're using [node-build][], `nodenv install major.minor.patch`
automatically invokes `nodenv alias major --auto` and
`nodenv alias major.minor --auto`, so you'll always have
up to date aliases.

<!-- toc -->

- [Installation](#installation)
- [Usage](#usage)
- [Credits](#credits)

<!-- tocstop -->

## Installation

    git clone https://github.com/nodenv/nodenv-aliases.git $(nodenv root)/plugins/nodenv-aliases

## Usage

Create a `major` and `major.minor` alias for each installed major and minor release:

    nodenv alias --auto

Create a `major` alias for the highest major release of, say 6:

    nodenv alias 6 --auto

Create a `major.minor` alias for the highest minor release of, say 0.8:

    nodenv alias 0.8 --auto

Create a `major.minor.patch-pre` alias for the highest prerelease of, say 8:

    nodenv alias 8.0.0-rc --auto

Create a named alias for a specific release:

    nodenv alias boron 6

Remove an alias:

    nodenv unalias <alias-name>

or

    nodenv alias <alias-name> --remove

## Credits

Forked from [Tim Pope][tpope]'s [rbenv-aliases][] by [Jason Karns][jasonkarns] and modified for nodenv.

[nodenv]: https://github.com/nodenv/nodenv
[node-build]: https://github.com/nodenv/node-build
[rbenv-aliases]: https://github.com/tpope/rbenv-aliases
[tpope]: https://github.com/tpope
[jasonkarns]: https://github.com/jasonkarns
npm package: @nodenv/nodenv-each
Description: nodenv plugin to run a command across all installed nodes
Latest version: 1.3.0

# nodenv-each

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

Invoke commands for each nodenv Node version

<!-- toc -->

- [Installation](#installation)
- [Usage](#usage)
  * [Examples](#examples)
- [Credits](#credits)

<!-- tocstop -->

## Installation

To install nodenv-each, clone this repository into your nodenv plugins directory.

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

## Usage

```
$ nodenv help each
```

Verbose mode will print a header for each node so you can distinguish
the output.

**note**: Aliases ([nodenv-aliases][]) or symlinks are skipped.

### Examples

```
$ nodenv each npm install
$ nodenv each -v npm test
```

## Credits

Forked from [Chris Eppstein][chriseppstein]'s [rbenv-each][] by [Jason Karns][jasonkarns] and modified for [nodenv][].

[chriseppstein]: https://github.com/chriseppstein
[rbenv-each]: https://github.com/rbenv/rbenv-each
[jasonkarns]: https://github.com/jasonkarns
[nodenv]: https://github.com/nodenv/nodenv
[nodenv-aliases]: https://github.com/nodenv/nodenv-aliases
npm package: @nodenv/nodenv-env
Description: View environment variables pertaining to nodejs
Latest version: 1.0.0

# nodenv-env

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

[nodenv][] plugin to view environment variables pertaining to nodejs

## Installation

To install nodenv-env, clone this repository into your ~/.nodenv/plugins directory.

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

## Usage

Run the command

    $ nodenv env

## Credits

Forked from [ianheggie][]'s [rbenv-env][] by [Jason Karns][jasonkarns] and modified for nodenv.

[nodenv]: https://github.com/nodenv/nodenv
[ianheggie]: https://github.com/ianheggie
[rbenv-env]: https://github.com/ianheggie/rbenv-env
[jasonkarns]: https://github.com/jasonkarns