React Native: "Unable to resolve module react-swipeable-views-utils"
See original GitHub issueHi, thanks for your work!
I updated the react-swipeable-views to 0.9.1 and changed the import statements to:
import { virtualize } from 'react-swipeable-views-utils';
import SwipeableViews from 'react-swipeable-views-native';
The packager is unable to resolve react-swipeable-views-utils module. I am using the native version.
I also tried to install react-swipeable-views-utils as a separate package, the packager is unable to resolve react-addons-shallow-compare then. Installing the shallow-compare module gives me an “Unable to resolve keycode” error.
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Unable to Resolve Module in React Native App - Stack Overflow
I'm getting an error in React Native saying it can't resolve a module. It's saying a certain folder doesn't exist but the path...
Read more >0.62.1. error: Error: Unable to resolve module `react-native ...
Build completes but application fails to start with the error: error: Error: Unable to resolve module react-native/Libraries/vendor/core/isEmpty from ...
Read more >Troubleshooting | React Navigation
I'm getting an error "Unable to resolve module" after updating to the latest ... Error: While trying to resolve module "@react-navigation/native" from file ......
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 >Android Native Modules
You can find your Android project here within a React Native app: ... module method call, if it's a function, is treated as...
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

I confirm, I have tried it, it’s 💯 % fixed. Thanks for the report.
@habib786 please try to clear cache and reinstall npm packages: