Eisdir Illegal Operation on a Directory Read at Error Metro-bundler

NPM stuck giving the aforementioned error EISDIR: Illegal functioning on a directory, read at mistake (native)

Domicile
Question
NPM stuck giving the same error EISDIR: Illegal operation on a directory, read at error (native)

I am stuck with this error no thing what directory I am in, and what I type after "npm" in cmd.exe. Here is the npm-debug.log:

              0 info it worked if it ends with ok ane verbose cli [ 'C:\\Programme Files\\nodejs\\node.exe', one verbose cli   'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js' ] ii info using [email protected] 3 info using [email protected] 4 verbose stack Fault: EISDIR: illegal functioning on a directory, read 4 verbose stack     at Error (native) v verbose cwd C:\Users\me 6 error Windows_NT vi.1.7601 7 error argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" 8 fault node v4.2.6 9 error npm  v2.xiv.12 x mistake lawmaking EISDIR 11 error errno -4068 12 error syscall read 13 error eisdir EISDIR: illegal operation on a directory, read thirteen error eisdir This is nigh likely not a problem with npm itself 13 error eisdir and is related to npm not being able to observe a package.json in 13 error eisdir a package yous are trying to install. xiv verbose exit [ -4068, truthful ]

I take tried and uninstalling/reinstalling nodejs multiple times, I even deleted npm and npm-cache folders in C:\Users\me\AppData\Roaming. I'grand not sure what went incorrect to cause this. One 2d it was working fine, and now I can't get rid of this error. The explanation in the log does not make sense, as it gives this error in whatsoever directory. I should annotation that running a command prompt every bit administrator does not requite this error. I'chiliad pulling my hair out this Friday evening trying to get this fixed, whatever help would be greatly appreciated!

This question is tagged with node.js windows cmd npm file-permissions

~ Asked on 2016-01-23 02:43:37

32 Answers

I ran into the same trouble while I was changing some npm settings. I did a mistake with one npm config set command and this added a line referring to a non-existing directory to C:\Users\{User}\.npmrc. Later on I deleted that line manually from .npmrc, the problem was gone.

~ Answered on 2016-02-16 10:04:37

EISDIR stands for "Fault, Is Directory". This ways that NPM is trying to do something to a file but it is a directory. In your case, NPM is trying to "read" a file which is a directory (Line: 4). Since the operation cannot be done the error is thrown.

Three things to make sure here.

Make certain the file exists. If information technology does not, you demand to create it. (If NPM depends on whatever specific information in the file, you lot volition need to have that information at that place).
Make sure it is in fact a file and not a directory.
It has the right permissions. Yous tin change the file to have all permissions with "sudo chmod 777 FILE_NAME". (Careful: You are giving Read, Write and Execute permissions to every one on that file)

~ Answered on 2017-03-08 16:55:55

Had the same problem today afterwards i've upgraded my npm from version half dozen.4.i to version 6.5.0. I fixed this past downloading the .pkg installer (recommended for nearly users) from node.js and runned it afterwards.

~ Answered on 2018-12-28 10:53:17

In my case I was getting the "EISDIR: illegal functioning on a directory, read" because in my .athwart-cli.json file I wasn't providing a full path in "scripts:"

For example I had

              "scripts": [         "../node_modules/hammerjs",         "../node_modules/moment"       ],

In fact it should have been

              "scripts": [         "../node_modules/hammerjs/hammer.min.js",         "../node_modules/moment/min/moment.min.js"       ],

~ Answered on 2018-01-19 09:07:01

I had the same issue on Mac OS X (installed with homebrew), and the .npmrc is not the but place node stored config variables. There is a glocal npmrc config file in /usr/local/etc that you have to edit using this command:

              sudo nano npmrc

Remove the ca= line, or whatever the config setting was that broke your install, relieve that file, and try npm again, and you should see information technology working.

~ Answered on 2016-07-27 17:54:25

These foreign errors occured recently on my OSX machine.

I could help myself the quick & dirty manner past running:

sudo chmod -R 777 /usr/local/lib/node_modules/

Something seemed to have messed upwards the admission rights of all global node modules.

~ Answered on 2019-01-14 14:12:29

For me fixing was add slash after directory name

~ Answered on 2018-06-20 20:10:34

If your trouble is associated with the React Native packager. Endeavor resetting the cache with react-native first --reset-enshroud.

~ Answered on 2018-02-12 nineteen:05:23

Make certain node_modules (and your root bundle.json) doesn't incorporate a reference to npm's "packet.json" module. Deleting package.json FOLDER from node_modules solved the effect for me.

~ Answered on 2019-10-01 06:xx:l

Bank check to ensure you are running npm install from the proper directory.

(The package.json file could exist i extra directory down, for case.)

~ Answered on 2016-12-20 12:36:04

I had this upshot with gulp. The trouble was that gulp added a dependency to my source file and I recollect npm tried to open up it:

              {   "name": "name",   "version": "2.0.0",   "description": "",   "main": "gulpfile.js",   "scripts": {     "test": "echo \"Error: no test specified\" && exit ane"   },   "author": "",   "license": "ISC",   "devDependencies": {     "appname": "file://gulp",     "gulp-concat": "^2.six.one",     "gulp-electron": "^0.1.3",     "gulp-beat": "^0.5.2",     "gulp-uglify": "^two.0.0",     "gulp-util": "^three.0.vii",     "node-7z": "^0.4.0"   } }

Make certain that at that place are no strange references in y'all package.json file.

~ Answered on 2016-11-25 12:08:22

~ Answered on 2016-01-25 19:34:15

Had the same problem until I tried deleting the .git binder. It worked. I guess this type of problem tin have unlike causes.

~ Answered on 2018-01-19 21:39:28

In my case, i was facing this issue while installing create-react-app in MAC (Mojave Bone) with following command :

              sudo npm install create-react-app -g

and got errors like this :

              npm WARN tar EISDIR: illegal functioning on a directory, open up '/usr/local/lib/node_modules/.staging/rxjs-a84420a7/src/scheduler' npm WARN tar EISDIR: illegal operation on a directory, open up '/usr/local/lib/node_modules/.staging/rxjs-a84420a7/src/symbol' npm WARN tar EISDIR: illegal performance on a directory, open '/usr/local/lib/node_modules/.staging/rxjs-a84420a7/src/testing' npm WARN tar EISDIR: illegal functioning on a directory, open '/usr/local/lib/node_modules/.staging/rxjs-a84420a7/src/util' npm WARN tar EISDIR: illegal operation on a directory, open '/usr/local/lib/node_modules/.staging/rxjs-a84420a7/src/webSocket' npm WARN tar EISDIR: illegal performance on a directory, open '/usr/local/lib/node_modules/.staging/rxjs-a84420a7/symbol' npm WARN tar EISDIR: illegal performance on a directory, open '/usr/local/lib/node_modules/.staging/rxjs-a84420a7/testing' npm WARN tar EISDIR: illegal operation on a directory, open '/usr/local/lib/node_modules/.staging/rxjs-a84420a7/util' npm WARN tar EISDIR: illegal functioning on a directory, open up '/usr/local/lib/node_modules/.staging/rxjs-a84420a7/webSocket'

I accept read npm.community that try to install without sudo :

              npm install create-react-app -yard

and it really solved my issue ..!!

~ Answered on 2019-04-23 09:12:31

In my case I forgot to pass the total path of ane of the file information technology was asking. After passing full path of the file worked :)

~ Answered on 2019-04-16 21:51:55

I fixed this consequence past moving my directory from my exFAT bulldoze which does not support symlinking.

My exFat drive is shared between osx and a bootcamp windows sectionalization then when I tried to clone and npm install my project it was failing but never explains that exFAT doesn't support this functionality.

There are drivers out there that you tin install to add the ability to symlink but you'll have to do a lot of your setup manually compared to running a simple npm script.

~ Answered on 2020-02-05 21:25:56

In my example, the C:\Users\{user}\AppData\local\npm files were subconscious, so I was not able to discover & delete the problem directory. Took me DAYS to realize this!

So double check to un-hibernate any folders then yous don't miss them! Here'southward a link to do this if you don't know how.

~ Answered on 2020-06-29 21:23:52

This happened to me on npm publish --admission public command. Project contained directory named package.json. This mistake is pitiful - because projection HAS to have this directory and named exactly package.json (it was part of test instance fixture to assert correct behavior of this lib).

~ Answered on 2021-01-14 19:06:42

I had faced similar issue. I set cafile using the command:

              npm config set cafile PATH_TO_CERTIFICATE

I was able to resolve this by deleting the document file settings, and setting strict-ssl = false.

~ Answered on 2020-01-25 12:46:55

In my instance, I am working on angularv10 with cloth. I had inverse some script files and forgot to remove these empty "" in the scripts array

scripts: [.....bla, bla, etc, ""]

remove these empty""

npm clear-cache --force

close and open vscode

It worked.

~ Answered on 2021-01-07 05:27:26

In my example issue was that space graphic symbol was in the proper noun of the source folder (Windows 10).

~ Answered on 2020-10-06 22:xxx:55

On Mac:

Per-user config file: ~/.npmrc

~ Answered on 2020-10-01 14:34:05

In my case these steps solved my problem:

terminating npm process (CTRL + C)
deleting entire folder
creating new one
running npm again

~ Answered on 2019-05-29 07:43:05

Make sure to check your version of npm and whether or not there are issues with it. I was having the aforementioned issue at the time of this post and I discovered that my npm version (6.five) was having issues. I had to uninstall and reinstall npm version 6.4.1 and then everything started to work slap-up once more.

~ Answered on 2019-01-24 21:24:49

In my case, I'one thousand using Windows 10 in Spanish and this version mixes English and Spanish directory names. My problem was that the desktop directory has this name for some commands and escritorio to others. I believe that npm cannot resolve this. My solution was to simply modify to another directory starting from C:\ dissimilar to my dwelling house directory.

~ Answered on 2019-12-05 15:51:10

For mac os: If installed straight from nodejs website the npmrc file would be located in /usr/local/etc/npmrc. Just delete the config which is undefined and this problem would be fixed.

~ Answered on 2020-03-06 23:46:28

I had the aforementioned upshot. There was a linked binder in my directory which was causing the issue. i added that folder to ignore listing then it started working fine as expected.

~ Answered on 2018-05-31 16:27:09

Just delete .npmrc folder in c:users>'username' and try running the control it will be resolved !

~ Answered on 2020-11-23 09:17:12

I know this isn't specifically request almost forever js.. but google lead me here and so.. For me it was equally simple every bit an ending slash.

I just inverse:

              forever start -a -50 /dev/null/ /var/www/node/my_file.js

To:

              forever kickoff -a -l /dev/cypher /var/www/node/my_file.js

And the mistake disappeared

~ Answered on 2018-06-01 22:35:48

I had a broken symlink to node_modules in a subfolder

~ Answered on 2019-04-10 08:32:25

I had a like problem while setting upwards average code. It was reading my bundle.js file as a directory. And so as stated here. EISDIR mean its a directory and not a file. To set the issue, I deleted the file and just recreated (information technology was originally created automatically). If you cannot find the file (because its hidden), simply utilise the terminal to notice and delete it.

~ Answered on 2017-06-01 22:01:47

I just removed the line

              .babel('resources/assets/js/app.js')

for laravel v.half dozen with vue.js. in webpack.mix.js

~ Answered on 2020-05-twenty 07:12:14

Eisdir Illegal Operation on a Directory Read at Error Metro-bundler

NPM stuck giving the aforementioned error EISDIR: Illegal functioning on a directory, read at mistake (native)

32 Answers

Most Viewed Questions:

0 Response to "Eisdir Illegal Operation on a Directory Read at Error Metro-bundler"

Post a Comment

Iklan Atas Artikel

Iklan Tengah Artikel 1

Iklan Tengah Artikel 2

Iklan Bawah Artikel