Cannot find module 'core-util-is' after running gulp and bower install

[amite]

When I run gulp I get this error:

   Cannot find module 'core-util-is'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (/Users/amiterandole/Documents/current/webdev/angulpify/node_modules/gulp-if/node_modules/through2/node_modules/readable-stream/lib/_stream_duplex.js:39:12)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)

[jgoux]

I never encountered this error.
Could you determine which npm dependencie triggers it ?
You can try to scaffold the project with the --skip-install option.
Then you can look at the dependencies inside the package.jsonfile and try to install them one by one, for example : npm install yargs.
Sorry I can't help you more on this.

[jgoux]

Hey @amite , did you figure out where the bug comes from ? I'm sorry I can't reproduce it.

[jgoux]

I'm closing it for now, @amite if you still have this issue you can reopen it!

[iongion]

This happens when you abruptly terminate npm install :), just noted it here for ones that get burned by impatience

[jgoux]

Thanks for the tip @iongion !

[ANiedritis]

"Then you can look at the dependencies inside the package.jsonfile and try to install them one by one, for example : npm install yargs."

Yep, got the same error because of my impatience, and this did fix this error.

[mnpenner]

I just hit this error. Try nuking your node_modules directory and re-installing (npm install).

[Dynom]

I had this error too. I ran a npm install in a docker container. This probably has no relation but it's a pain to sort everything out when you have a gazillion (recursive) npm packages.

[andrewluetgers]

had same problem after nuking project node_modules. A clean install after to require nuking both the project and global node_modules folders did the trick.

[kdcllc]

I used VS.NET 2015 and my project experienced this problem so I deleted npm cache that is specific to the project and was able to user Task Runner Explore (TRE) within the project. Visual Studio.NET 2015 by default downloads all of the dependencies when TRE is open.