Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upgetting "Cannot find module 'internal/fs'" in Node.js v7.0.0 #14232
Comments
othiym23
added
windows
support
labels
Oct 11, 2016
This comment has been minimized.
This comment has been minimized.
You're going to need to upgrade to |
othiym23
closed this
Oct 11, 2016
This comment has been minimized.
This comment has been minimized.
Also, you should be able to use the version of npm packaged with Node 7.0.0, but you may need to manually delete any copies of npm that don't get uninstalled by Node's uninstall script. |
This comment has been minimized.
This comment has been minimized.
cool, works for me. after I upgrade npm to 3.10.9. it was fixed |
This comment has been minimized.
This comment has been minimized.
piotr-cz
commented
Oct 26, 2016
If this happens when running gulp, you have to downgrade nodejs to v6, see gulpjs/gulp#1843 |
This comment has been minimized.
This comment has been minimized.
tim-mc
commented
Oct 26, 2016
This error is also happening for me with node 7, npm versions 3.10.9 & 4.0.1. Should I open a separate issue? |
This comment has been minimized.
This comment has been minimized.
jackiehluo
commented
Oct 26, 2016
Same as @tim-mc! |
This comment has been minimized.
This comment has been minimized.
hult
commented
Oct 27, 2016
Had the same issue as @tim-mc @jackiehluo, tried different versions of npm (including the one packaged with node), but it didn't help. Removing my |
This comment has been minimized.
This comment has been minimized.
piotr-cz
commented
Oct 27, 2016
Check error stack trace, there is a change that there is a dependency vinyl-fs: 0.3.0 which is causing this |
This comment has been minimized.
This comment has been minimized.
heziqiang
commented
Oct 27, 2016
•
@othiym23 it works by upgrading npm to npm@3.10.9, thanks! |
This comment has been minimized.
This comment has been minimized.
ymc-sise
commented
Oct 27, 2016
Same as @tim-mc! |
This comment has been minimized.
This comment has been minimized.
tim-mc
commented
Oct 27, 2016
•
FWIW, I've tried removing |
timvandermeij
referenced this issue
Oct 27, 2016
Closed
Update Node to latest version on the bots #7369
This comment has been minimized.
This comment has been minimized.
joelself
commented
Oct 27, 2016
I can't upgrade npm because I get the same username@machine:~/$ npm install npm@3.10.9
npm ERR! Linux 3.13.0-91-generic
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "npm@3.10.9"
npm ERR! node v7.0.0
npm ERR! npm v3.10.8
npm ERR! code MODULE_NOT_FOUND
npm ERR! Cannot find module 'internal/fs'
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! <https://github.com/npm/npm/issues> |
This comment has been minimized.
This comment has been minimized.
guyellis
commented
Oct 27, 2016
•
This comment has been minimized.
This comment has been minimized.
vuongtran
commented
Oct 28, 2016
@guyellis It work fine for me. Thanks! |
This comment has been minimized.
This comment has been minimized.
juankmarin
commented
Oct 28, 2016
Works for me removing the node_modules folder and install again |
This comment has been minimized.
This comment has been minimized.
gempain
commented
Nov 1, 2016
@guyellis completing your comment: |
This comment has been minimized.
This comment has been minimized.
guyellis
commented
Nov 1, 2016
@gempain thanks. I should have mentioned that |
This comment has been minimized.
This comment has been minimized.
gempain
commented
Nov 6, 2016
•
@guyellis not sure either. But I think your comment is perfect as is. I guess I should've known how to switch between node versions. But the Google search took me a minute, so not too bad :) |
added a commit
to kelly-vernon-volusion/runscope-api-wrapper
that referenced
this issue
Nov 18, 2016
kelly-vernon-volusion
referenced this issue
Nov 18, 2016
Merged
problem with node 7.x where gulp cannot find internal/fs #2
This comment has been minimized.
This comment has been minimized.
one-aalam
commented
Nov 24, 2016
@guyellis Thanks! worked like a charm |
This comment has been minimized.
This comment has been minimized.
thedillonb
commented
Nov 30, 2016
This doesn't appear to be fixed in 3.10.9 as suggested above. Pulling the latest NodeJS current release (7.2.0) which bundles NPM 3.10.9 still results in failure:
|
This comment has been minimized.
This comment has been minimized.
xpolb01
commented
Nov 30, 2016
I had the same issue. What I did was the following:
|
This comment has been minimized.
This comment has been minimized.
bountyx
commented
Dec 1, 2016
@guyellis Same issue, your instructions also worked for me. Can anyone shed light onto WHY that fixes the issue? |
This comment has been minimized.
This comment has been minimized.
lsommaruga
commented
Dec 2, 2016
@xpolb01 Thnks also work for me OS X Yosemite 10.10.5 (got the error while installing nodemon module npm install -g nodemon ) |
This comment has been minimized.
This comment has been minimized.
vitalygoji
commented
Feb 14, 2017
Language? What language do you think you will be using working on your
future fast food jobs after you boss realises that you can't fix a bug
which was sitting there for several YEARS?
…On Feb 13, 2017 5:27 AM, "Nicolás Fantone" ***@***.***> wrote:
@vitalygoji <https://github.com/vitalygoji> Wow, there. Easy on the
language, fella. I can understand your frustration, but your words have
absolutely no place in here (nor everywhere else, to be frank).
(Also, you got the date wrong: *20017* is yet to come).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#14232 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABJDfr0Hyo_DJWgC4Fxu0dlCABSGJCPTks5rcFozgaJpZM4KTLHq>
.
|
This comment has been minimized.
This comment has been minimized.
mitchallen
commented
Feb 14, 2017
Fortunately GitHub provides a mute-this-thread option ... |
This comment has been minimized.
This comment has been minimized.
vitalygoji
commented
Feb 14, 2017
That will fix that bug. Thank you!
…On Feb 13, 2017 7:29 PM, "Mitch Allen" ***@***.***> wrote:
Fortunately GitHub provides a mute-this-thread option ...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#14232 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABJDfpP7u49_WqdpKBtdN-u3fWs9ZKK8ks5rcR-IgaJpZM4KTLHq>
.
|
This comment has been minimized.
This comment has been minimized.
fabrikate
commented
Feb 16, 2017
•
I am getting this same issue. Anytime I try and npm install I get the following error:
To get rid of this I uninstall npm and reinstall. Any clarity as to what is causing this issue? |
This comment has been minimized.
This comment has been minimized.
vitalygoji
commented
Feb 16, 2017
My advice is to avoid npm. I reported this issue and all I got was a bunch
of insults in return. I am surprised that Google Polymer recommends npm.
We need to report to google that npm team is incapable of fixing two years
old bugs. They are clearly YEARS away from being production ready.
…On Feb 16, 2017 10:48 AM, "Kate Stearns" ***@***.***> wrote:
I am getting this same issue.
Node: v7.4.0
NPM: 4.0.5
Anytime I try and npm install I get the following error:
`npm ERR! Darwin 15.6.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! node v7.4.0
npm ERR! npm v4.0.5
npm ERR! code MODULE_NOT_FOUND
npm ERR! Cannot find module 'internal/fs'
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! https://github.com/npm/npm/issues
npm ERR! Please include the following file with any support request:
npm ERR! /Users/name/frontend/npm-debug.log
`
Any suggestions since I am unable to npm install anything?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#14232 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABJDfodEEsux7QjqoIfNRK7l57dWPxUwks5rdJnogaJpZM4KTLHq>
.
|
This comment has been minimized.
This comment has been minimized.
agalazis
commented
Feb 19, 2017
•
for me even downloading didn't work for a specific package even when trying to clean install all global modules. Not sure if it's actually an npm issue anymore... xD |
This comment has been minimized.
This comment has been minimized.
fabrikate
commented
Feb 19, 2017
•
For me I get this issue when I switch my versions of node. ( Work is 4.2, Projects I use 7.5 ). Two work arounds are to use homebrew to uninstall then install npm OR create a VM. |
This comment has been minimized.
This comment has been minimized.
BrianO
commented
Feb 19, 2017
I have followed the tip above by "jessaustin" about removing Node 7.. version and going back to 6.9 version. I notice the Node website says "Latest LTS Version: v6.9.5 (includes npm 3.10.10)", but when I do "npm --version", my machine now says 2.3.0. Should i try to update NPM to a higher version now? I do see my Dependencies errors are gone in Visual Studio 2015 Core project, but this is after so many changes, I may not be in the clear and just getting lucky that the package update succeeded somewhere along the way.. Thanks |
This comment has been minimized.
This comment has been minimized.
danhouldsworth
commented
Feb 21, 2017
I've just recompiled node from source (now : node v7.5 / npm v4.1.2) and still broken. Frustratingly, I followed the earlier advice to delete node_modules/ and so now I'm stuck!
|
This comment has been minimized.
This comment has been minimized.
vitalygoji
commented
Feb 21, 2017
Some people depend on that tool. Is word "lawsuit" sound familiar to NPM
team?
…On Tue, Feb 21, 2017 at 7:32 AM, danhouldsworth ***@***.***> wrote:
I've just recompiled node from source (now : node v7.5 / npm v4.1.2) and
still broken. Frustratingly, I followed the earlier advice to delete
node_modules/ and so now I'm stuck!
npm ERR! Linux 4.4.44-39.55.amzn1.x86_64
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "--production"
npm ERR! node v7.5.0
npm ERR! npm v4.1.2
npm ERR! code MODULE_NOT_FOUND
npm ERR! Cannot find module 'internal/fs'
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! <https://github.com/npm/npm/issues>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#14232 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABJDfrP5pMgWACgLWNwcK0WPXliHqzn9ks5rewOfgaJpZM4KTLHq>
.
|
This comment has been minimized.
This comment has been minimized.
agalazis
commented
Feb 21, 2017
LOL. Don't do open source, worst case scenario you will get sued. Just kidding, I am sure they are covered by their license. @vitalygoji What did you do about it? did you do a pull request and they didn't accept it? |
This comment has been minimized.
This comment has been minimized.
vitalygoji
commented
Feb 21, 2017
I can't believe that they got used by lots of people. What did google and
GitHub people think when they started using this unsupported crap? This bug
is several years old now
…On Feb 21, 2017 1:26 PM, "Andreas Galazis" ***@***.***> wrote:
LOL. Don't do open source, worst case scenario you will get sued. Just
kidding, I am sure they are covered by their license. @vitalygoji
<https://github.com/vitalygoji> What did you do about it? did you do a
pull request and they didn't accept it?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#14232 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABJDfgww7Q0gKrX5MHcJKHaAJLbvc-JNks5re1aQgaJpZM4KTLHq>
.
|
This comment has been minimized.
This comment has been minimized.
jcastrov
commented
Feb 27, 2017
Still with this issue |
This comment has been minimized.
This comment has been minimized.
doapp-ryanp
commented
Mar 2, 2017
•
I use the To fix this error, I simply removed npm from the global space (macOS): I then re-ran To summarise: > sudo rm -rf /usr/local/lib/node_modules/npm
> sudo n latest
> node --version
v7.7.1
> npm --version
4.1.2
> sudo n 4.3.2
> npm --version
2.14.12 Here are some other suggestions that did not work for me: http://stackoverflow.com/questions/40308623/cannot-find-module-internal-fs-afer-upgrading-to-node-7 |
This comment has been minimized.
This comment has been minimized.
rsibanez89
commented
Mar 4, 2017
Works fine for me.
|
This comment has been minimized.
This comment has been minimized.
JohnnyWalkerDesign
commented
Mar 27, 2017
@doapp-ryanp Thanks! Your solution was the one that worked for me. Frustrating bug! |
This comment has been minimized.
This comment has been minimized.
codinronan
commented
May 15, 2017
In my case, the problem was bower - I was on 1.7.3, Node 7.7.4, npm 4.1. Upgrading Bower to 1.8.0 solved the issue for me. |
This comment has been minimized.
This comment has been minimized.
agalazis
commented
May 16, 2017
since the issue is upgrading one solution is docker... do clean builds/runs in docker xD |
This comment has been minimized.
This comment has been minimized.
samvloeberghs
commented
May 19, 2017
going back to v |
This comment has been minimized.
This comment has been minimized.
vanessarusu
commented
May 20, 2017
deleting the node_modules and running npm install worked for me! |
This comment has been minimized.
This comment has been minimized.
siddo420
commented
Jun 21, 2017
@vanessarusu did you delete global node_modules folder? rm -rf /usr/local/lib/node_modules/ |
This comment has been minimized.
This comment has been minimized.
siddo420
commented
Jun 21, 2017
I renamed the folder and tried but didn't work |
This comment has been minimized.
This comment has been minimized.
shubham-chaudhari
commented
Jul 11, 2017
•
npm -g install npm@next resolved for me.... |
cpetrov
referenced this issue
Jul 14, 2017
Closed
tabris initi crashes on description when using typescript template #24
This comment has been minimized.
This comment has been minimized.
pyotrritchie
commented
Sep 4, 2017
$ npm install npm -v 5.3.0 I had this issue on npm 4.2.0 and node 7.8.0 so updated to the above and still having the same issue. |
This comment has been minimized.
This comment has been minimized.
guntram
commented
Sep 11, 2017
•
On Windows_NT 6.1.7601, removing the EDIT: I did not get the error again with the mentioned versions. |
This comment has been minimized.
This comment has been minimized.
Jero786
commented
Sep 16, 2017
•
Works fine for me too! |
This comment has been minimized.
This comment has been minimized.
alexey-sh
commented
Jan 11, 2018
|
Gcaufy commentedOct 11, 2016
•
edited
I'm opening this issue because:
What's going wrong?
When I use node v6.7.0, I do
npm install
, it works well.After I upgrade to v7.0.0-nightly, I get an error:
Then I downgrade to v6.7.0, it works well again.
Errors
Detail
Other
I also checked this issue #12880
But I tried to uninstall and install many times, it does not work for me.
I download Node.js from these two links:
V6.7.0
v7.0.0