# Install install-peerdeps with Homebrew

CLI to automatically install peerDeps. Version 3.0.7 via Homebrew; verified from local package data.

## Install

```sh
sudo av install brew:install-peerdeps
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install install-peerdeps
```

  Evidence: local Homebrew formula metadata

## Package facts

- **Package key:** brew:install-peerdeps
- **Package manager:** Homebrew
- **Package manager page:** <https://formulae.brew.sh/formula/install-peerdeps>
- **Version:** 3.0.7
- **Source summary:** CLI to automatically install peerDeps
- **Homepage:** <https://github.com/nathanhleung/install-peerdeps>
- **Repository:** <https://github.com/nathanhleung/install-peerdeps>
- **Upstream docs:** <https://github.com/nathanhleung/install-peerdeps#readme>
- **License:** MIT
- **Source archive:** <https://registry.npmjs.org/install-peerdeps/-/install-peerdeps-3.0.7.tgz>
- **Generated:** 2026-07-08T07:18:31+00:00

## Executables

- install-peerdeps (cli)
- install-peerdeps (alias)

## Dependencies

- node

## Install behavior

- Post-install hook: not defined
- Bottle: available on all

## Freshness

- Page generated: 2026-07-08
- Package-manager version: 3.0.7
- Local data: ok
- Upstream repository: https://github.com/nathanhleung/install-peerdeps
- info: No package-manager update timestamp was available.
- info: No cached GitHub release or tag data was available.
## Project history and usage

install-peerdeps is a JavaScript command-line helper for installing an npm package together with its peer dependencies. It exists because npm's peer-dependency behavior made some package installs, especially linting presets, tedious to reproduce by hand.

### Project history

The GitHub repository and npm package appeared in 2016. The README explains the motivation directly: starting with npm v3.0, peer dependencies were not automatically installed on npm install, and manually assembling the matching packages was awkward.

The README presents install-peerdeps as a memorable, cross-platform replacement for shell snippets that parse npm info output. It also notes visibility from Airbnb's ESLint config README while disclaiming any affiliation with Airbnb.

The release history shows the tool adapting to package-manager churn. Version 2.x addressed registry behavior, version 3.0.0 moved toward using package-manager commands to get package info, and later 3.x releases fixed Yarn, pnpm, Windows command spawning, version-range parsing, and dependency choices.

### Adoption history

The npm registry metadata records the package from 2016 onward with dozens of published versions. Homebrew packages the npm tarball as a formula, which is notable because the project is primarily an npm CLI but also appears in a system package manager.

Adoption followed a practical JavaScript workflow need: installing packages such as eslint-config-airbnb with the exact peers listed by the package, while allowing npm, Yarn, and pnpm command paths.

### How it is used

The documented pattern is npx install-peerdeps package@version, or the Yarn and pnpm dlx equivalents. Flags control dev/global installs, installing only peers, dry runs, local node_modules lookup, and extra arguments passed through to the underlying package manager.

The canonical example installs eslint-config-airbnb and its peer ESLint plugins in one command, converting peerDependencies metadata into an install command the user can run or inspect.

### Why package nerds care

install-peerdeps is package-nerd archaeology for the npm v3 peer-dependency era. It packaged a common README workaround into a reusable executable and preserved a slice of JavaScript ecosystem pain around peerDependencies, ESLint presets, npm, Yarn, pnpm, and Windows shells.

Its significance is not algorithmic complexity; it is workflow glue. Package managers changed peer-dependency behavior, and this small CLI became a bridge for users and docs that needed reproducible peer installs.

### Timeline

- 2016: GitHub repository and npm package created.
- 2017: Early 1.x releases appear on npm.
- 2019: 2.0.0 published in the npm release stream.
- 2021: 3.0.0 published with package-manager-info changes.
- 2025: 3.0.7 released with fixes for version-range, Yarn, and option-parsing issues.

### Related projects

- install-peerdeps is related to npm, Yarn, pnpm, npx, eslint-config-airbnb, ESLint plugin packaging, peerDependencies metadata, and JavaScript package-manager compatibility tools.

### Sources

- <https://api.github.com/repos/nathanhleung/install-peerdeps/releases>
- <https://formulae.brew.sh/api/formula/install-peerdeps.json>
- <https://github.com/nathanhleung/install-peerdeps>
- <https://registry.npmjs.org/install-peerdeps>


## Security Notes

narrow executable package without higher-risk signals.

- **Geiger risk:** green / low
- narrow executable package without higher-risk signals

## Source Database Details

- **Source Database:** Homebrew formula API
- **Tap:** homebrew/core
- **Full Name:** install-peerdeps
- **Version Scheme:** 0
- **Revision:** 0
- **Bottle Stable Root URL:** <https://ghcr.io/v2/homebrew/core>
- **Deprecated:** no
- **Disabled:** no
- **Keg Only:** no
- **URL Keys:** stable


## Related links

- [Source-control packages](https://www.automicvault.com/pkg/source-control-tools/) - Belongs to a source-control command family.
- [Package publisher tools](https://www.automicvault.com/pkg/package-publishers/) - Belongs to a package publishing or registry command family.
- [Terminal utility packages](https://www.automicvault.com/pkg/terminal-utilities/) - Matched terminal and command-line workflow metadata.
- [Text processing packages](https://www.automicvault.com/pkg/text-processing-tools/) - Matched text, document, or structured-data processing metadata.
- [node](https://www.automicvault.com/pkg/brew/node/) - Runtime dependency declared by Homebrew.
- [corepack](https://www.automicvault.com/pkg/brew/corepack/) - Shares av.db curated category or tags: cli, developer-tools, javascript, npm, package-management.
- [ni](https://www.automicvault.com/pkg/brew/ni/) - Shares av.db curated category or tags: cli, developer-tools, npm, package-management, pnpm.
- [nrm](https://www.automicvault.com/pkg/brew/nrm/) - Shares av.db curated category or tags: cli, developer-tools, javascript, npm, package-management.
- [patch-package](https://www.automicvault.com/pkg/brew/patch-package/) - Shares av.db curated category or tags: cli, developer-tools, npm, package-management.
- [bower](https://www.automicvault.com/pkg/brew/bower/) - Shares av.db curated category or tags: cli, developer-tools, javascript, package-management.
- [cargo-binstall](https://www.automicvault.com/pkg/brew/cargo-binstall/) - Shares av.db curated category or tags: cli, developer-tools, package-management.
- [corral](https://www.automicvault.com/pkg/brew/corral/) - Shares av.db curated category or tags: cli, developer-tools, package-management.
- [eget](https://www.automicvault.com/pkg/brew/eget/) - Shares av.db curated category or tags: cli, developer-tools, package-management.
- [install-peerdeps](https://www.automicvault.com/pkg/npm/install-peerdeps/) - Same normalized package name appears in another local ecosystem. Shared terms: automatically, install, install-peerdeps, npm, peerdeps.
- [install-peerdeps](https://www.automicvault.com/pkg/npm/install-peerdeps/) - Same normalized package name in another local ecosystem.

## Combined YAML source

View the package source record on GitHub. [combined/install-peerdeps.yml](https://github.com/automic-vault/db/blob/main/combined/install-peerdeps.yml)


## Sources

- Nucleus package database
- Geiger risk classifier
- package-page enrichment
- curated package history
- package version freshness
- av.db category and tag curation
- package relationship graph
- cross-ecosystem install command graph
