Question

How do I install a specific version of a package using npm?

Answer and Explanation

You can install a specific version of a package using npm by specifying the version number along with the package name during the installation process. Here’s how to do it:

1. Basic Syntax:

The general syntax for installing a specific package version is:

npm install package-name@version-number

Replace package-name with the actual name of the npm package you want to install, and replace version-number with the specific version you need.

2. Examples:

- Installing a Specific Version:

To install version 2.2.0 of a package named 'lodash', you would use the following command:

npm install lodash@2.2.0

- Installing the Latest Version of a Major Release:

To install the latest version within a specific major release (e.g., the latest version in the 2.x.x series), you can use:

npm install lodash@2

- Installing the Latest Version of a Minor Release:

To install the latest version within a specific minor release (e.g., the latest version in the 2.2.x series), use:

npm install lodash@2.2

- Using a Tag:

Some packages use tags like ‘latest’ , ‘next’ or ‘beta’. To install a specific tag you can use:

npm install package-name@tag

For example to install the beta version, if available, use npm install lodash@beta

3. Checking Installed Version:

After installation, you can check the installed version in your package.json or by using:

npm list package-name

4. Version Ranges and Specifiers:

npm also supports version ranges and specifiers in the package.json file like using caret ^ or tilde ~ allowing for updates within a range of versions. However, for explicit installation, you should use the exact version.

5. Package-lock.json:

- Ensure that you have a package-lock.json file if you are working on a project. This file helps guarantee the specific versions are maintained across different development environments. After installing a specific version, update the package-lock.json by running npm install again, to ensure your dependencies are correctly saved.

By using the method described above, you can precisely manage package versions for your projects, and avoid compatibility issues that might arise with newer updates.

More questions