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.
Unable to resolve PropTypes
See original GitHub issueWith version 6.0.0 I get:
Unable to resolve module `../utils/PropTypes` from `.../node_modules/react-redux/lib/components/Provider.js`: The module `../utils/PropTypes` could not be found from `.../node_modules/react-redux/lib/components/Provider.js`. Indeed, none of these files exist:
And indeed, I cannot find that file either. Any suggestions to what could be happening?
Issue Analytics
- State:
- Created 5 years ago
- Reactions:12
- Comments:7 (1 by maintainers)
Top Results From Across the Web
react native - Unable to resolve module prop-types, but grep ...
I am just learning React Native. Full error message is here: Unable to resolve module prop-types from /Users/raarts/work/MobileApp/app/ ...
Read more >Unable to resolve module `prop-types` · Issue #1 - GitHub
This is the error message im getting. All i did was copy the git hub, npm install. I run mpm start and react0native...
Read more >prop-types - npm
Start using prop-types in your project by running `npm i prop-types`. ... It should return an Error // object if the validation fails....
Read more >Don't Call PropTypes Warning - React
Don't call PropTypes directly. Using PropTypes in any other way than annotating React components with them is no longer supported: var apiShape =...
Read more >Module not found: Error: Can't resolve 'prop-types'
0, I was getting an error Module not found: Error: Can't resolve 'prop-types' , Because prop-types has been removed from the react core...
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 Free
Top 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
Assuming you guys experienced the issue like me on react-native, you should reinstall the deps, re-package the app and launch the packager using
--reset-cache, which would solve the problem.@balthazar Thanks. Your way of “resetting” the environment helped us. We rebuilt our environment, so like deleting
node_modulesand just reinstalled everything again.