New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: Cannot find module 'internal/fs' when npm install on mac #9377

Closed
shufanshijie opened this Issue Oct 31, 2016 · 95 comments

Comments

Projects
None yet
@shufanshijie

shufanshijie commented Oct 31, 2016

5 verbose stack Error: Cannot find module 'internal/fs'
5 verbose stack     at Function.Module._resolveFilename (module.js:472:15)
5 verbose stack     at Function.Module._load (module.js:420:25)
5 verbose stack     at Module.require (module.js:500:17)
5 verbose stack     at require (internal/module.js:20:19)
5 verbose stack     at evalmachine.<anonymous>:17:20
5 verbose stack     at Object.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/cmd-shim/node_modules/graceful-fs/fs.js:11:1)
5 verbose stack     at Module._compile (module.js:573:32)
5 verbose stack     at Object.Module._extensions..js (module.js:582:10)
5 verbose stack     at Module.load (module.js:490:32)
5 verbose stack     at tryModuleLoad (module.js:449:12)
6 verbose cwd /Users/huweiqing
7 error Darwin 14.5.0
8 error argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "iconv-lite"
9 error node v7.0.0
10 error npm  v3.10.8
11 error code MODULE_NOT_FOUND
12 error Cannot find module 'internal/fs'
@cjihrig

This comment has been minimized.

Show comment
Hide comment
@cjihrig

cjihrig Oct 31, 2016

Contributor

Hm, can you read over the discussion in #9355.

Contributor

cjihrig commented Oct 31, 2016

Hm, can you read over the discussion in #9355.

@Fishrock123

This comment has been minimized.

Show comment
Hide comment
@Fishrock123

Fishrock123 Oct 31, 2016

Member

I'm getting a #3606 vibe from these. Smells like an installer problem.

Member

Fishrock123 commented Oct 31, 2016

I'm getting a #3606 vibe from these. Smells like an installer problem.

@Fishrock123

This comment has been minimized.

Show comment
Hide comment
@Fishrock123

Fishrock123 Oct 31, 2016

Member

@shufanshijie

What is the output of node -v and npm -v?
How did you install Node.js?

Member

Fishrock123 commented Oct 31, 2016

@shufanshijie

What is the output of node -v and npm -v?
How did you install Node.js?

@Fishrock123

This comment has been minimized.

Show comment
Hide comment
@Fishrock123

Fishrock123 Oct 31, 2016

Member

If you run rm -rf /usr/local/lib/node_modules/npm and then re-install Node.js does it work?

Member

Fishrock123 commented Oct 31, 2016

If you run rm -rf /usr/local/lib/node_modules/npm and then re-install Node.js does it work?

@addaleax addaleax added the npm label Oct 31, 2016

@thefourtheye

This comment has been minimized.

Show comment
Hide comment
@thefourtheye

thefourtheye Oct 31, 2016

Contributor

Unable to reproduce the problem.

➜  ~ node -v
v7.0.0
➜  ~ npm -v
3.10.8
➜  ~ uname -v
Darwin Kernel Version 15.6.0: Thu Sep  1 15:01:16 PDT 2016; root:xnu-3248.60.11~2/RELEASE_X86_64
➜  ~ npm i iconv-lite
/Users/thefourtheye
└── iconv-lite@0.4.13

Could be because of the stale npm installation, but not sure how that could have happened though. Please try what @Fishrock123 suggested above.

Contributor

thefourtheye commented Oct 31, 2016

Unable to reproduce the problem.

➜  ~ node -v
v7.0.0
➜  ~ npm -v
3.10.8
➜  ~ uname -v
Darwin Kernel Version 15.6.0: Thu Sep  1 15:01:16 PDT 2016; root:xnu-3248.60.11~2/RELEASE_X86_64
➜  ~ npm i iconv-lite
/Users/thefourtheye
└── iconv-lite@0.4.13

Could be because of the stale npm installation, but not sure how that could have happened though. Please try what @Fishrock123 suggested above.

@giulio-sefaira

This comment has been minimized.

Show comment
Hide comment
@giulio-sefaira

giulio-sefaira Nov 1, 2016

Same problem for me on a MacOsX Sierra:

$ uname -v
Darwin Kernel Version 16.1.0: Thu Oct 13 21:26:57 PDT 2016; root:xnu-3789.21.3~60/RELEASE_X86_64
$ node -v
v7.0.0
$ npm -v
3.10.8

I tried to uninstall / reinstall, but it didn't fix the problem

giulio-sefaira commented Nov 1, 2016

Same problem for me on a MacOsX Sierra:

$ uname -v
Darwin Kernel Version 16.1.0: Thu Oct 13 21:26:57 PDT 2016; root:xnu-3789.21.3~60/RELEASE_X86_64
$ node -v
v7.0.0
$ npm -v
3.10.8

I tried to uninstall / reinstall, but it didn't fix the problem

@gibfahn

This comment has been minimized.

Show comment
Hide comment
@gibfahn

gibfahn Nov 1, 2016

Member

@shufanshijie @giulio-sefaira How did you install node? With brew or nvm? Or directly from https://nodejs.org/en/download/ ?

Member

gibfahn commented Nov 1, 2016

@shufanshijie @giulio-sefaira How did you install node? With brew or nvm? Or directly from https://nodejs.org/en/download/ ?

@giulio-sefaira

This comment has been minimized.

Show comment
Hide comment
@giulio-sefaira

giulio-sefaira Nov 1, 2016

hi @gibfahn . I used brew. I uninstalled node, wiped entirely the node_modules library (rm -rf /usr/local/lib/node_modules) and reinstalled by brew

giulio-sefaira commented Nov 1, 2016

hi @gibfahn . I used brew. I uninstalled node, wiped entirely the node_modules library (rm -rf /usr/local/lib/node_modules) and reinstalled by brew

@OnceMore2020

This comment has been minimized.

Show comment
Hide comment
@OnceMore2020

OnceMore2020 Nov 1, 2016

I tried to reinstall node with brew and delete entire /usr/local/lib/node_modules, the error still happens.

OnceMore2020 commented Nov 1, 2016

I tried to reinstall node with brew and delete entire /usr/local/lib/node_modules, the error still happens.

@Fishrock123

This comment has been minimized.

Show comment
Hide comment
@Fishrock123

Fishrock123 Nov 1, 2016

Member

@giulio-sefaira @OnceMore2020 could you please run which npm?

Member

Fishrock123 commented Nov 1, 2016

@giulio-sefaira @OnceMore2020 could you please run which npm?

@giulio-sefaira

This comment has been minimized.

Show comment
Hide comment
@giulio-sefaira

giulio-sefaira Nov 1, 2016

@Fishrock123

$ which npm
npm is /usr/local/bin/npm
npm is /usr/local/bin/npm
npm is /usr/local/bin/npm

giulio-sefaira commented Nov 1, 2016

@Fishrock123

$ which npm
npm is /usr/local/bin/npm
npm is /usr/local/bin/npm
npm is /usr/local/bin/npm
@giulio-sefaira

This comment has been minimized.

Show comment
Hide comment
@giulio-sefaira

giulio-sefaira Nov 1, 2016

$ /usr/local/bin/npm -v 3.10.8

giulio-sefaira commented Nov 1, 2016

$ /usr/local/bin/npm -v 3.10.8

@Leolik

This comment has been minimized.

Show comment
Hide comment
@Leolik

Leolik Nov 1, 2016

get this error in Ubuntu 16.04
node -v = v7.0.0
npm -v = 3.10.8

Leolik commented Nov 1, 2016

get this error in Ubuntu 16.04
node -v = v7.0.0
npm -v = 3.10.8

@gibfahn

This comment has been minimized.

Show comment
Hide comment
@gibfahn

gibfahn Nov 1, 2016

Member

@Leolik How did you install node?

Member

gibfahn commented Nov 1, 2016

@Leolik How did you install node?

@Leolik

This comment has been minimized.

Show comment
Hide comment
@Leolik

Leolik Nov 1, 2016

@gibfahn sudo n latest
but after reading #9355 and removing /usr/local/lib/node_modules/ - error not reproduced

Leolik commented Nov 1, 2016

@gibfahn sudo n latest
but after reading #9355 and removing /usr/local/lib/node_modules/ - error not reproduced

@fane89

This comment has been minimized.

Show comment
Hide comment
@fane89

fane89 Nov 2, 2016

Also after removing /usr/local/lib/node_modules/ and the local project node_modules - error gone.

fane89 commented Nov 2, 2016

Also after removing /usr/local/lib/node_modules/ and the local project node_modules - error gone.

@gabrielperales

This comment has been minimized.

Show comment
Hide comment
@gabrielperales

gabrielperales Nov 2, 2016

I solved this issue thanks to the answer of @Leolik and @fane89

gabrielperales commented Nov 2, 2016

I solved this issue thanks to the answer of @Leolik and @fane89

@spelunk

This comment has been minimized.

Show comment
Hide comment
@spelunk

spelunk Nov 2, 2016

I ran into this problem too, but was able to resolve it by rolling back to an older version of node/npm and forcing a "flush" of the npm module:

$ sudo n 6.
$ sudo npm install -g npm@3.10.0
$ sudo npm install -g npm@next
$ sudo n 7.

spelunk commented Nov 2, 2016

I ran into this problem too, but was able to resolve it by rolling back to an older version of node/npm and forcing a "flush" of the npm module:

$ sudo n 6.
$ sudo npm install -g npm@3.10.0
$ sudo npm install -g npm@next
$ sudo n 7.
@Swelly

This comment has been minimized.

Show comment
Hide comment
@Swelly

Swelly Nov 3, 2016

Using Mac OS Sierra and installed Node + npm via Homebrew.

This is still not functional for me. I've gone through the thread and continue to have:

Cannot find module 'internal/fs'

verbose cli 'install' ]
2 info using npm@3.3.8
3 info using node@v7.0.0
4 verbose stack Error: Cannot find module 'internal/fs'

I've removed /usr/local/lib/node_modules/ and reinstalled node etc etc. to no avial @giulio-sefaira are you in the clear yet?

Swelly commented Nov 3, 2016

Using Mac OS Sierra and installed Node + npm via Homebrew.

This is still not functional for me. I've gone through the thread and continue to have:

Cannot find module 'internal/fs'

verbose cli 'install' ]
2 info using npm@3.3.8
3 info using node@v7.0.0
4 verbose stack Error: Cannot find module 'internal/fs'

I've removed /usr/local/lib/node_modules/ and reinstalled node etc etc. to no avial @giulio-sefaira are you in the clear yet?

@addaleax

This comment has been minimized.

Show comment
Hide comment
@addaleax

addaleax Nov 3, 2016

Member

Since I assume this kind of thing is also popping up on the npm issue tracker… @nodejs/npm @KenanY do you know what’s up with this?

Member

addaleax commented Nov 3, 2016

Since I assume this kind of thing is also popping up on the npm issue tracker… @nodejs/npm @KenanY do you know what’s up with this?

@MylesBorins

This comment has been minimized.

Show comment
Hide comment
@MylesBorins

MylesBorins Nov 3, 2016

Member

@Swelly did you install npm separately from node? Node v7 comes shipped with npm v3.10.8 and a fresh install of node with homebrew should be coming with that version.

what does which npm show?

Member

MylesBorins commented Nov 3, 2016

@Swelly did you install npm separately from node? Node v7 comes shipped with npm v3.10.8 and a fresh install of node with homebrew should be coming with that version.

what does which npm show?

@othiym23

This comment has been minimized.

Show comment
Hide comment
@othiym23

othiym23 Nov 3, 2016

Contributor

@thealphanerd The reason that this happens is that the Node installer doesn't remove /usr/local/lib/node_modules/npm before installing the new version, so if somebody has a version of npm installed that's old enough that it doesn't include the fixed graceful-fs (somewhere / anywhere) in its own install tree, it's possible, in some cases, for the new install to end up using a stale old version of graceful-fs.

There's no easy way for npm to work around this itself without doing some super hacky stuff in a postinstall script, and the fix to the installer, as described above, should be pretty simple, so is there any way we can work to get it fixed there?

Contributor

othiym23 commented Nov 3, 2016

@thealphanerd The reason that this happens is that the Node installer doesn't remove /usr/local/lib/node_modules/npm before installing the new version, so if somebody has a version of npm installed that's old enough that it doesn't include the fixed graceful-fs (somewhere / anywhere) in its own install tree, it's possible, in some cases, for the new install to end up using a stale old version of graceful-fs.

There's no easy way for npm to work around this itself without doing some super hacky stuff in a postinstall script, and the fix to the installer, as described above, should be pretty simple, so is there any way we can work to get it fixed there?

@MylesBorins

This comment has been minimized.

Show comment
Hide comment
@MylesBorins

MylesBorins Nov 3, 2016

Member

@othiym23 the user above said that they installed via homebrew not our installer.. which I just tested and it does in fact uninstall the npm directory before it installs.

I have an old branch where I tried to get an rm -rf /usr/local/lib/node_modules/npm working in the installer but could never get it to work
https://github.com/thealphanerd/node/tree/rimraf-npm

edit: I lied the above branch was doing the rm -rf in the make file... I also had done some work on the installer but can't find it

Member

MylesBorins commented Nov 3, 2016

@othiym23 the user above said that they installed via homebrew not our installer.. which I just tested and it does in fact uninstall the npm directory before it installs.

I have an old branch where I tried to get an rm -rf /usr/local/lib/node_modules/npm working in the installer but could never get it to work
https://github.com/thealphanerd/node/tree/rimraf-npm

edit: I lied the above branch was doing the rm -rf in the make file... I also had done some work on the installer but can't find it

@othiym23

This comment has been minimized.

Show comment
Hide comment
@othiym23

othiym23 Nov 3, 2016

Contributor

@othiym23 the user above said that they installed via homebrew not our installer.. which I just tested and it does in fact uninstall the npm directory before it installs.

It hasn't always, and in any case it puts each version of npm in its own Cellar/npm/<version> directory, so that's probably something else going on. The only versions of graceful-fs available to npm are all new enough to not rely on internals:

npm@4.0.1 /Users/ogd/Documents/projects/npm/npm
├── graceful-fs@4.1.9
└─┬ tap@7.1.2
  └─┬ nyc@7.1.0
    └─┬ caching-transform@1.0.1
      └─┬ write-file-atomic@1.1.4
        └── graceful-fs@4.1.4

(That nyc dep is kinda dodgy, but it's a devDependency that won't get installed on a client machine.)

I can confirm with total certainty that this is a reproducible problem with the way the Node installer works, though. So at least that part is within our control to fix, and it should be. This regularly causes problems for npm users aside from this one, although I'm blanking at the moment on the last time we saw this.

Contributor

othiym23 commented Nov 3, 2016

@othiym23 the user above said that they installed via homebrew not our installer.. which I just tested and it does in fact uninstall the npm directory before it installs.

It hasn't always, and in any case it puts each version of npm in its own Cellar/npm/<version> directory, so that's probably something else going on. The only versions of graceful-fs available to npm are all new enough to not rely on internals:

npm@4.0.1 /Users/ogd/Documents/projects/npm/npm
├── graceful-fs@4.1.9
└─┬ tap@7.1.2
  └─┬ nyc@7.1.0
    └─┬ caching-transform@1.0.1
      └─┬ write-file-atomic@1.1.4
        └── graceful-fs@4.1.4

(That nyc dep is kinda dodgy, but it's a devDependency that won't get installed on a client machine.)

I can confirm with total certainty that this is a reproducible problem with the way the Node installer works, though. So at least that part is within our control to fix, and it should be. This regularly causes problems for npm users aside from this one, although I'm blanking at the moment on the last time we saw this.

@MylesBorins

This comment has been minimized.

Show comment
Hide comment
@MylesBorins

MylesBorins Nov 3, 2016

Member

@othiym23 so the main issue I ran into was trying to remove things in /usr/local/ with the installer... during the install phase it has admin privileges, but I could not figure out how to get it to remove

has to be fixed around https://github.com/nodejs/node/blob/master/tools/osx-pkg.pmdoc/02npm.xml#L8-L9

I can dig into this again tomorrow

Member

MylesBorins commented Nov 3, 2016

@othiym23 so the main issue I ran into was trying to remove things in /usr/local/ with the installer... during the install phase it has admin privileges, but I could not figure out how to get it to remove

has to be fixed around https://github.com/nodejs/node/blob/master/tools/osx-pkg.pmdoc/02npm.xml#L8-L9

I can dig into this again tomorrow

@evanlucas

This comment has been minimized.

Show comment
Hide comment
@evanlucas

evanlucas Nov 3, 2016

Member

I'll dig in again too. I have some ideas on how we can do this.

Member

evanlucas commented Nov 3, 2016

I'll dig in again too. I have some ideas on how we can do this.

@balinterdi

This comment has been minimized.

Show comment
Hide comment
@balinterdi

balinterdi May 10, 2017

In my case the solution mentioned by @kriskhaira did not work. Since I couldn't upgrade the graceful-fs dependencies I ended up downgrading to node 6 which fixed the issue.

balinterdi commented May 10, 2017

In my case the solution mentioned by @kriskhaira did not work. Since I couldn't upgrade the graceful-fs dependencies I ended up downgrading to node 6 which fixed the issue.

@pmc-a

This comment has been minimized.

Show comment
Hide comment
@pmc-a

pmc-a May 29, 2017

Seen this issue with v7.10.0, solution was downgrading to v6.10.3 like @balinterdi mentioned. Also needed to remove node_modules and reinstall.

pmc-a commented May 29, 2017

Seen this issue with v7.10.0, solution was downgrading to v6.10.3 like @balinterdi mentioned. Also needed to remove node_modules and reinstall.

@adamreisnz

This comment has been minimized.

Show comment
Hide comment
@adamreisnz

adamreisnz May 31, 2017

Ran into this issue when using lerna bootstrap. Nothing suggested here was feasible or worked, so in the end the simple solution was to use yarn instead via lerna bootstrap --npm-client=yarn

This was with Node 8 and npm 5 btw.

adamreisnz commented May 31, 2017

Ran into this issue when using lerna bootstrap. Nothing suggested here was feasible or worked, so in the end the simple solution was to use yarn instead via lerna bootstrap --npm-client=yarn

This was with Node 8 and npm 5 btw.

@haleyparty

This comment has been minimized.

Show comment
Hide comment
@haleyparty

haleyparty Jun 1, 2017

Also ran into this issue when on Node 8. Set my nvm to v6.10.3 fixed the issue.

haleyparty commented Jun 1, 2017

Also ran into this issue when on Node 8. Set my nvm to v6.10.3 fixed the issue.

@TimothyGu

This comment has been minimized.

Show comment
Hide comment
@TimothyGu

TimothyGu Jun 1, 2017

Member

@adamreisnz @haleyparty Could (one of) you create a new issue with full stack trace? Thanks!

Member

TimothyGu commented Jun 1, 2017

@adamreisnz @haleyparty Could (one of) you create a new issue with full stack trace? Thanks!

@haleyparty

This comment has been minimized.

Show comment
Hide comment
@haleyparty

haleyparty commented Jun 1, 2017

@TimothyGu Will do now!

@TimothyGu

This comment has been minimized.

Show comment
Hide comment
@TimothyGu

TimothyGu Jun 1, 2017

Member

For posterity: #13361

Member

TimothyGu commented Jun 1, 2017

For posterity: #13361

@panpepson

This comment has been minimized.

Show comment
Hide comment
@panpepson

panpepson Jun 14, 2017

Hi,

ive removed all the node.js package on my OS

apt-get purge node.js

and manually remove/clear

/home/user*/(.npm,.ionic), /root/(.npm,.ionic), /usr/lib/node_modules

manual removal of the remainder helped and update your OS and new install node.js and ionic

cu

panpepson commented Jun 14, 2017

Hi,

ive removed all the node.js package on my OS

apt-get purge node.js

and manually remove/clear

/home/user*/(.npm,.ionic), /root/(.npm,.ionic), /usr/lib/node_modules

manual removal of the remainder helped and update your OS and new install node.js and ionic

cu

@panpepson

This comment has been minimized.

Show comment
Hide comment
@panpepson

panpepson Jun 14, 2017

Hi,

ive removed all the node.js package on my OS

apt-get purge node.js

and manually remove/clear

/home/user*/(.npm,.ionic), /root/(.npm,.ionic), /usr/lib/node_modules

manual removal of the remainder helped and update your OS and new install node.js and ionic

cu

panpepson commented Jun 14, 2017

Hi,

ive removed all the node.js package on my OS

apt-get purge node.js

and manually remove/clear

/home/user*/(.npm,.ionic), /root/(.npm,.ionic), /usr/lib/node_modules

manual removal of the remainder helped and update your OS and new install node.js and ionic

cu

@dtruffaut

This comment has been minimized.

Show comment
Hide comment
@dtruffaut

dtruffaut Jun 18, 2017

On Windows, I confirm that deleting the directory :

C:\Users<your_username>\AppData\Roaming\npm\node_modules

solves the issue.

dtruffaut commented Jun 18, 2017

On Windows, I confirm that deleting the directory :

C:\Users<your_username>\AppData\Roaming\npm\node_modules

solves the issue.

@jspblm

This comment has been minimized.

Show comment
Hide comment
@jspblm

jspblm Jul 9, 2017

@Fishrock123 Solution works for me on node v8.1.3 and npm 5.0.3

jspblm commented Jul 9, 2017

@Fishrock123 Solution works for me on node v8.1.3 and npm 5.0.3

@MichalZalecki

This comment has been minimized.

Show comment
Hide comment
@MichalZalecki

MichalZalecki Jul 11, 2017

@Fishrock123 solution is generally working 💥

If it's not working for you make sure that your version of npm is actually under /usr/local/lib/node_modules/npm. Run which npm. For node installed e.g. through ansible nodejs role it can be in: ~/nodejs/bin/npm. If that's the case then you want to rm -rf ~/nodejs/lib/node_modules/npm. Reinstall and you should be fine.

MichalZalecki commented Jul 11, 2017

@Fishrock123 solution is generally working 💥

If it's not working for you make sure that your version of npm is actually under /usr/local/lib/node_modules/npm. Run which npm. For node installed e.g. through ansible nodejs role it can be in: ~/nodejs/bin/npm. If that's the case then you want to rm -rf ~/nodejs/lib/node_modules/npm. Reinstall and you should be fine.

@redexp

This comment has been minimized.

Show comment
Hide comment
@redexp

redexp Jul 22, 2017

I get this error when I switched to older node with nvm.

Here my solution. I tried in console which bower it gives me /usr/bin/bower it was symlink to /usr/lib/node_modules/bower/bin/bower so I just removed symlink sudo rm /usr/bin/bower and removed module itself rm -rf /usr/lib/node_modules/bower and installed bower again npm i -g bower. After that was no error

redexp commented Jul 22, 2017

I get this error when I switched to older node with nvm.

Here my solution. I tried in console which bower it gives me /usr/bin/bower it was symlink to /usr/lib/node_modules/bower/bin/bower so I just removed symlink sudo rm /usr/bin/bower and removed module itself rm -rf /usr/lib/node_modules/bower and installed bower again npm i -g bower. After that was no error

@shahzadns

This comment has been minimized.

Show comment
Hide comment
@shahzadns

shahzadns Aug 17, 2017

For me this error came after using gulp serve command on angular1-gulp project, by removing the local node_modules folder and doing npm install solved this error.

node 7.9.0
npm 4.2.0
node installed using nvm version 0.25.1
Mac OS Sierra.

Hope this will help someone.
Cheers !

shahzadns commented Aug 17, 2017

For me this error came after using gulp serve command on angular1-gulp project, by removing the local node_modules folder and doing npm install solved this error.

node 7.9.0
npm 4.2.0
node installed using nvm version 0.25.1
Mac OS Sierra.

Hope this will help someone.
Cheers !

@develucas

This comment has been minimized.

Show comment
Hide comment
@develucas

develucas Aug 30, 2017

I also experienced it lately and solved it in the following way. For me there was a conflict but at the system level and it was caused by not cleaned properly, old nodejs installation. I couldn't use latest bower package, so after reading your comments

>whereis node_modules
node_modules: /usr/lib/node_modules /usr/local/lib/node_modules

I've deleted the second directory as it was for nodejs 6.x, and all returned to normal.

Cheers

develucas commented Aug 30, 2017

I also experienced it lately and solved it in the following way. For me there was a conflict but at the system level and it was caused by not cleaned properly, old nodejs installation. I couldn't use latest bower package, so after reading your comments

>whereis node_modules
node_modules: /usr/lib/node_modules /usr/local/lib/node_modules

I've deleted the second directory as it was for nodejs 6.x, and all returned to normal.

Cheers

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Sep 7, 2017

I had a similar problem and it seems that reinstalling gulp and also deleting node_modules directory in my project folder fixed the problem. I use node version 8.0.0 and npm 5.0.0.

EDIT ~ I mean this is for people having problem with graceful-fs module working with gulp.

ghost commented Sep 7, 2017

I had a similar problem and it seems that reinstalling gulp and also deleting node_modules directory in my project folder fixed the problem. I use node version 8.0.0 and npm 5.0.0.

EDIT ~ I mean this is for people having problem with graceful-fs module working with gulp.

@taylorc93

This comment has been minimized.

Show comment
Hide comment
@taylorc93

taylorc93 Sep 18, 2017

I ran into this issue as well when using lerna bootstrap. Turned out I had a node_modules folder in my home directory that had a copy of NPM in it that lerna was using. No idea how that got there, but removing it did the trick.

taylorc93 commented Sep 18, 2017

I ran into this issue as well when using lerna bootstrap. Turned out I had a node_modules folder in my home directory that had a copy of NPM in it that lerna was using. No idea how that got there, but removing it did the trick.

@zhuziyi1989

This comment has been minimized.

Show comment
Hide comment
@zhuziyi1989

zhuziyi1989 Mar 28, 2018

Reference solution: #9355

zhuziyi1989 commented Mar 28, 2018

Reference solution: #9355

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment