NPM - Cannot read property "match" of undefined

When trying to run an npm command, you can’t install the packages, you may get the error:

 stephen  ~/_coding/remine/revolution   master  👉 npm run setup

> revolution@0.0.1 setup /Users/stephen/_coding/remine/revolution
> lerna link && lerna bootstrap

lerna notice cli v3.15.0
lerna info Symlinking packages and binaries
lerna notice cli v3.15.0
lerna info Bootstrapping 6 packages
lerna info Installing external dependencies
lerna ERR! npm install exited 1 in '@revolution/web'
lerna ERR! npm install stderr:
npm ERR! Cannot read property 'match' of undefined

npm ERR! A complete log of this run can be found in:
npm ERR! /Users/stephen/.npm/_logs/2019-10-11T17_31_46_811Z-debug.log

lerna ERR! npm install exited 1 in '@revolution/web'
lerna WARN complete Waiting for 5 child processes to exit. CTRL-C to exit immediately.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! revolution@0.0.1 setup: `lerna link && lerna bootstrap`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the revolution@0.0.1 setup script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /Users/stephen/.npm/_logs/2019-10-11T17_31_46_935Z-debug.log

While not a root-cause solution, a workaround is:

1. Delete node_modules and package-lock.json
2. Run npm install again

Comments

[Jacob Evans]

I like it, making articles that are little like StackOverflow questions/answers

[Stephen Charles Weiss]

Exactly!

[apalumbo]

Removing package-lock.json looks like an atomic bomb ;-), you can have issues later on ci/cd or other devs envs IMHO. Clearing npm cache should be ok , like @henriquesath said
npm cache clean --force

[Warren Gates]

This work temporarily, but it happens everytime I npm install, how do I prevent this from happening every time?

[Henrique Sathler]

Try "npm cache clean --force"

[Tran Thuy Oanh]

nice