# postinstall-postinstall

> runs your app's postinstall on this lib's postinstall

Latest version **2.1.0** (published 2020-03-27) · MIT license · 0 weekly downloads

## Install

```sh
npm install postinstall-postinstall
pnpm add postinstall-postinstall
yarn add postinstall-postinstall
bun add postinstall-postinstall
```

## 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 | 2020-03-27 |
| First published | 2018-03-29 |
| Weekly downloads | 0 |
| License | MIT |
| TypeScript types | none |
| Module format | CommonJS |
| Dependencies | 0 |
| Unpacked size | 2.7 KB |
| Known vulnerabilities | 0 |
| Install scripts | yes |
| GitHub stars | 56 |
| Author | David Sheldrick |
| Maintainers | ds300 |

## Links

- npm: https://www.npmjs.com/package/postinstall-postinstall
- Repository: https://github.com/ds300/postinstall-postinstall
- npm.io page: https://npm.io/package/postinstall-postinstall

## Recent versions

- 2.1.0 (latest) — 2020-03-27
- 2.0.0 — 2018-10-19
- 1.0.0 — 2018-03-29

## README

postinstall-postinstall
===================

Run your app's `postinstall` npm script during this package's `postinstall` script.

## Why

Yarn runs the `postinstall` script after `yarn`, `yarn install` and `yarn add <package>` but not after `yarn remove <package>`. If you add this package to your project, it will execute your project's `postinstall` hook even after a `yarn remove <package>`. This requires your `postinstall` script to be idempotent, because it will be run twice for `yarn`, `yarn install`, and `yarn add <package>`

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