Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bundle error #138

Closed
ghost opened this issue Nov 23, 2018 · 4 comments
Closed

Bundle error #138

ghost opened this issue Nov 23, 2018 · 4 comments

Comments

@ghost
Copy link

ghost commented Nov 23, 2018

react: "16.6.1",
react-native: "0.57.5",
react-native-razorpay: "^2.0.14",

I am trying to integrate razorpay into exisiting RNN project, getting the following error on react-native run-android, Please help.

error: bundling failed: Error: jest-haste-map: Haste module naming collision:
Duplicate module name: react-native
Paths: /Users/crushy/edt/node_modules/react-native/package.json collides with /Users/crushy/edt/node_modules/react-native-razorpay/node_modules/react-native/package.json

This error is caused by hasteImpl returning the same name for different files.
at setModule (/Users/crushy/edt/node_modules/jest-haste-map/build/index.js:551:17)
at workerReply (/Users/crushy/edt/node_modules/jest-haste-map/build/index.js:613:9)
at
at process._tickCallback (internal/process/next_tick.js:188:7)

@iThink32
Copy link
Contributor

iThink32 commented Nov 23, 2018

@crushy26 first make sure you're using the latest version of react-native-razorpay , after which if you still find node modules in the react-native-razorpay package delete it and try.

@ghost
Copy link
Author

ghost commented Nov 23, 2018

Hi @iThink32, thank you for the quick reply. I managed to make it work by blacklisting the razor-pay's node_modules/react-native in metro bundler.

@iThink32
Copy link
Contributor

iThink32 commented Nov 23, 2018

@crushy26 that will also do but ideally speaking you can delete the node-modules folder in react-native-razorpay as we are not referencing it from there

@iThink32
Copy link
Contributor

closing as the issue is fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant