How to fix npm ERR! code EINVALIDRANGE npm ERR! Invalid version range: ">=foo" in npm

npmBEGINNERMEDIUMUpdated Dec 6, 2025· 177 views

The EINVALIDRANGE error occurs when package.json contains a version specification that doesn't follow semver syntax. Fix malformed version ranges like '>=foo' or use proper semver format like '^1.0.0'.

Quick fix

Fixes EINVALIDRANGE

npm ERR! Invalid version range: ">=foo"
  1. Find the invalid version
  2. Use valid semver syntax
  3. Fix common mistakes
  4. Check package-lock.json
npm — error
npm ERR! Invalid version range: ">=foo"
npm ERR! code EINVALIDRANGE
npm ERR! Invalid version range: ">=foo"

What this error means

This error occurs when npm's semver parser encounters a version range that doesn't follow semantic versioning rules. Version ranges must use valid semver syntax—numbers separated by dots, optionally with range operators. Common invalid patterns include using text instead of numbers ('>=foo'), incomplete versions ('1.0' instead of '1.0.0'), or malformed range syntax ('1.0.0-2.0.0' instead of '>=1.0.0 <2.0.0'). npm uses the node-semver library to parse versions, which strictly enforces semver 2.0 specification.

Typical symptoms

  • npm install fails with 'Invalid version range' error
  • Error shows the specific malformed version string
  • npm audit crashes when encountering invalid versions
  • Package resolution fails before downloading
  • Inherited projects with old dependencies fail to install

Common causes

  1. Version range contains text instead of numbers
  2. Incomplete version format (1.0 instead of 1.0.0)
  3. Invalid range operators or syntax
  4. Corrupted package-lock.json with malformed entries
  5. Copy-paste error from documentation or other sources
  6. Git URLs or file paths in version field

How to fix "npm ERR! code EINVALIDRANGE npm ERR! Invalid version range: ">=foo""

1Find the invalid version

The error message shows exactly what's wrong:

bash
npm ERR! Invalid version range: ">=foo"

Search your package.json for this string:

bash
grep -n "foo" package.json
2Use valid semver syntax

Valid version formats:

json
{
  "dependencies": {
    "exact": "1.2.3",
    "caret": "^1.2.3",
    "tilde": "~1.2.3",
    "range": ">=1.0.0 <2.0.0",
    "or": "1.0.0 || 2.0.0",
    "any": "*",
    "latest": "latest"
  }
}

Invalid:
- ">=foo" - text instead of number
- "1.0" - missing patch version
- "v1.0.0" - leading 'v'

3Fix common mistakes

Common fixes:

json
// Wrong → Right
"1.0" → "1.0.0"
"v1.0.0" → "1.0.0"
">=1 <2" → ">=1.0.0 <2.0.0"
"1.0.0-2.0.0" → ">=1.0.0 <=2.0.0"
"latest" → "latest" // This is actually valid
4Check package-lock.json

Invalid versions can hide in the lock file:

bash
# Search for suspicious entries
grep -E '"version":\s*"[^0-9]' package-lock.json

If found, delete and regenerate:

bash
rm package-lock.json
npm install
5Use --no-audit if audit fails

Sometimes npm audit crashes on packages with historical invalid versions:

bash
npm install --no-audit

This skips the audit phase that scans all package versions.

6Validate before committing

Use a linter to catch invalid versions:

bash
npx npm-package-json-lint .

Or check specific versions:

bash
node -e "require('semver').validRange('^1.0.0')"

Advanced notes

Semver ranges in npm support complex patterns:

bash
^1.2.3 := >=1.2.3 <2.0.0 (same major)
~1.2.3 := >=1.2.3 <1.3.0 (same minor)
1.2.x  := >=1.2.0 <1.3.0
*      := >=0.0.0 (any version)

Pre-release versions have special rules:

bash
1.0.0-alpha.1 < 1.0.0-alpha.2 < 1.0.0-beta < 1.0.0

If you're using a monorepo tool like Lerna or Nx, ensure workspace protocol versions (workspace:*) are properly resolved before publishing.

For Git dependencies, use the proper URL format:

json
"git+https://github.com/user/repo.git#semver:^1.0.0"

Frequently asked questions

What does "EINVALIDRANGE" mean?
This error occurs when npm's semver parser encounters a version range that doesn't follow semantic versioning rules. Version ranges must use valid semver syntax—numbers separated by dots, optionally with range operators. 0').
How do I fix "EINVALIDRANGE"?
The EINVALIDRANGE error occurs when package.json contains a version specification that doesn't follow semver syntax. Fix malformed version ranges like '>=foo' or use proper semver format like '^1.0.0'.
What causes "EINVALIDRANGE"?
Version range contains text instead of numbers Incomplete version format (1.0 instead of 1.0.0) Invalid range operators or syntax
Is the "EINVALIDRANGE" error serious?
It is a medium-severity error — more of a blocker than a risk. The steps above resolve it.

Official resources & further reading