React Native - Error: Unable to resolve module ‘stream’
See original GitHub issueReopening this issue, can the fix from aws-amplify v0.1.34 be added to aws-amplify-react-native please
There appears to be a node core module imported from this package via the aws-amplify package.
error: bundling failed: Error: Unable to resolve module
streamfrom/Users/joshua/Documents/side-projects/RoomShakeClient/node_modules/cipher-base/index.js: Module does not exist in the module map Does anybody know a fix for this? I’ve downgraded a few versions but it doesn’t seem to help
Issue Analytics
- State:
- Created 6 years ago
- Comments:26 (8 by maintainers)
Top Results From Across the Web
Unable to resolve module `stream` - Stack Overflow
just install stream using npm install stream and run the project again.
Read more >Error: Unable to resolve module 'stream' · Issue #33981 - GitHub
I have tried any clear command and action. ... If you are sure the module exists, try these steps: Clear watchman watches: watchman...
Read more >can't resolve 'stream' in cipher-base - You.com | The AI Search ...
Error : Unable to resolve module stream from C:\**\node_modules\cipher-base\index.js: stream could not be found within the project.
Read more >Unable to resolve module when trying to build-React Native
Coding example for the question Unable to resolve module when trying to build-React Native.
Read more >stream-chat-react-native-core - npm
The official React Native and Expo components for Stream Chat, a service for building chat applications. Latest version: 5.7.0, ...
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
Using npm instead of yarn solved the issue for us. Not sure what the exact reason is but that might be something to look into.
It requires node.js modules (e.g. stream). With latest versions of RN these aren’t picked up by the packager.