Unable to resolve module `react-native/Libraries/Renderer/shims/ReactNativePropRegistry` from `........./node_modules/native-base/dist/src/Utils/computeProps.js`
See original GitHub issueHi all,
I’m currently using
"native-base": "^2.2.1"
and
"react-native": "^0.44.3"
and I get an error saying
Unable to resolve module react-native/Libraries/Renderer/shims/ReactNativePropRegistry from path/to/node_modules/native-base/dist/src/Utils/computeProps.js
.
I believe this is a version issue and but not sure this is a native-base’s issue or react-native’s issue.
Has anyone had same problem before?
Issue Analytics
- State:
- Created 6 years ago
- Reactions:39
- Comments:35 (4 by maintainers)
Top Results From Across the Web
0.62.1. error: Error: Unable to resolve module `react-native ...
error: Error: Unable to resolve module react-native/Libraries/vendor/core/isEmpty from node_modules/deprecated-react-native-listview/index.js : react-native/ ...
Read more >Unable to Resolve Module in React Native App - Stack Overflow
Once I made a file called Index.js but imported index.js . Hello Case-sensitive-imports, my old friend. – KeshavDulal. Jan 8 ...
Read more >React Native, Typescript and VS Code: Unable to resolve ...
The problem with resolving modules turned out to be related to VS Code's typescript project helper.
Read more >Module not found | Can not resolve module in react - YouTube
Your browser can't play this video. ... Module not found | Can not resolve module in react ... 21K views 1 year ago...
Read more >Solved: Cannot find module react : npm install - YouTube
Transcript · Publish Your Own npm Module : Creating a Local Module (1 of 2) · How to Install Node Js in Windows...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@thinq4yourself seems to be a problem with native-base 2.2.1. Just remove the “^” and choose version 2.2.0. Delete everything and execute “npm install” again. It should work then, it took me almost an hour to find the reason for this bug.
I’m also using RN 0.45.1
I think using NB for enterprise project it’s very dangerous, I have this kind of errors every time I’m trying to upgrade or change a npm module 😦 And I’m losing many hours for that !