# metarunnerjs

> A metarunner tool

Latest version **1.0.5** (published 2015-10-27) · MIT license · 0 weekly downloads

## Install

```sh
npm install metarunnerjs
pnpm add metarunnerjs
yarn add metarunnerjs
bun add metarunnerjs
```

Provides the command `metarunner`.

## Health

**Score 15/100 (F)** — status: abandoned.

Positive: no vulnerabilities.

Warnings: low downloads; no types; no esm support.

Negative: abandoned; low maintenance score.

## Facts

| | |
|---|---|
| Version | 1.0.5 |
| Published | 2015-10-27 |
| First published | 2015-10-10 |
| Weekly downloads | 0 |
| License | MIT |
| TypeScript types | none |
| Module format | CommonJS |
| Dependencies | 4 |
| Known vulnerabilities | 0 |
| Install scripts | no |
| Author | Chase Adams |
| Maintainers | chaseadamsio |

## Links

- npm: https://www.npmjs.com/package/metarunnerjs
- npm.io page: https://npm.io/package/metarunnerjs

## Dependencies (4)

- [mkdirp](https://npm.io/package/mkdirp.md) ^0.5.1
- [prompt](https://npm.io/package/prompt.md) ^0.2.14
- [resolve](https://npm.io/package/resolve.md) ^1.1.6
- [jsonfile](https://npm.io/package/jsonfile.md) ^2.2.2

## Recent versions

- 1.0.5 (latest) — 2015-10-27
- 1.0.4 — 2015-10-27
- 1.0.3 — 2015-10-27
- 1.0.2 — 2015-10-27
- 1.0.1 — 2015-10-10
- 1.0.0 — 2015-10-10

## README

# metarunnerjs

> A tool for generating meta-runners for Node CLI Tools

`metarunner` allows you to generate a thin CLI tool that can be installed `-g` so your consumers don't have to install a bulky library at the global level or be tied to a global dependency for projects, while allowing them to use your command in the command line.

## Installation

Within your cli project, run:

```
npm install metarunner --save
```

## Usage

To scaffold out your thin command line utility, from within your project simply run:

```
node ./node_modules/.bin/metarunner
```

This will prompt you for a few questions and generate your CLI tool after you've answered all the prompts.

### Example Workflow

`metarunnerjs` generates a thin CLI runner that looks for a project's local dependency of the same name of the command being run.

For instance, I create a package called `howl` that has a `bin` in its `package.json` and when I run it, it will output the text "howl".

I would have a project dependency in my project on the `howl` package, but I would only be able to access it by adding it as a script to the `package.json` of my project.

If I use the `metarunnerjs` package, I can create a `howl-cli` (this is the recommended naming convention), which, when initialized, will add a `bin` entry to check for the dependency in your project and then run that dependencies `bin`.

---
_Source: https://npm.io/package/metarunnerjs · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._