react-native-paper v4.6.0 to v4.7.0 build fails with error Unable to resolve module `./CheckboxElements`
See original GitHub issueCurrent behavior
After upgrading to v4.7.0 from v4.6.0 the app build fails with the error unable to resolve module CheckboxElements.
Error:
error: Error: Unable to resolve module ./CheckboxElements from node_modules\react-native-paper\src\components\Checkbox\Checkbox.tsx:
Expected behavior
App to run successfully.
What have you tried
Downgrading to v4.6.0 resolves the issue
Your Environment
| software | version |
|---|---|
| ios or android | android |
| react-native | 0.63.4 |
| react-native-paper | 4.7.0 |
| node | v14.10.1 |
| npm or yarn | npm |
| npm | 6.14…8 |
| expo sdk | |
| react-native-vector-icons | 7.1.0 |
note: I’m using react-native CLI and not EXPO.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Unable to resolve module react-native when using pnpm
I am using pnpm version 7.17.0, react native version 0.70.6, and node version v19.1.0, on M1 macos 13.0.1. It seems like pnpm isn' ......
Read more >unable to resolve module react-native-elements - You.com
I'm try to run expo project on iOS. When I run command expo start , Metro bundle starts successfully but when I click...
Read more >Troubleshooting | React Native Elements
On this page you can find solutions to commonly encountered issues. ... This error occurs when trying to import a component that doesn't...
Read more >react-native-paper - npm
Material design for React Native. Latest version: 5.1.0, last published: 7 days ago. Start using react-native-paper in your project by ...
Read more >Troubleshooting | React Navigation
Before troubleshooting an issue, make sure that you have upgraded to the latest ... I'm getting an error "Unable to resolve module" after...
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

npm start -- --reset-cachesolved the problem for me.See #2447