Dependency Upgrade Strategies for Node.js Projects (npm, pnpm, yarn)

In Node.js projects, checking and upgrading dependencies are routine operations for maintenance. Below are detailed solutions for the three major package managers `npm`, `pnpm`, and `yarn`, along with recommended third-party tools.

## 1. Check Installed Dependencies

If you want to view what packages and versions are installed in your project:

| **Tool** | **Command**              | **Description**                        |
| -------- | ------------------------ | -------------------------------------- |
| **npm**  | `npm ls --depth=0`       | Lists top-level dependency versions.  |
| **pnpm** | `pnpm ls`                | Lists top-level dependencies by default, very clear. |
| **yarn** | `yarn list --depth=0`    | Lists installed dependency tree (commonly used in v1). |

> **Tip:** If you want to see why a specific package was installed (dependency chain), use `npm why <package-name>` or `pnpm why <package-name>`.

## 2. Check Upgradable Dependencies (Native Solutions)

The built-in `outdated` command in native tools compares versions in `package.json` with the remote repository's latest versions.

### Output typically includes:

- **Current**: Currently installed version.
- **Wanted**: Highest version matching the semantic version range in `package.json` (e.g., `^1.0.0`).
- **Latest**: Latest version available in the remote repository (may include major version updates).

#### Commands for each tool:

- **npm**: `npm outdated`
- **pnpm**: `pnpm outdated`
- **yarn**: `yarn outdated`

## 3. Dependency Upgrade Strategies

### Strategy A: Safe Upgrade (Upgrade to Wanted Version)

This usually involves patch (Patch) or minor version (Minor) updates, carries low risk, and won't modify version ranges in `package.json`.

- **npm**: `npm update`
- **pnpm**: `pnpm up`
- **yarn**: `yarn upgrade`

### Strategy B: Complete Upgrade (Upgrade to Latest Version)

If you want to ignore `^` or `~` constraints and upgrade directly to the latest version (may involve breaking changes), use these interactive commands:

#### **pnpm (Most Recommended)**

pnpm provides a user-friendly interactive interface:

```Bash
pnpm up -i --latest
```

*This will pop up a list where you can select packages to upgrade using space key, very intuitive.*

#### **Yarn**

```Bash
yarn upgrade-interactive --latest
```

#### **npm (Requires Third-party Tool)**

npm's native support for "one-click upgrade to latest" is limited. **`npm-check-updates` (ncu)** is commonly recommended.

## 4. Ultimate Tool: npm-check-updates (ncu)

This is currently the most universal cross-platform solution supporting npm/pnpm/yarn. It can directly modify version numbers in `package.json` to latest versions.

1. **Check updates**:

   ```Bash
   npx npm-check-updates
   ```

2. **Batch update package.json**:

   ```Bash
   npx npm-check-updates -u
   ```

3. **Install updates**:

   After modifying `package.json`, run `npm install` or `pnpm install` based on your tool.

## Summary and Recommendations

1. **Routine checks**: Use `pnpm outdated` or `npm outdated`.
2. **Interactive quick upgrades**: Recommended `pnpm up -i --latest`.
3. **Bulk powerful upgrades**: Use `ncu -u`.
4. **Safety note**: After major version (Major) upgrades, always run unit tests to prevent project crashes caused by API changes in dependencies.