https://github.com/privatenumber/i-peers
npx package to install local peer-dependencies
https://github.com/privatenumber/i-peers
install npm npm-install-peers npx peerdependencies
Last synced: 7 months ago
JSON representation
npx package to install local peer-dependencies
- Host: GitHub
- URL: https://github.com/privatenumber/i-peers
- Owner: privatenumber
- License: mit
- Created: 2018-09-06T20:07:16.000Z (about 7 years ago)
- Default Branch: develop
- Last Pushed: 2020-10-13T04:11:45.000Z (about 5 years ago)
- Last Synced: 2025-03-18T16:04:11.471Z (8 months ago)
- Topics: install, npm, npm-install-peers, npx, peerdependencies
- Language: JavaScript
- Homepage:
- Size: 14.6 KB
- Stars: 7
- Watchers: 2
- Forks: 1
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# i-peers [](https://npm.im/i-peers) [](https://npm.im/i-peers) [](https://packagephobia.now.sh/result?p=i-peers)
Zero-dependency CLI to install your peer-dependencies.
👉 Run it in your project directory:
```sh
npx i-peers
```
## 🙋♂️ Why?
- **⚡️ Blazing fast** Has no dependencies and is optimized for npx!
- **🔥 Uses your npm** and doesn't install one!
- **🐥 Tiny** `469 B` minzipped!
## ⚙️ Options
- `-a` Install all dependencies
- `-a ci` Installs all dependencies with `npm ci`
## 💁♀️ FAQ
### When would I use this?
In rare instances where you have peer-dependencies that you can't declare as dev-dependencies. For example, when the peer-dependency is propietary and can only be installed behind a fire-wall (eg. private npm registry), declaring it as a dev-dependency might cause your CI to fail at `npm install`.
### How is this different from [npm-install-peers](https://github.com/spatie/npm-install-peers)?
They accomplish the same task, but `i-peers` is dramatically lighter, and therefore, faster.
The latest version of `npm-install-peers` 
vs `i-peers` 