Tool <code>ni</code> is a utility that removes the need to recognize a type of package manager in JS projects (npm, yarn, pnpm, bun). It provides a unified interface and uses appropriate commands instead (calls <code>yarn</code> in yarn projects, <code>npm</code> in npm projects, etc.).
Let's assume getting a project with an unknown manager (at least for the first 5 seconds) or just a situation when we work with multiple projects having different managers. It may become a little bit annoying to pay attention to which manager we need.
The <code>ni</code> is a CLI utility that recognizes a project package manager according to its lock file (<code>yarn.lock</code>, <code>package-lock.json</code>, etc.) and uses appropriate commands. At least basic ones that could be unified.
<h2 id="heading-installation">Installation</h2>
<pre><code class="lang-bash">npm i -g @antfu/ni
</code></pre>
Also, it is better to create a config <code>~/.nirc</code> with default values.
<pre><code class="lang-bash">defaultAgent=npm
globalAgent=npm
</code></pre>
<h2 id="heading-usage">Usage</h2>
Examples below are based on the <code>yarn</code> commands.
<pre><code class="lang-bash">ni # yarn install
ni X # yarn add X
ni -D X # yarn add -D X
nr dev # yarn run dev
na # yarn
</code></pre>
A full list is defined at <a target="_blank" href="https://github.com/antfu-collective/ni">README.md</a> of the library.
It is nothing too special, but it removes a tiny annoying part during app development.

*Tool* `ni` *is a utility that removes the need to recognize a type of package manager in JS projects (npm, yarn, pnpm, bun). It provides a unified interface and uses appropriate commands instead (calls* `yarn` in yarn projects, `npm` in npm projects, etc.*).*

Let's assume getting a project with an unknown manager (at least for the first 5 seconds) or just a situation when we work with multiple projects having different managers. It may become a little bit annoying to pay attention to which manager we need.

The `ni` is a CLI utility that recognizes a project package manager according to its lock file (`yarn.lock`, `package-lock.json`, etc.) and uses appropriate commands. At least basic ones that could be unified.

## Installation

```bash
npm i -g @antfu/ni
```

Also, it is better to create a config `~/.nirc` with default values.

```bash
defaultAgent=npm
globalAgent=npm
```

## Usage

Examples below are based on the `yarn` commands.

```bash
ni      # yarn install
ni X    # yarn add X
ni -D X # yarn add -D X
nr dev  # yarn run dev
na      # yarn
```

A full list is defined at [README.md](https://github.com/antfu-collective/ni) of the library.

It is nothing too special, but it removes a tiny annoying part during app development.

Tool ni is a utility that removes the need to recognize a type of manager in JS apps. It provides a unified interface and uses appropriate commands instead.

Cheat Sheet: ni - universal CLI alias for npm/yarn/pnpm/bun

Installation

Usage