博览会:无法解析模块“./调试器

本文介绍了博览会:无法解析模块“./调试器的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

重新加载后，我的应用已停止加载.

After a reload my app has stopped loading.

我已经在模拟器和2个真正的devives(android和ios)上进行了尝试.

I have tried on both emulators and 2 real devives, android and ios.

错误是:

错误:无法从``:

Error: Unable to resolve module ./debugger-ui/debuggerWorker.d9da4ed7 from ``:

有时我会收到错误消息无法找到实例".

and occassionally I will get the error, 'unable to locate instance'.

我尝试了以下操作:

清晰的守望者手表:watchman watch-del-all.

删除node_modules文件夹:rm -rf node_modules && npm install.

重置Metro Bundler缓存:rm -rf /tmp/metro-bundler-cache-*或npm start -- --reset-cache.

删除急速缓存:rm -rf /tmp/haste-map-react-native-packager-*.

重新启动计算机.

Clear watchman watches: watchman watch-del-all .

Delete the node_modules folder: rm -rf node_modules && npm install .

Reset Metro Bundler cache: rm -rf /tmp/metro-bundler-cache-* or npm start -- --reset-cache .

Remove haste cache: rm -rf /tmp/haste-map-react-native-packager-* .

Restart the computer. Expo CLI 3.11.3 environment info: System: OS: macOS 10.15.2 Shell: 5.7.1 - /bin/zsh Binaries: Node: 12.8.0 - ~/.nvm/versions/node/v12.8.0/bin/node Yarn: 1.19.1 - /usr/local/bin/yarn npm: 6.13.4 - ~/.nvm/versions/node/v12.8.0/bin/npm Watchman: 4.9.0 - /usr/local/bin/watchman IDEs: Android Studio: 3.5 AI-191.8026.42.35.5791312 Xcode: 11.2/11B41 - /usr/bin/xcodebuild npmPackages: expo: ~36.0.0 => 36.0.2 react: ~16.9.0 => 16.9.0 react-native: github/expo/react-native/archive/sdk-36.0.0.tar.gz => 0.61.4 react-navigation: ^4.0.10 => 4.0.10 npmGlobalPackages: expo-cli: 3.11.3

关于我还能尝试解决什么的任何想法?

Any ideas on what else I can try to resolve this?

下面的完整错误:

Error: Unable to resolve module `./debugger-ui/debuggerWorker.d9da4ed7` from ``: None of these files exist: * debugger-ui/debuggerWorker.d9da4ed7(.native|.native.expo.ts|.expo.ts|.native.expo.tsx|.expo.tsx|.native.expo.js|.expo.js|.native.expo.jsx|.expo.jsx|.native.ts|.ts|.native.tsx|.tsx|.native.js|.js|.native.jsx|.jsx|.native.json|.json|.native.wasm|.wasm) * debugger-ui/debuggerWorker.d9da4ed7/index(.native|.native.expo.ts|.expo.ts|.native.expo.tsx|.expo.tsx|.native.expo.js|.expo.js|.native.expo.jsx|.expo.jsx|.native.ts|.ts|.native.tsx|.tsx|.native.js|.js|.native.jsx|.jsx|.native.json|.json|.native.wasm|.wasm) at ModuleResolver.resolveDependency (/Users/serdarmustafa/task_location_namespace/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:163:15) at ResolutionRequest.resolveDependency (/Users/serdarmustafa/task_location_namespace/node_modules/metro/src/node-haste/DependencyGraph/ResolutionRequest.js:52:18) at DependencyGraph.resolveDependency (/Users/serdarmustafa/task_location_namespace/node_modules/metro/src/node-haste/DependencyGraph.js:282:16) at /Users/serdarmustafa/task_location_namespace/node_modules/metro/src/lib/transformHelpers.js:267:42 at /Users/serdarmustafa/task_location_namespace/node_modules/metro/src/Server.js:1305:37 at Generator.next (<anonymous>) at asyncGeneratorStep (/Users/serdarmustafa/task_location_namespace/node_modules/metro/src/Server.js:99:24) at _next (/Users/serdarmustafa/task_location_namespace/node_modules/metro/src/Server.js:119:9) at processTicksAndRejections (internal/process/task_queues.js:85:5)

推荐答案

更新:我不再使用expo，从注释中看，expo似乎已更改为npm软件包.这个答案可能已经过时了.

在package.json中检查您的npm版本.

"dependencies": { "@react-native-firebase/app": "^6.0.0", "@react-native-firebase/auth": "^6.0.0", "acorn": "^7.0.0", "axios": "^0.19.1", "expo-web-browser": "^8.0.0", "i": "^0.3.6", "loadash": "^1.0.0", "npm": "^6.11.3",

就我而言，我做了npm update并且我的npm版本在dependecy中移到了导致重大更改的最新版本

In my case, I did npm update and my npm version in dependecy moved to the latest version which caused breaking changes