Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

ReactNativePropRegistry not found for react-native >= 0.44

See original GitHub issue

Hey!

I’m currently trying to get this running with react-native >= 0.44. Unfortunately the imports seem to be wrong:

error: bundling: UnableToResolveError: Unable to resolve module `react-native/Libraries/Renderer/shims/ReactNativePropRegistry` from `my-project/node_modules/react-native-easy-grid/Utils/computeProps.js`: Module does not exist in the module map or in these directories:
  my-project/node_modules/react-native/Libraries/Renderer/shims
,   my-project/node_modules/react-native/Libraries/Renderer/shims

This might be related to https://github.com/facebook/react-native/issues/4968
To resolve try the following:
  1. Clear watchman watches: `watchman watch-del-all`.
  2. Delete the `node_modules` folder: `rm -rf node_modules && npm install`.
  3. Reset packager cache: `rm -fr $TMPDIR/react-*` or `npm start -- --reset-cache`.
    at ResolutionRequest._resolveNodeDependency (my-project/node_modules/react-native/packager/src/node-haste/DependencyGraph/ResolutionRequest.js:394:11)
    at ResolutionRequest.resolveDependency (my-project/node_modules/react-native/packager/src/node-haste/DependencyGraph/ResolutionRequest.js:141:29)
    at dependencyNames.map.name (my-project/node_modules/react-native/packager/src/node-haste/DependencyGraph/ResolutionRequest.js:145:59)
    at Array.map (native)
    at ResolutionRequest.resolveModuleDependencies (my-project/node_modules/react-native/packager/src/node-haste/DependencyGraph/ResolutionRequest.js:145:42)
    at Promise.resolve.then (my-project/node_modules/react-native/packager/src/node-haste/DependencyGraph/ResolutionRequest.js:169:21)
    at process._tickCallback (internal/process/next_tick.js:103:7)

I suspect this is highly related to https://github.com/GeekyAnts/NativeBase/issues/307? If yes I guess those fixes should be applied here also? I’d be willing to contribute those but wanted to make sure first that is actually something both wanted & needed.

Thanks Tim

Issue Analytics

State:
Created 6 years ago
Reactions:2
Comments:11 (1 by maintainers)

Top GitHub Comments

13reactions

poptocrackcommented, Jul 12, 2017

There is a workaround : npm install --save react-native-easy-grid@0.1.13 Install this version until they fix the 0.1.11. It seems there is also a mistake ine the version number, 0.1.11 is the latest.

2reactions

bobmuldercommented, Oct 12, 2017

That sounds good @SupriyaKalghatgi. When do you expect to have it fixed? (can’t nearly work on my project now because of this bug 😦).

Top Results From Across the Web

Issues - GitHub

"react-native": "^0.44.3" and I get an error saying. Unable to resolve module react-native/Libraries/Renderer/shims/ReactNativePropRegistry from ...

react-native: command not found - Stack Overflow

After adding right path to the PATH variable issue is resolved. Below are the steps to find the right path. 1. Enter: npm...

Common Issues Coming in First React Native Project Set Up.

Header Files Not Found in XCode: This issue is so common and on doing some R&D you find that this issue is due...

[Solved]-React Native ios build failed on react-native run-ios

React native run iOS build failed error: Multiple commands produceEntry, ":CFBundleIdentifier", Does Not Exist · Run a React Native iOS release build from ......

Build fails on bitrise but works locally - ld: library not found for

Bitrise Build Issue Report template Description of the issue I have upgrade from react-native 0.44.3 to 0.50.0, I also use a library for ......