# heroku-cli-node

> utilities for working with Node.js programs

Latest version **2.1.0** (published 2017-05-19) · MIT license · 0 weekly downloads

## Install

```sh
npm install heroku-cli-node
pnpm add heroku-cli-node
yarn add heroku-cli-node
bun add heroku-cli-node
```

## 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 | 2.1.0 |
| Published | 2017-05-19 |
| First published | 2017-01-14 |
| Weekly downloads | 0 |
| License | MIT |
| TypeScript types | none |
| Module format | CommonJS |
| Dependencies | 2 |
| Known vulnerabilities | 0 (+3 in 1 direct dependencies) |
| Install scripts | no |
| Author | Hunter Loftis @hunterloftis |
| Maintainers | hunterloftis |
| Keywords | heroku-plugin |

## Links

- npm: https://www.npmjs.com/package/heroku-cli-node
- npm.io page: https://npm.io/package/heroku-cli-node

## Dependencies (2)

- [marked](https://npm.io/package/marked.md) ^0.3.6
- [marked-terminal](https://npm.io/package/marked-terminal.md) ^2.0.0

## Recent versions

- 2.1.0 (latest) — 2017-05-19
- 2.0.1 — 2017-04-06
- 2.0.0 — 2017-02-25
- 1.1.0 — 2017-01-14
- 1.0.0 — 2017-01-14

## README

# Quickly create best-practice Node.js apps for Heroku

```
$ heroku plugins:install heroku-cli-node
$ heroku node:generate myapp
```

## Why?

A solid node app still takes a lot of boilerplate:

- `package.json`, configured for an app instead of a module
- `.env` to inject environment variables locally
- `yarn.lock` to lock your dependencies
- `readme.md` to describe what the app does
- `.gitignore` so you can keep node modules out of git
- `app.json` to support [Pipelines](https://devcenter.heroku.com/articles/pipelines),
[Review Apps](https://devcenter.heroku.com/articles/github-integration-review-apps),
[CI](https://www.heroku.com/form/ci-beta),
and the ['Deploy to Heroku' Button](https://devcenter.heroku.com/articles/heroku-button)
- at least one file in `/bin` to provide an executable for your app
- a [standard](http://standardjs.com/) linter to keep you on track
- a mechanism for identifying [security vulnerabilities](https://github.com/nodesecurity/nsp)
- automated [testing](https://github.com/facebook/jest)
- and finally a `Procfile` to list your app's process types

...and I like to build solid apps, but I'm *also lazy.*

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