Unable to resolve module `./debugger-ui/ui.cc464243.js` from ``

mmafrar commented 4 years ago

Environment

System: OS: macOS High Sierra 10.13.6 CPU: (4) x64 Intel(R) Core(TM) i5-5250U CPU @ 1.60GHz Memory: 2.28 GB / 8.00 GB Shell: 3.2.57 - /bin/bash Binaries: Node: 13.7.0 - /usr/local/bin/node Yarn: Not Found npm: 6.13.6 - /usr/local/bin/npm Watchman: 4.9.0 - /usr/local/bin/watchman SDKs: iOS SDK: Platforms: iOS 12.1, macOS 10.14, tvOS 12.1, watchOS 5.1 Android SDK: Not Found IDEs: Android Studio: Not Found Xcode: 10.1/10B61 - /usr/bin/xcodebuild Languages: Python: 2.7.10 - /usr/bin/python npmPackages: @react-native-community/cli: Not Found react: ^16.11.0 => 16.11.0 react-native: ^0.62.0 => 0.62.0 npmGlobalPackages: react-native: Not Found

Description

Hi there! I'm a React Native newbie working on an interesting side project. Recently I updated project's @react-native-community/cli-debugger-ui version to 4.2.1 and had to come across below issue. Tried several workarounds, nothing worked. Reverting back @react-native-community/cli-debugger-ui version to 3.0.0 resolved the issue.

Error: Unable to resolve module ./debugger-ui/ui.cc464243.js from ``:

None of these files exist:

debugger-ui/ui.cc464243.js(.native|.native.js|.js|.native.json|.json|.native.ts|.ts|.native.tsx|.tsx)
debugger-ui/ui.cc464243.js/index(.native|.native.js|.js|.native.json|.json|.native.ts|.ts|.native.tsx|.tsx) at ModuleResolver.resolveDependency (DIR/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:163:15) at ResolutionRequest.resolveDependency (DIR/node_modules/metro/src/node-haste/DependencyGraph/ResolutionRequest.js:52:18) at DependencyGraph.resolveDependency (DIR/node_modules/metro/src/node-haste/DependencyGraph.js:287:16) at DIR/node_modules/metro/src/lib/transformHelpers.js:267:42 at Server. (DIR/node_modules/metro/src/Server.js:841:41) at Generator.next () at asyncGeneratorStep (DIR/node_modules/metro/src/Server.js:99:24) at _next (DIR/node_modules/metro/src/Server.js:119:9)

Reproducible Demo

Setup a project with @react-native-community/cli-debugger-ui using version 3.0.0.
Build and run the application and enable debugger.
Update @react-native-community/cli-debugger-ui to version 4.2.1.
Rerun the app and above error will be displayed on Metro Bundler console.
Revert @react-native-community/cli-debugger-ui back to version 3.0.0.
Rerun the application and issue will disappear.

mnikolic10 commented 4 years ago

this was the solution for me https://stackoverflow.com/a/60755519/1557613

Hard refresh of the debugger window also worked for me (cmd + shift + r)

wwwtony5488 commented 4 years ago

Just try all the ways I found still failed, the easiest one for me is to clone the repository, install and build again.

kevmmdev commented 4 years ago

this was the solution for me https://stackoverflow.com/a/60755519/1557613

Hard refresh of the debugger window also worked for me (cmd + shift + r)

yeah but I noticed we have to redo this if we restart our machines.

thebne commented 4 years ago

This still happens to me. Tried all the solutions: https://stackoverflow.com/a/60755519/1557613 https://github.com/react-native-community/cli/issues/1081#issuecomment-614223917 https://github.com/react-native-community/cli/issues/1081#issuecomment-609648148 https://github.com/facebook/react-native/issues/28531#issuecomment-617101194

garrettg123 commented 4 years ago

I'm getting this on RN 0.61.4, expo 37.0.12. Using yarn workspaces, not sure if that's relevant.

gmjelle commented 4 years ago

Here as well. Bare expo project w/

RN @ 0.61.5
Expo @ 37.0.3 Was working fine till an hour ago. Had to reboot my laptop, and afterwards project wouldn't work anymore.

travisseh commented 4 years ago

this was the solution for me https://stackoverflow.com/a/60755519/1557613

Hard refresh of the debugger window also worked for me (cmd + shift + r)

This worked for me too!

omerfaran commented 4 years ago

I tried all the solutions suggested here and nothing worked for me, still the exact same error.

Is there an alternative to that remote debugger?

omerfaran commented 4 years ago

After deleting my cache and reloading chrome it didn't help, I even tried to restart my pc and nothing of course. But then today it started working again without me doing anything. Really strange

R4DIC4L commented 4 years ago

@timhagn solution of setting the resolutions to RN debugger CLI version 4.7.0 and installing that specific version worked for me. I'm using RN v0.62.2. I also reset the cache after npm install and before re-running with npx.

R4DIC4L commented 4 years ago

If it helps someone, I have noticed that this error appears also after changing something in package.json such as the app version and not use npm install command before running. If I ran install after changing the version property, the package-lock.json probably changed and the debugger worked again.

I didn't expect that the version would affect the debugger, since without Debugging on, the application still works. Guess it's best to always run the install command after changing something in package.json, even for options unrelated to packages.

crutchcorn commented 4 years ago

None of these solutions worked for me, but the note about onPress being time-sensitive lead me to the right result:

https://github.com/facebook/react-native/issues/28531#issuecomment-640342824

sivasaiakhil commented 4 years ago

I got same the issue. when I open the debugger in the console I am getting this error. I spent more to debug this error.

Solution I used resolutions in the package.json.

"resolutions": {
    "@react-native-community/cli-debugger-ui": "4.7.0"
  },

then I deleted package-lock.json and node_modules. then I reinstalled node modules, synced with the android studio. clean the project. Finally, used react-native run-android

mikeRChambers610 commented 4 years ago

Having the same issue after upgrading to Expo SDK 38 and RN 0.62. None of the suggested fixes have worked.

samiede commented 4 years ago

I have the same problem, no expo, but RN 0.62.2, none of the fixes worked. Since the error lies in the cli-debugger, probably, the App still runs when started with android studio, so maybe that might help a few people continue development?

chandan1602 commented 4 years ago

For expo users, I think you accidently turned on Live Debugging in Expo, Just clear Expo's Cache and Data from your Phone, and everything will be back to normal.

mikeRChambers610 commented 4 years ago

For expo users, I think you accidently turned on Live Debugging in Expo, Just clear Expo's Cache and Data from your Phone, and everything will be back to normal.

@chandan1602

I tried uninstalling the app on the simulator and reinstalling. That didnt help. Is there another way to clear cache and data from the expo app?

chandan1602 commented 4 years ago

For expo users, I think you accidently turned on Live Debugging in Expo, Just clear Expo's Cache and Data from your Phone, and everything will be back to normal.

@chandan1602

I tried uninstalling the app on the simulator and reinstalling. That didnt help. Is there another way to clear cache and data from the expo app?

Do you get the same error now, my method was plain and simple, i just opened the app info, and from there i cleared the app cache and data, also i ran expo r -c and collectively that worked for me

m-jachym commented 4 years ago

Unfortunately none of the above solutions work for me 😢

samiede commented 4 years ago

After updating to RN 63.0, I still get the error, but the app compiles nonetheless and is debuggable.

banumolu commented 4 years ago

I was getting this error => Error: Unable to resolve module `./debugger-ui/debuggerWorker.d9da4ed7` from ``: I am able to solve this by doing Ctrl+C to stop bundle and running npm start again

ovy9086 commented 4 years ago

this is just retarded. spending 1 hour to try and debug this app...

muthuspark commented 4 years ago

For some reason what worked for me was to use my IP like 192.168.31.91:8081/debugger-ui instead of the default localhost:8081/debugger-ui

thijs-qv commented 4 years ago

Running "empty cache and hard reload" on the debugger page in Chrome as mentioned here fixes the issue for me.

m-jachym commented 4 years ago

After struggling with this issue for a long time i tried a combination of methods which I have found in this topic and expo forum, and it works for me!

I did what notbrent described in this post , and in package.json add this line ( yep, in 3.0.0 version)

"resolutions": { "@react-native-community/cli-debugger-ui": "3.0.0" },

delete this:

"plugins": [ "@babel/plugin-proposal-class-properties" ]

Hope it will help somebody

m-jachym commented 4 years ago

And after few days it just stop working.

Now I don't have any error message. I just can't touch anything.

My god, how shitty it is...

xclidongbo commented 4 years ago

Same Error. RN version: 0.63.2

ammar299 commented 4 years ago

above solutions no work for me....

lovetofail commented 4 years ago

I added "resolutions" but it didn't help.

"resolutions": {
   "@react-native-community/cli-debugger-ui": "4.7.0"
 },

After that I did "yarn add react-devtools-core" and the error went away.

ryantando commented 4 years ago

Been 2 days and still havent found the fix on this

dccabao commented 4 years ago

Still no fix for this? Should we go flutter now?

ryantando commented 4 years ago

Still no fix for this? Should we go flutter now?

On my side the issue cause by react-native-reanimated@2, I removed it and the issue disappear. maybe try to check your libs

dccabao commented 4 years ago

Still no fix for this? Should we go flutter now?

On my side the issue cause by react-native-reanimated@2, I removed it and the issue disappear. maybe try to check your libs

How to know what's causing the issue from the libraries tho

m-jachym commented 4 years ago

Still no fix for this? Should we go flutter now?

On my side the issue cause by react-native-reanimated@2, I removed it and the issue disappear. maybe try to check your libs

How to know what's causing the issue from the libraries tho

It's not only about libraries. I tried to start new project on new machine and it sometimes works, sometimes not...

joeshub commented 4 years ago

this is such a mess, does anyone actually have a fix?

AnthonyBuilder commented 4 years ago

I tried to delete the build in android/app/build folder and the node_modules folder, on the terminal I launched npm install && npm cache clean --force, then navigated to the android folder and ran ./gradlew installDebug checked syntax errors when importing libraries and two of them were missing the braces {} between the variable name, just so it worked, try to observe if the libraries are compatible with the versions of another library, I believe it is a bug between the version of react and the requested libraries

SwatDoge commented 4 years ago

For expo users, I think you accidently turned on Live Debugging in Expo, Just clear Expo's Cache and Data from your Phone, and everything will be back to normal.

Thank you so much!!! saved my project

ZehaIrawan commented 4 years ago

Mac OS Catalina Android Emulator "react-native": "0.63.2"

I've tried to clear the cache and reinstalling node modules, none of that works for me. Reinstalling the app in the emulator seems to do the trick.

Hope it helps!

aposhettigar commented 4 years ago

Does anyone have a fix for this yet?

yadinbk commented 4 years ago

have the same problem' non of the above helps.

specific Error

Error: Unable to resolve module ./debugger-ui/ui.bcd3f9d1.js from ``:

None of these files exist:

debugger-ui\ui.bcd3f9d1.js(.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\ui.bcd3f9d1.js\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 (C:\Users\yadin\DoneWithIt2\node_modules\metro\src\node-haste\DependencyGraph\ModuleResolution.js:163:15) at ResolutionRequest.resolveDependency (C:\Users\yadin\DoneWithIt2\node_modules\metro\src\node-haste\DependencyGraph\ResolutionRequest.js:52:18) at DependencyGraph.resolveDependency (C:\Users\yadin\DoneWithIt2\node_modules\metro\src\node-haste\DependencyGraph.js:287:16) at C:\Users\yadin\DoneWithIt2\node_modules\metro\src\lib\transformHelpers.js:267:42 at Server. (C:\Users\yadin\DoneWithIt2\node_modules\metro\src\Server.js:841:41) at Generator.next () at asyncGeneratorStep (C:\Users\yadin\DoneWithIt2\node_modules\metro\src\Server.js:99:24) at _next (C:\Users\yadin\DoneWithIt2\node_modules\metro\src\Server.js:119:9)

rahamin1 commented 4 years ago

Same problem on Windows 10 with RN 0.62.2

jayampathiadhikari commented 4 years ago

If someones having the problem still, try using react-navigation v4. I had v5 and downgraded it to v4 and it worked.

CacaoRick commented 4 years ago

In expo app, I resolve by install react-native-debugger-open

yarn add -D react-native-debugger-open

And add this script to package.json, use yarn debug to start expo dev server.

"debug": "REACT_DEBUGGER=\"rndebugger-open --open --expo\" expo start"

With --expo flag, react-native-debugger-open auto use expo's correct port.

Turn on Debug Remote JS in expo app, react-native-debugger will auto launch, and redux-devtools is work.

I use in expo 39 and react-native-debugger installed. Both redux-devtools-extension and window.__REDUX_DEVTOOLS_EXTENSION__ are work.

corelmax commented 4 years ago

faced the same and solved by just restarting the bundler with --reset-cache.

yarn start --reset-cache

mathew3 commented 3 years ago

I encountered the same issue, so far I've been working only with the iOS simulator

RN version:

"react": "16.13.1",
"react-native": "0.63.3",

what worked for me was removing the app from the simulator and installing it again

MarshallPatryk commented 3 years ago

This problem I resolved by stoping debugging remote JS in expo app.

brentvatne commented 3 years ago

if you want to get a proper fix for this, if you're using react-native 0.63 (or expo sdk 39+) then delete your node_modules and lockfile (yarn.lock or package-lock.json) and run yarn/npm install again. this will pull in the latest version of @react-native-community/cli that includes a fix

rahamin1 commented 3 years ago

if you want to get a proper fix for this, if you're using react-native 0.63 (or expo sdk 39+) then delete your node_modules and lockfile (yarn.lock or package-lock.json) and run yarn/npm install again. this will pull in the latest version of @react-native-community/cli that includes a fix

Tried that. Didn't help.

https://github.com/facebook/react-native/issues/28844#issuecomment-730535093

brentvatne commented 3 years ago

sorry i'm not sure what your issue might be. could you try to investigate the root cause and report back?

rahamin1 commented 3 years ago

No idea either...

react-native-community / cli