# penv

> A package.json enviroment manager

Latest version **0.2.0** (published 2018-11-12) · MIT license · 0 weekly downloads

## Install

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

Provides the command `penv`.

## Health

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

Positive: no vulnerabilities.

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

Negative: abandoned; low maintenance score.

## Facts

| | |
|---|---|
| Version | 0.2.0 |
| Published | 2018-11-12 |
| First published | 2013-03-20 |
| Weekly downloads | 0 |
| License | MIT |
| TypeScript types | none |
| Module format | CommonJS |
| Dependencies | 3 |
| Unpacked size | 11.8 KB |
| Known vulnerabilities | 0 |
| Install scripts | no |
| GitHub stars | 16 |
| Author | Julian Duque |
| Maintainers | julianduque |

## Links

- npm: https://www.npmjs.com/package/penv
- Repository: https://github.com/julianduque/penv
- Homepage: https://github.com/julianduque/penv#readme
- Issues: https://github.com/julianduque/penv/issues
- npm.io page: https://npm.io/package/penv

## Dependencies (3)

- [eyes](https://npm.io/package/eyes.md) ~0.1.8
- [utile](https://npm.io/package/utile.md) ^0.3.0
- [lodash.merge](https://npm.io/package/lodash.merge.md) ^4.6.1

## Recent versions

- 0.2.0 (latest) — 2018-11-12
- 0.1.1 — 2013-12-13
- 0.1.0 — 2013-05-23
- 0.0.2 — 2013-03-20
- 0.0.1 — 2013-03-20

## README

# penv

A package.json environment customizer

Sometimes we need a different `package.json` properties for our different environments like production, staging and development. (Ex: `jitsu` deploys)

With `penv` you can customize your `package.json` file with properties defined inside an `environments.json` file.

## Installation

```
$ npm install -g penv
```

## Example

### package.json
Create your package.json file

```
{
  "name": "app",
  "subdomain": "myapp",
  "scripts": {
    "start": "node app.js"
  },
  "version": "0.0.1",
  "engines": {
    "node": "0.8.x"
  }
}
```

### environments.json
Create your environments.json file with the customized properties

```
{
  "staging": {
    "name": "app-staging",
    "subdomain": "myapp-staging"
  }
}
```

Then run

```
$ penv staging
```

And you will have a customized `package.json` like the following:

### customized package.json
```
{
  "name": "app-staging",
  "subdomain": "myapp-staging",
  "scripts": {
    "start": "node app.js"
  },
  "version": "0.0.1",
  "engines": {
    "node": "0.8.x"
  },
  "env": {
    "NODE_ENV": "staging"
  }
}
```

## Restore Original
The original `package.json` file will be renamed to `.package.json`.
You can restore your original package.json by running

```
$ penv base
```



## License

The MIT License (MIT)
Copyright (c) 2013 Julián Duque

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.

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