Learn How to Instantly Install a Specific Version of an NPM Package!

Have you ever updated a npm package only to have your project break? Or maybe you need to work on an older project that depends on a particular version of a library. Knowing how to install a specific version npm package is a fundamental skill for any JavaScript developer to ensure project stability and consistency across different machines and environments. 

In this detailed blog, you will learn everything about managing package versions. We will cover all the different methods for installing packages, explore the core concepts of semantic versioning, and understand how package.json and package-lock.json work together to control your project's dependencies.  

JavaScript is crucial for scalable apps, and NPM helps manage dependencies. upGrad’s Software Engineering Courses provide training in JavaScript, system architecture, and core programming to build reliable software. Enroll today! 

How to Install a Specific Version of NPM Package: All the Methods 

There are several ways to specify which version of a package you want to install. The method you choose depends on how precise you need to be. Let's cover all the commands you can use. 

Improve your programming skills with courses on tools like NPM, covering techniques to manage dependencies, use AI, and build scalable applications, such as: 

• Advanced Certificate Program in Generative AI 
• Executive PG Programme in Machine Learning & AI – IIIT Bangalore 
• Professional Certificate Program in Data Science and AI 

Installing an Exact Version Number 

This is the most common and direct method. You tell npm to fetch one specific version, and it will not deviate. This is perfect for ensuring stability when you know a particular version works with your code. 

Syntax: 

Bash 
npm install <package-name>@<version-number> 
 

Example: 

To install exactly version 17.0.2 of React, you would run: 

Bash 
npm install react@17.0.2 
 

This command adds "react": "17.0.2" to your package.json, locking it to that version. 

Also Read: How to Install Dev Dependencies in npm? A Complete Guide to Dependencies & Scripts 

Installing Using Version Ranges 

Sometimes you want to allow for minor updates or bug fixes. You can do this using special characters in the version specifier. 

1. Using the Caret (^) for Minor Updates 

The caret is the default for npm install. It allows for any patch or minor updates but will not install a new major version. This is a good balance between stability and getting new features. 

• Syntax: npm install <package-name>@^<version-number> 
• Example: npm install lodash@^4.17.20 
• What it means: This will install version 4.17.20 or any later version up to, but not including, 5.0.0. So, 4.18.0 would be installed, but 5.0.0 would not. 

2. Using the Tilde (~) for Patch Updates 

The tilde is more restrictive. It only allows for patch-level updates, which are typically just for bug fixes. This is a safer, more conservative approach. 

• Syntax: npm install <package-name>@~<version-number> 
• Example: npm install lodash@~4.17.20 
• What it means: This will install version 4.17.20 or any later patch version up to, but not including, 4.18.0. It will install 4.17.21 but not 4.18.0. 

Also Read: Top 45+ Nodejs Project Ideas for Beginners and Professionals 

Installing Using Tags 

Packages often have tags, which are human-readable labels that point to a specific version. The most common tag is latest. 

• Syntax: npm install <package-name>@<tag-name> 
• Example: npm install react@latest 
• What it means: This will look up which version the latest tag points to and install it. Other common tags include beta or next for pre-release versions. 

Installing from a Git Repository 

You can also install a package directly from a Git repository, like GitHub. This is useful for installing a forked version of a package or a version that has not been published to the npm registry yet. 

• Syntax: npm install <git-remote-url> 
• Example: npm install git+https://github.com/expressjs/express.git 
• What it means: This command clones the repository and installs the package. You can even specify a particular branch or commit hash: npm install expressjs/express#main. 

Also Read: How to Use GitHub: A Beginner's Guide to Getting Started and Exploring Its Benefits in 2025 

Installing from a Local Folder or Tarball 

If you have the package code on your local machine, you can install it directly from the folder. This is great for local development and testing of packages you are creating yourself. 

• Syntax: npm install <folder-path> 
• Example: npm install ../my-local-package 
• What it means: This creates a symbolic link to your local package folder inside node_modules. Any changes you make to the local package code will be immediately reflected in your project. 

 Quick Summary Table: 

Understanding Semantic Versioning (SemVer) 

To properly install a specific version npm package, you need to understand what the version numbers mean. The npm ecosystem uses a standard called Semantic Versioning, or SemVer, which gives meaning to each number in a version like 16.8.0. 

The format is always MAJOR.MINOR.PATCH. 

• MAJOR (16.x.x): This number is incremented when an update contains breaking changes. A breaking change means the new version is not backward-compatible. If you upgrade to a new major version, you might need to update your own code to adapt to the changes. 
• MINOR (16.8.x): This number is incremented when new features are added in a backward-compatible way. Your existing code should continue to work without any changes after a minor update. 
• PATCH (16.8.0): This number is incremented for backward-compatible bug fixes. These are the safest updates, as their main purpose is to correct errors in the code. 

This system provides a clear way for package authors to communicate the impact of their changes, helping you make informed decisions about which versions to install. 

Also Read: Yarn vs NPM: Key Differences and How to Choose the Right Package Manager in 2025 

The Role of package.json and package-lock.json 

Your project's dependencies are managed by two very important files: package.json and package-lock.json. They work together to ensure your project's dependencies are both flexible and consistent. 

package.json - The Project Manifest 

This file is the main configuration file for your project. It contains important metadata, such as the project's name, version, and scripts. Its most important role in dependency management is the dependencies section. 

When you install a specific version npm package, an entry is added to this file. 

Example dependencies in package.json: 

JSON 
"dependencies": { 
 "lodash": "^4.17.21", 
 "react": "~17.0.2", 
 "moment": "2.29.4" 
} 
 

This section acts as a set of rules. It tells npm that the project is compatible with: 

• Any version of lodash from 4.17.21 up to 5.0.0. 
• Any patch version of react from 17.0.2 up to 17.1.0. 
• Exactly version 2.29.4 of moment. 

package-lock.json - The Exact Recipe 

This file is automatically generated by npm the first time you install a package. It is a much more detailed file that records the exact version of every single package and sub-package that was installed in your node_modules folder. 

Why is this file so important? 

The package-lock.json file guarantees that your project is reproducible. When another developer clones your project and runs npm install, npm will read the package-lock.json file and install the exact versions listed there, completely ignoring the version ranges in package.json. This ensures that every member of the team has the exact same set of dependencies, which prevents "it works on my machine" issues. 

You should always commit your package-lock.json file to your version control system (like Git). 

Also Read: package.json vs package-lock.json: Major Differences 

How to Find Available Versions of a Package 

Before you can decide how to install a specific version of npm package, you first need to know what your options are. NPM provides easy ways to see all the published versions of a package. 

Method 1: Using the npm view Command 

You can check for available versions directly from your command line using the npm view command (or its shorthand npm v). 

To get a full list of all available versions for a package, run: 

Bash 
npm view <package-name> versions 
 

Example: 

Bash 
npm view lodash versions 
 

This command will print out an array of strings, with every version of Lodash that has ever been published. This is helpful for finding a specific older version or checking for the latest release. 

Also read: Top Front-End Developer Interview Questions for 2025 

Method 2: Using the NPM Website 

A more user-friendly way to see available versions is to use the official npm website. 

1. Open your web browser and go to https://www.npmjs.com/. 
2. Use the search bar to find your package (e.g., "lodash"). 
3. On the package's page, click on the "Versions" tab. 

This page provides a clean, chronological list of all the package's versions, along with their publication dates. This can make it easier to find the version you are looking for. 

Managing and Updating Your Packages 

Once you have packages installed, you will also need to manage them over time. NPM provides commands to help with this. 

Checking for Outdated Packages 

To see which of your installed packages have newer versions available (based on the rules in your package.json), you can run: 

Bash 
npm outdated 
 

This command produces a table showing the current version, the wanted version (based on your package.json ranges), and the latest version available. This is a great way to see what updates are available for your project. 

Also Read: Full Stack Developer Salary in India 2025: Trends & Top Recruiters 

Updating Packages 

To update your packages to the newest versions allowed by your package.json ranges, you can run: 

Bash 
npm update 
 

This command will go through your dependencies, find newer versions that satisfy the caret (^) and tilde (~) ranges, and install them. It will also update your package-lock.json file to reflect these new versions. 

If you want to update a package to a new major version, npm update will not do it. You must do this manually by running the npm install command with the new version. For example: 

Bash 
# To upgrade React from version 17 to 18 
npm install react@18.0.0 

Conclusion 

With a solid grasp of these commands and concepts, you have complete control over your project's dependencies. The ability to install a specific version npm package is a crucial skill that ensures your applications are stable, consistent, and maintainable. 

Boost your career with our popular Software Engineering courses, offering hands-on training and expert guidance to turn you into a skilled software developer.

Master in-demand Software Development skills like coding, system design, DevOps, and agile methodologies to excel in today’s competitive tech industry.

In-Demand Software Development Skills

Stay informed with our widely-read Software Development articles, covering everything from coding techniques to the latest advancements in software engineering.

Read our Articles related to Software Development