NPM not working (Cannot find module 'internal/fs' - nodejs) - javascript

NPM error on update. I recently update to Node version 7.x. Now npm is not working.
I am unable to locate the error, it may be due to -
npm ERR! Cannot find module 'internal/fs'.
I get the following when I run sudo npm update -g -
npm ERR! Linux 3.13.0-101-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "update" "-g"
npm ERR! node v7.1.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>
My /etc/profile.d/nodejs.sh has the following contents:
NODE_PATH=/usr/lib/nodejs:/usr/lib/node_modules:/usr/share/javascript
export NODE_PATH

You should be able to remove the npm directory (typically /usr/local/lib/node_modules/npm) and then reinstall one of the official node tarballs, which includes npm (you can find the latest from http://nodejs.org/dist/latest-v7.x/).
Did you upgrade from an older version of node?
If so, that is probably part of the reason why you are having this issue. Older versions of graceful-fs (a dependency of npm) did things that are no longer available in node v7.

According to this thread, updating npm to version 4 will solve your problem, try:
npm i -g npm#4
If this doesn't work, try:
~/.n/n/versions/node/7.0.0/bin/npm i -g npm#4

delete node_modules directory and then type in your console "npm install". For a reason that I dont know, if you only update npm, it does not fix the error, but re-installing npm everything is gonna be allright.

For me, if I facing error "cannot find module internal/fs", it would be refer to command path. Better find the command path:
npm config get prefix
put into system environment path.
It is worked for me after facing the error several days.

Related

create-react-app aborting with code ENOENT

Just started out with React using an online course from Udemy. For some reason my create-react-app stopped working all of a sudden and it shows this log.
Installing packages. This might take a couple of minutes.
Installing react, react-dom, and react-scripts with cra-template...
npm ERR! code ENOENT
npm ERR! syscall rename
npm ERR! path C:\Users\Vahram\Desktop\Udemy-React\Personal-Notes\Sec5\pokedex-exercise\node_modules\postcss-normalize
npm ERR! dest C:\Users\Vahram\Desktop\Udemy-React\Personal-Notes\Sec5\pokedex-exercise\node_modules\.postcss-normalize.DELETE
npm ERR! errno -4058
npm ERR! enoent ENOENT: no such file or directory, rename 'C:\Users\Vahram\Desktop\Udemy-React\Personal-Notes\Sec5\pokedex-exercise\node_modules\postcss-normalize' -> 'C:\Users\Vahram\Desktop\Udemy-React\Personal-Notes\Sec5\pokedex-exercise\node_modules\.postcss-normalize.DELETE'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Vahram\AppData\Roaming\npm-cache\_logs\2021-05-06T21_38_53_463Z-debug.log
Aborting installation.
npm install --save --save-exact --loglevel error react react-dom react-scripts cra-template has failed.
Deleting generated file... node_modules
Deleting generated file... package.json
Deleting pokedex-exercise/ from C:\Users\Vahram\Desktop\Udemy-React\Personal-Notes\Sec5
Done.
I checked out similar questions on here and there were some solutions I tried. The usual answer is to delete package.json but I don't have that seeing as I'm trying to make a new React app. Here's what I've tried so far:
Originally tried npx create-react-app my_app
Then tried running npm install -g create-react-app and then create-react-app my_app.
Then tried npm cache clean --force followed by npm rebuild then step 2 again.
Then tried npm init --yes to generate a package.json file, followed by trying to make a new app again using CRA.
Tried restarting the machine
Curious thing I noticed that I'm not sure is related to the issue:
When I go to Task Manager, there are two Node.js processes running. When I try to end one, it spawns another Node.js process... I can't get rid of all Node.js processes. This is why I originally restarted the machine.
Any help is appreciated! I have no idea how to proceed... I'm even thinking of formatting my machine and starting everything from scratch. However, I'd like to know why this happens so that I can avoid it in the future.
I just solved this using the following command.
npm uninstall -g create-react-app
and then:
npm install -g create-react-app
Regards

error: this is probably not a problem with npm. This is likely additonal logging output above

C:\Users\Jorge\Desktop\space-xplorer>npm install
node-sass#4.11.0 install C:\Users\Jorge\Desktop\space-xplorer\node_modules\node-sass
node scripts/install.js
Downloading binary from https://github.com/sass/node-sass/releases/download/v4.11.0/win32-x64-72_binding.node
Cannot download "https://github.com/sass/node-sass/releases/download/v4.11.0/win32-x64-72_binding.node":
HTTP error 404 Not Found
Hint: If github.com is not accessible in your location
try setting a proxy via HTTP_PROXY, e.g.
export HTTP_PROXY=http://example.com:1234
or configure npm proxy via
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! node-sass#4.11.0 postinstall: node scripts/build.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the node-sass#4.11.0 postinstall 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! C:\Users\Jorge\AppData\Roaming\npm-cache_logs\2020-01-23T22_44_17_513Z-debug.log
This issue is coming because of compatibility issue of node version and node sass version.
You need to downgrade node version to 10 to install node sass 4.1.0. It is not compatible with version 12 of node.
See this discussion for the same issue.
Compatible versions are listed on the readme https://github.com/sass/node-sass#supported-nodejs-versions-vary-by-release-please-consult-the-releases-page-below-is-a-quick-guide-for-minimium-support
Following 2 lines of code will resolve this error
npm run build
npm start
you should ask a question and provide some explanation, not just throw an error up and expect an answer. But I've seen this before:
Basically NPM is trying lacking a dependency for loading node-sass, and its fallback is to get the file it needs from github.
Looks like you're behind a firewall that blocks you from direct access to github, but all you actually need is that file bindings file.
You would have to have a proxy server that is allowed to access github, or download the binary file yourself.
I downgraded the node from 14.8 to 12.18.3, but it did NOT solve the problem.
but after that, as crazy as it is may sound, I deleted the package-lock.json and tried to install the package again and solved the problem.

Unable to install node modules because 'This is related to npm not being able to find a file.'

So in my recent project I tried to install some node modules, in this case, express and MySQL, which both return the same error:
npm WARN thecaptain.ga#1.0.0 No repository field.
npm ERR! path C:\Users\user\projectroot\node_modules\on-finished
npm ERR! code ENOENT
npm ERR! errno -4058
npm ERR! syscall rename
npm ERR! enoent ENOENT: no such file or directory, rename 'C:\Users\user\projectroot\node_modules\on-
finished' -> 'C:\Users\user\projectroot\node_modules.on-finished.DELETE'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent
npm ERR! A complete log of this run can be found in:
I tried to delete all the related files, then reinstalling it, however that did not change anything. I have run npm init before the install even attempted to fill in the dependency manually, to then run npm install. It happens with every node module in any node project I have.
Turns out the issue was because the dropbox tried to synchronize the files as i was installing the package. Pausing or disabling this fixes the issue...
Could you try this please:
1 - Ensure no NPM scripts are running.
2 - Navigate to your project route
3 - Run this command:
rm package-lock.json && npm i
Note - it may also be worth trying to delete your 'node_modules' folder in your project directory and running the above command.

React keeps aborting installation when I try the tutorial

I was trying to follow the tutorial on the react website today but for whatever reason it doesnt want to work for me when i run the command:
npx create-react-app my-app
`I get the following error message;
Creating a new React app in D:\NodeJs\react\my-app.
Installing packages. This might take a couple of minutes.
Installing react, react-dom, and react-scripts...
npm ERR! code ETARGET
npm ERR! notarget No matching version found for postcss#^7.0.11
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! notarget
npm ERR! notarget It was specified as a dependency of 'autoprefixer'
npm ERR! notarget
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\matth\AppData\Roaming\npm-cache\_logs\2019-01-
12T17_55_39_805Z-debug.log
Aborting installation.
npm install --save --save-exact --loglevel error react react-dom react-
scripts has failed.
Deleting generated file... package.json
Deleting my-app/ from D:\NodeJs\react
Done.`
My npm version is 6.5.0 and Node is 11.6.0
Not sure what the heck is going on as when I did this on my work laptop it worked without any issues with the exact same versions of node and npm
I was fix problem when I error create-react-app
Err: code ERR_SOCKET_TIMEOUT
npm ERR! network Socket timeout
npm ERR! network This is a problem related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! A complete log of this run can be found in:
I had rename file .npmrc --> .npmrc-old
C:\Users\you\.npmrc
And I success >>> I feel perfect
-
Or can you fix:
--> use git bash terminal
Just an update for everyone. It worked now. All I did was reinstall nodejs for the 4th time, nothing else. Makes 0 sense. anyways, thanks for your answers, appreciate it.
I also got a same error.
Try to run npm cache clean --force after that just run create-react-app
Definitely It will work

NodeJS - setting up mean.io cannot find module errors

I'm sort of new to this whole "node" js thing. When trying to install the MEAN package from http://mean.io/, I followed these steps faithfully:
I "cd" to my directory, run "npm install", and then the "grunt" command, and get this error:
Error: Cannot find module 'coffee-script'
So I roll with the punches. npm install coffee-script, run "grunt" again.
Error: Cannot find module 'getobject'
Ever patient, I decide "okay, forget grunt". I run "node server". Then I get this error:
Error: Cannot find module 'merge-descriptors'
What's wrong? How can I get MEAN working here? (I thought npm was supposed to make life easier).
Update 12/31/13: When I look at the output of npm install, there are a number of "Error: EMFILE" errors. As I understand those errors are related to too many files being opened and graceful-fs is a solution to this. Sample EMFILE error pasted below:
npm ERR! System Darwin 13.0.0
npm ERR! command "node" "/usr/local/bin/npm" "install"
npm ERR! cwd /Users/cnokes/Desktop/mean-master
npm ERR! node -v v0.10.7
npm ERR! npm -v 1.2.21
npm ERR! path /Users/cnokes/Desktop/mean-master/node_modules/grunt/node_modules/iconv-lite/README.md
npm ERR! code EMFILE
npm ERR! errno 20
npm ERR! tar.unpack error reading /var/folders/wv/xrm8qphn5bsgfj5w45kqrwl9lgq2j2/T/npm-27019/1388513549132-0.22752901865169406/tmp.tgz
With graceful-fs installed, I re-run npm install and get a couple of these errors:
npm ERR! Error: ENOENT, utime '/Users/cnokes/Downloads/mean-master2/node_modules/express/node_modules/fresh/index.js'
I've run in to this and think this might be connected to another issue.
Basically it's related to the number of open files (alot) that get open when we do a npm install.
It has been blogged about nicely here - http://otaqui.com/blog/1618/how-to-fix-error-emfile-too-many-open-files-from-yeoman-and-npm/
and I update the mean FAQ
https://github.com/linnovate/mean/wiki/Faq

Categories