Clear mediacentral cache12/16/2023 If there are some other solutions, please suggest. System Images: android-28 | Google APIs Intel x86 Atom, android-28 | Google Play Intel x86 Atom, android-29 | Google APIs Intel x86 Atom Watchman: 4.9.0 - /usr/local/bin/watchman Watchman watch-del-all & rm -rf $TMPDIR/react-native-packager-cache-* & rm -rf $TMPDIR/react-* & rm -rf $TMPDIR/metro-* & rm -rf node_modules/ & yarn cache clean -force & yarn install & react-native start -reset-cacheĬPU: (8) 圆4 Intel(R) Core(TM) i5-8257U CPU 1.40GHz React-native start -reset-cache not working.īelow command is also not working for me. I am using RN 0.59Įrror: bundling failed: Error: Unable to resolve module from /: Module does not exist in the Haste module map This worked for me, the metro cache file names have changed. So the whole command means to recursively purge any files that start with "metro-" or "haste-map-" from your system's temporary directory. $TMPDIR/metro-* means every file/folder that matches with the * wildcard (so metro-foo as well as metro-bar).$TMPDIR is the environment variable for your systems temporary directory, it isn't the same on every platform.rm -rf means to recursively remove all files/folders at the following path.It is very frustrating to have to go to 6 different places to get this the command: rm -rf $TMPDIR/metro-* & rm -rf $TMPDIR/haste-map-* That helped, since I could at least know that my application was working in theory. For sanity, I finally went and Dockerized the bundler and pointed the native app at the container just to make sure I wasn't crazy. I just ran into an issue that required figuring out how to purge everything related to a React Native build and I feel all the pain here.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |