How do you switch between pnpm versions?

When facing the need to switch between different versions of PNPM, you can leverage effective tools and strategies to manage this process. I will briefly introduce several commonly used methods to achieve this goal, along with examples.

1. Using NVM (Node Version Manager)

NVM is a popular Node.js version management tool that can indirectly help manage different versions of PNPM, as PNPM's operation depends on the Node.js version. Using NVM allows you to easily switch Node.js versions, thereby indirectly switching or reinstalling different versions of PNPM.

Installing NVM:

bash
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.0/install.sh | bash

Installing and Using a Specific Node.js Version with NVM:

bash
nvm install 14
nvm use 14

Installing PNPM under this Node.js version:

bash
npm install -g pnpm

2. Using PNPM's Built-in Version Management Feature

Starting from PNPM version 6.10.0, PNPM supports built-in version management, allowing users to conveniently switch between different PNPM versions. The pnpm env command can manage different Node.js and PNPM environments.

Listing all available PNPM versions:

bash
pnpm env list --available

Using a specific PNPM version:

bash
pnpm env use --pnpm <version>

3. Using Volta

Volta is another modern tool designed specifically for managing versions of JavaScript command-line tools and libraries, including Node.js and package managers like PNPM.

Installing Volta:

bash
curl https://get.volta.sh | bash

Installing and Using a Specific PNPM Version with Volta:

bash
volta install pnpm@6.14.2

Example

Suppose we are using PNPM version 6.14.2 in a project and suddenly need to switch to 5.18.9 to test for downward compatibility issues. We can use Volta to achieve a quick switch:

bash
volta install pnpm@5.18.9

After switching, running pnpm --version should display 5.18.9, indicating that we have successfully switched to the older version.

These are the different methods and tools to switch and manage different versions of PNPM. The choice of method depends on personal or project requirements, as well as your preferred tooling.

PNPM (Performant NPM) is an effective package manager for handling dependencies in JavaScript projects, similar to npm and Yarn. In PNPM, if you want to switch between different versions of packages in your project, there are typically several approaches:

1. Using the pnpm add command to specify a version

When adding a specific version of a package to your project, use the pnpm add command with the version number. For example:

sh
pnpm add lodash@4.17.15

This installs version 4.17.15 of the lodash package.

2. Modifying the package.json file

Specify the required package version directly in the project's package.json file, then run pnpm install. For example:

json
{
  "dependencies": {
    "lodash": "4.17.15"
  }
}

After modifying package.json, execute the following command to install the specified dependencies:

sh
pnpm install

3. Using .npmrc or pnpm-workspace.yaml configuration files (for workspaces)

When working with PNPM workspaces (monorepo), specify a particular package version in the .npmrc or pnpm-workspace.yaml file.

In the .npmrc file, add the following configuration to fix a specific version:

plaintext
lodash=4.17.15

In the pnpm-workspace.yaml file, specify it as:

yaml
packages:
  - 'packages/*'

dependencies:
  lodash: 4.17.15

4. Using the pnpm update command to update versions

To update a package to its latest version or a specific version range, use the pnpm update command. For example:

sh
# Update to the latest version
pnpm update lodash

# Update to a specific version range
pnpm update lodash@^4.17.0

This updates lodash to the latest version or the latest version within the ^4.17.0 range.

5. Using version management tools

For large-scale projects or multiple projects, more complex version management strategies may be needed. In such cases, use tools like nvm (Node Version Manager) to manage Node.js versions across projects, as different Node.js versions may include or be compatible with various package manager versions.

These are common methods for switching package versions in PNPM. In practice, selecting the most appropriate method based on project requirements and team workflows is essential for effective version management.