Course contentsShow
← JavaScript
Lesson 2493 of 2,72351. Package ManagementFree lesson

npm outdated and Version Checking

Checking which installed packages have newer versions available.

npm outdated and Version Checking

What you'll learn: How to identify which of your installed packages have newer versions available so you can decide whether to update them.

Why Check for Outdated Packages?

Packages evolve constantly—bug fixes, security patches, and new features are released regularly. Just because you installed a package yesterday doesn't mean you have the latest version today. You need a way to see what's changed since your last installation without manually visiting each package's page.

The npm outdated Command

Running npm outdated in your project directory displays a table of all packages that have newer versions available:

npm outdated

This shows you four key columns:

  • Package: The package name
  • Current: The version you have installed in node_modules
  • Wanted: The latest version that satisfies your package.json version range (e.g., if you specified ^1.2.0, it might show 1.5.0 but not 2.0.0)
  • Latest: The absolute newest published version, regardless of your version constraints

Reading the Output

If a package appears in the output, it means there's a newer version available. The color coding (when supported) helps too: yellow typically means a minor/patch update is available, red means a major version is available.

This command doesn't modify anything—it's purely informational. You can then decide whether to run npm update (updates to "Wanted" versions) or manually change version ranges in package.json and reinstall.

Practical Use

Regularly running npm outdated helps you stay current with security fixes and improvements while being aware of potentially breaking major updates before installing them.

Key Takeaway: npm outdated gives you a snapshot of available package updates, showing current, wanted, and latest versions so you can make informed decisions about updating dependencies.