Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error: EISDIR: illegal operation on a directory, read at Object.readSync

See original GitHub issue

Fresh Expo install of Ignite, when I run the app in Expo on my Android phone, I see the error below. This was happening on Node V14, I upgraded to the latest Node v15 (as the metro server seemed to keep crashing too), this has solved the crashing but I’m still getting the debug error.

Finished building JavaScript bundle in 1293ms.

Running application on ONEPLUS A6003.

Error: EISDIR: illegal operation on a directory, read
    at Object.readSync (node:fs:617:3)
    at tryReadSync (node:fs:382:20)
    at Object.readFileSync (node:fs:419:19)
    at UnableToResolveError.buildCodeFrameMessage (/Users/user/Sites/sitename/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:304:17)
    at new UnableToResolveError (/Users/user/Sites/sitename/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:290:35)
    at ModuleResolver.resolveDependency (/Users/user/Sites/sitename/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:168:15)
    at DependencyGraph.resolveDependency (/Users/user/Sites/sitename/node_modules/metro/src/node-haste/DependencyGraph.js:353:43)
    at /Users/user/Sites/sitename/node_modules/metro/src/lib/transformHelpers.js:271:42
    at /Users/user/Sites/sitename/node_modules/metro/src/Server.js:1097:37
    at Generator.next (<anonymous>)

Here’s Ignite Doctor:

System
  platform           darwin
  arch               arm64
  cpu                8 cores      Apple M1
  directory          name        ~/Sites/name

JavaScript (and globally-installed packages)
  node               15.9.0       ~/.nvm/versions/node/v15.9.0/bin/node
  npm                7.6.1        ~/.nvm/versions/node/v15.9.0/bin/npm
    npm              7.6.1
    yarn             1.22.10
  yarn               1.22.10      ~/.nvm/versions/node/v15.9.0/bin/yarn

Ignite
  ignite-cli         6.2.0        ~/.npm-packages/bin/ignite
  ignite src         build        ~/.npm-packages/lib/node_modules/ignite-cli/build

Android
  java               1.8.0_282    /usr/bin/java
  android home       -            undefined

iOS
  xcode              12.4
  cocoapods          1.10.1       /usr/local/bin/pod

Issue Analytics

State:
Created 3 years ago
Reactions:1
Comments:8 (2 by maintainers)

Top GitHub Comments

1reaction

hssdivcommented, Mar 11, 2021

in my case (not fresh install) removing “react-native-reanimated” library helped

0reactions

joshuayoescommented, Oct 4, 2022

There has been a lot of changes since this issue last had activity. This is going to be closed for now, but please re-open if this still needs attention.

Top Results From Across the Web

EISDIR: illegal operation on a directory, using with React ...

Error : EISDIR: illegal operation on a directory, read at Object.readSync (fs.js:592:3) at tryReadSync (fs.js:366:20) at Object.

Metro bundler: Error: EISDIR: illegal operation on a directory ...

I'm still looking for a solution. I've read elsewhere that it could be a problem with using react-native-animated . This error is new...

NPM stuck giving the same error EISDIR: Illegal operation on ...

Windows : NPM stuck giving the same error EISDIR : Illegal operation on a directory, read at error (native) [ Beautify Your Computer ......

[error: eisdir: illegal operation on a directory, read] { errno ...

EISDIR stands for "Error, Is Directory". This means that NPM is trying to do something to a file but it is a directory....

angular/angular-cli - Gitter

Error : EISDIR: illegal operation on a directory, read at Error (native) at Object.fs.readSync (fs.js:731:19) at tryReadSync (fs.js:486:20) at Object.fs.