## TL;DR

For example, say xml2js 0.2.6 (located in folder [node_modules] 3 in the current project) is outdated, because a newer version exists (0.2.7).

## Steps

1. To check if any module in a project is 'old': npm outdated ' outdated ' will check every module defined in file package.json and see if there is a newer version in the NPM registry. For example, say xml2js 0.2.6 (located in folder [node_modules] 3 in the current project) is outdated, because a newer version exists (0.2.7). You would see: xml2js@0.2.7 node_modules/xml2js current=0.2.6 To update all dependencies, if you are confident this is desirable: npm update Or, to update a single dependency, such as xml2js : npm update xml2js To update package.json version numbers, append the --save flag: npm update --save

## When to use

You are seeing this: To check if any module in a project is 'old': npm outdated ' outdated ' will check every module defined in file package.json and see if there is a newer version in the NPM registry. Use this skill when you run into "npm check and update package if needed".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

Versions mentioned in the source: xml2js 0.2.6, 0.2.7. If you are on something much newer or older, the details may have shifted.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
