Error: EISDIR: illegal operation on a directory, read at Object.readSync (fs.js:614:3) at tryReadSync (fs.js:383:20) at Object.readFileSync (fs.js:420:19) at UnableToResolveError.buildCodeFrameMessage (F:\appsubsee\app\node_modules\metro\src\node-haste\DependencyGraph\ModuleResolution.js:347:17) at new UnableToResolveError (F:\appsubsee\app\node_modules\metro\src\node-haste\DependencyGraph\ModuleResolution.js:333:35) at ModuleResolver.resolveDependency (F:\appsubsee\app\node_modules\metro\src\node-haste\DependencyGraph\ModuleResolution.js:211:15) at DependencyGraph.resolveDependency (F:\appsubsee\app\node_modules\metro\src\node-haste\DependencyGraph.js:413:43) at F:\appsubsee\app\node_modules\metro\src\lib\transformHelpers.js:317:42 at F:\appsubsee\app\node_modules\metro\src\Server.js:1471:14 at Generator.next (<anonymous>) Error: EISDIR: illegal operation on a directory, read at Object.readSync (fs.js:614:3) at tryReadSync (fs.js:383:20) at Object.readFileSync (fs.js:420:19) at UnableToResolveError.buildCodeFrameMessage (F:\appsubsee\app\node_modules\metro\src\node-haste\DependencyGraph\ModuleResolution.js:347:17) at new UnableToResolveError (F:\appsubsee\app\node_modules\metro\src\node-haste\DependencyGraph\ModuleResolution.js:333:35) at ModuleResolver.resolveDependency (F:\appsubsee\app\node_modules\metro\src\node-haste\DependencyGraph\ModuleResolution.js:211:15) at DependencyGraph.resolveDependency (F:\appsubsee\app\node_modules\metro\src\node-haste\DependencyGraph.js:413:43) at F:\appsubsee\app\node_modules\metro\src\lib\transformHelpers.js:317:42 at F:\appsubsee\app\node_modules\metro\src\Server.js:1471:14 at Generator.next (<anonymous>) Error: EISDIR: illegal operation on a directory, read at Object.readSync (fs.js:614:3) at tryReadSync (fs.js:383:20) at Object.readFileSync (fs.js:420:19) at UnableToResolveError.buildCodeFrameMessage (F:\appsubsee\app\node_modules\metro\src\node-haste\DependencyGraph\ModuleResolution.js:347:17) at new UnableToResolveError (F:\appsubsee\app\node_modules\metro\src\node-haste\DependencyGraph\ModuleResolution.js:333:35) at ModuleResolver.resolveDependency (F:\appsubsee\app\node_modules\metro\src\node-haste\DependencyGraph\ModuleResolution.js:211:15) at DependencyGraph.resolveDependency (F:\appsubsee\app\node_modules\metro\src\node-haste\DependencyGraph.js:413:43) at F:\appsubsee\app\node_modules\metro\src\lib\transformHelpers.js:317:42 at F:\appsubsee\app\node_modules\metro\src\Server.js:1471:14 at Generator.next (<anonymous>) Error: EISDIR: illegal operation on a directory, read at Object.readSync (fs.js:614:3) at tryReadSync (fs.js:383:20) at Object.readFileSync (fs.js:420:19) at UnableToResolveError.buildCodeFrameMessage (F:\appsubsee\app\node_modules\metro\src\node-haste\DependencyGraph\ModuleResolution.js:347:17) at new UnableToResolveError (F:\appsubsee\app\node_modules\metro\src\node-haste\DependencyGraph\ModuleResolution.js:333:35) at ModuleResolver.resolveDependency (F:\appsubsee\app\node_modules\metro\src\node-haste\DependencyGraph\ModuleResolution.js:211:15) at DependencyGraph.resolveDependency (F:\appsubsee\app\node_modules\metro\src\node-haste\DependencyGraph.js:413:43) at F:\appsubsee\app\node_modules\metro\src\lib\transformHelpers.js:317:42 at F:\appsubsee\app\node_modules\metro\src\Server.js:1471:14 at Generator.next (<anonymous>) Android Running app on DUB-LX1 TypeError: (0 , _nativeStack.createStackNavigator) is not a function at node_modules\expo\build\logs\LogSerialization.js:156:14 in _captureConsoleStackTrace at node_modules\expo\build\logs\LogSerialization.js:41:26 in serializeLogDataAsync - ... 9 more stack frames from framework internals Unable to symbolicate stack trace: The stack is null Invariant Violation: "main" has not been registered. This can happen if: * Metro (the local dev server) is run from the wrong folder. Check if Metro is running, stop it and restart it in the current project. * A module failed to load due to an error and `AppRegistry.registerComponent` wasn't called. at node_modules\expo\build\logs\LogSerialization.js:156:14 in _captureConsoleStackTrace at node_modules\expo\build\logs\LogSerialization.js:41:26 in serializeLogDataAsync - ... 9 more stack frames from framework internals Unable to symbolicate stack trace: The stack is null
سلام استاد خسته نباشید من تمام فایل ها رو نصب کردم و موقع ران همچین اروری رو بهم میده نمیدونم مشکل کجاست لطفا راهنماییم کنید ممنون ارتا فلاح پور سیاهگورابی
سلام دوست من
بابت دیر جواب دادن عذر خواهی میکنم خیلی از سوالات در بخش spam ایمیلم قرار گرفته و متاسفانه نتونستم به خیلی از سوالات جواب بدم
اگر یک با node_modules رو پاک کنی و دوباره با دستور npm i نصب کنی بازم این خطا رو میده?