-
Notifications
You must be signed in to change notification settings - Fork 24.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Unable to resolve module & ENOENT: no such file or directory #5054
Comments
Hey shawnXiao, thanks for reporting this issue! React Native, as you've probably heard, is getting really popular and truth is we're getting a bit overwhelmed by the activity surrounding it. There are just too many issues for us to manage properly.
|
Hi there! A good thing to try in this case is |
It's a cache issue. See: #1924 You need to clear your packager cache: |
Fixed again with:
|
If clearing the cache still doesn't work for you, do you have a project |
Tried all the things in this thread.
Still getting the error: |
Follow up: the source code I checked out did not have an ios folder, causing the start up of the app to fail. I fixed that at the source and it started up fine after pulling new code. Just a very cryptic error message in this case. |
I have the same situation. My project only has a How can I create a new iOS project based on the android React Native project that I have? |
@marktani I think the answer is "find whoever made the project and get them to add the ios folder into their repo". Barring that, |
Right, thanks for the help! I got it working by doing I am the one who created the project in the first place, but I did so on a Linux machine. I think that's why there was no ios folder being created... |
That doesn't sound right. I don't have a linux vm handy to test it on though... On second thought I suppose it could be right because XCode won't run on linux. Wow, how lame would that be? Only being able to develop ios apps on a mac, even when using a cross-platform tool like RN? |
|
@julesmoretti thx! |
react-native upgrade will init your project config !!! |
Hi
I want to upgrade my React Native from 0.13.2 to 0.17, so as the instruction https://facebook.github.io/react-native/docs/upgrading.html#content
npm install --save react-native@0.17
and thenreact-native upgrade
But when I run my project, the terminal say this:
Unable to resolve module requestAnimationFrame from /Users/xiong/Documents/meituan/frontend/bee/node_modules/react-native/Libraries/Animated/src/AnimatedImplementation.js
Unable to resolve module keyMirror from /Users/xiong/Documents/meituan/frontend/bee/node_modules/react-native/Libraries/Components/WebView/WebView.ios.js
Unable to resolve module ReactPropTypes from /Users/xiong/Documents/meituan/frontend/bee/node_modules/react-native/Libraries/Inspector/ElementProperties.js
Unable to resolve module ReactDefaultPerf from /Users/xiong/Documents/meituan/frontend/bee/node_modules/react-native/Libraries/Utilities/RCTRenderingPerf.js
Unable to resolve module ReactPropTypes from /Users/xiong/Documents/meituan/frontend/bee/node_modules/react-native/Libraries/CameraRoll/CameraRoll.js
...
...
...
Unable to resolve module ReactPropTypes from /Users/xiong/Documents/meituan/frontend/bee/node_modules/react-native/Libraries/LayoutAnimation/LayoutAnimation.js
Unable to resolve module keyMirror from /Users/xiong/Documents/meituan/frontend/bee/node_modules/react-native/Libraries/LayoutAnimation/LayoutAnimation.js
[00:46:03] find dependencies (494ms)
[00:46:03] transform
transforming [======== ] 21% 65/311Error: ENOENT: no such file or directory, open '/Users/xiong/Documents/meituan/frontend/bee/node_modules/react-native/packager/react-packager/src/DependencyResolver/polyfills/prelude_dev.js'
at Error (native)
transforming [======================================= ] 98% 304/311[10:17:56] request:/index.ios.bundle?platform=ios&dev=true
Error: ENOENT: no such file or directory, open '/Users/xiong/Documents/meituan/frontend/bee/node_modules/react-native/packager/react-packager/src/DependencyResolver/polyfills/prelude_dev.js'
at Error (native)
The text was updated successfully, but these errors were encountered: