Skip to content
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 react/lib/ReactDebugCurrentFrame #13017

Closed
gold-duo opened this issue Mar 19, 2017 · 9 comments
Closed

Unable to resolve module react/lib/ReactDebugCurrentFrame #13017

gold-duo opened this issue Mar 19, 2017 · 9 comments
Labels
Resolution: Locked This issue was locked by the bot.

Comments

@gold-duo
Copy link

gold-duo commented Mar 19, 2017

Unable to resolve module react/lib/ReactDebugCurrentFrame from ....\node_modules\react-native\Libraries\Renderer\src\renderers\shared\stack\reconciler\ReactCompositeComponent.js: Module does not exist in the module map or in these directories:
...\node_modules\react\lib

@gold-duo
Copy link
Author

gold-duo commented Mar 19, 2017

When I update to 0.43.0 - rc. 1 version
npm WARN react-native@0.43.0-rc.1 requires a peer of react@~16.0.0-alpha.3 but none was installed.
npm install -save react@~16.0.0-alpha.3
To solve the problem

@tigerohuang
Copy link

@droidwolf, where can I find the newest version of react and react-native such as react@~16.0.0-alpha.3 and react-native@0.43.0-rc.1 , I only can find 0.42.3

@gold-duo
Copy link
Author

gold-duo commented Apr 1, 2017

@ivanzotov
Copy link
Contributor

+1

@wilomgfx
Copy link

wilomgfx commented Apr 4, 2017

I got that error as well on react ^15.4.2 and react-native 0.43, but upgrading to 16.0.0-alpha.6 fixed it. So id say.. stay away from 0.43 or use react 16.0.0-alpha.6

@itinance
Copy link
Contributor

Seems that RN 0.43 shouldn't made it out of the door in this stage, particularly when essential Components like ListView got deprecated as 0.43 is not ready for serious usage yet.

@callmetwan
Copy link

callmetwan commented May 3, 2017

I was also having trouble upgrading. I decided to start a brand new project and migrate things over as a last resort.

I get @droidwolf's error on init of a brand new project, not changing a single thing.

I'm on the latest version of MacOS and Xcode. What else am I missing?

EDIT: I restarted the simulator (not the packager, but the simulator) and everything seems to work now. sigh

@digitaldavenyc
Copy link

digitaldavenyc commented May 12, 2017

This is a library issue, restarting xcode, cleaning your build, clearing npm cache and running react-native run-ios fixes the issue. Not sure which one ... I really hate node libraries sometimes.

@jose2007kj
Copy link

"react": "16.0.0-alpha.6", this version got me working

@facebook facebook locked as resolved and limited conversation to collaborators May 24, 2018
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Jul 18, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests

9 participants