Question

Metro 运行时出错：metro-hermes-compiler\src\emhermesc.js:77

2022-01-12

8408

android react-native

我通过 yarn start 启动 metro。在另一个终端我运行 yarn android 。在安装应用程序时，metro 终端出现以下错误，并且 metro 停止执行：

C:\Users\SAMSUNG\Desktop\ReactNativeProjects\MyApp\node_modules\metro-hermes-compiler\src\emhermesc.js:77
          throw ex;
          ^

Error: EPERM: operation not permitted, lstat 'C:\Users\SAMSUNG\Desktop\ReactNativeProjects\MyApp\node_modules\react-native-gesture-handler\android\build\kotlin\compileDebugKotlin\caches-jvm'
Emitted 'error' event on NodeWatcher instance at:
    at NodeWatcher.<anonymous> (C:\Users\SAMSUNG\Desktop\ReactNativeProjects\MyApp\node_modules\sane\src\node_watcher.js:291:16)
    at FSReqCallback.oncomplete (fs.js:168:21) {
  errno: -4048,
  code: 'EPERM',
  syscall: 'lstat',
  path: 'C:\\Users\\SAMSUNG\\Desktop\\ReactNativeProjects\\MyApp\\node_modules\\react-native-gesture-handler\\android\\build\\kotlin\\compileDebugKotlin\\caches-jvm'
}

在构建应用程序时，我再次通过 yarn start 启动 metro。当应用程序构建完成时，发生以下崩溃：

BUNDLE  ./index.js

 ERROR  TypeError: undefined is not an object (evaluating 'InnerNativeModule.installCoreFunctions')
 ERROR  Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication). A frequent cause of the
error is that the application entry file path is incorrect.
      This can also happen when the JS bundle is corrupt or there is an early initialization error when loading React Native.
 ERROR  Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication). A frequent cause of the
error is that the application entry file path is incorrect.
      This can also happen when the JS bundle is corrupt or there is an early initialization error when loading React Native.

我什么都不明白。这些问题发生在我尝试添加库 @react-navigation/drawer 及其先决条件时： yarn add react-native-gesture-handler react-native-reanimated

Answer 1

在 Windows 10 上遇到了同样的问题。更改 node_watcher.js 为我解决了这个问题。我更改了函数 isIgnorableFileError 以适用于 error === null，并在 NodeWatcher 类中使用了此函数。这些更改远非完美，但现在它可以正常工作了。

第一个猜测 - 当 NodeWatcher 和构建同时访问文件时出现权限问题。

这是 yarn patch-package sane

diff --git a/node_modules/sane/src/node_watcher.js b/node_modules/sane/src/node_watcher.js

index ce90e4e..51b5e9a 100644

--- a/node_modules/sane/src/node_watcher.js

+++ b/node_modules/sane/src/node_watcher.js

@@ -287,7 +287,7 @@ module.exports = class NodeWatcher extends EventEmitter {

     fs.lstat(

       fullPath,

       function(error, stat) {

-        if (error && error.code !== 'ENOENT') {

+        if (!isIgnorableFileError(error)) {

           this.emit('error', error);

         } else if (!error && stat.isDirectory()) {

           // win32 emits usless change events on dirs.

@@ -304,7 +304,7 @@ module.exports = class NodeWatcher extends EventEmitter {

               this.emitEvent(ADD_EVENT, relativePath, stat);

             }

           }

-        } else {

+        } else if (!error) {

           let registered = this.registered(fullPath);

           if (error && error.code === 'ENOENT') {

             this.unregister(fullPath);

@@ -390,9 +390,14 @@ module.exports = class NodeWatcher extends EventEmitter {

  * @private

  */

 function isIgnorableFileError(error) {

+  if (error !== null)

+  {

+    console.log(error + " " + platform)

+  }

   return (

+    error === null ||

     error.code === 'ENOENT' ||

     // Workaround Windows node issue #4337.

-    (error.code === 'EPERM' && platform === 'win32')

+    (error.code === 'EPERM')

   );

 }

的结果

Answer 2

我遇到了同样的问题。对我来说，通过安装 watchman 解决了这个问题。我的 Mac 上没有安装 watchman。它可能会帮助某些人。

Answer 3

我遇到了这个确切的问题，我设法通过清理以前的构建（“ android/app/build ”删除整个构建文件夹）解决了它。以防万一，也删除“ node_modules ”并执行 npm i 或 yarn 。最后，运行项目 yarn start --reset-cache ，然后运行 yarn android 。