Duplicate module name: react-native

[sjenit]

Loading dependency graph...(node:13752) UnhandledPromiseRejectionWarning: Error: jest-haste-map: @providesModule naming collision:
  Duplicate module name: react-native
  Paths: E:\my_project\node_modules\react-native-razorpay\node_modules\react-native\package.json collides with E:\my_project\node_modules\react-native\package.json

This error is caused by a @providesModule declaration with the same name across two different files.
    at setModule (E:\my_project\node_modules\metro\node_modules\jest-haste-map\build\index.js:462:17)
    at workerReply (E:\my_project\node_modules\metro\node_modules\jest-haste-map\build\index.js:512:9)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:188:7)
(node:13752) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
(node:13752) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:13752) UnhandledPromiseRejectionWarning: Error: jest-haste-map: @providesModule naming collision:
  Duplicate module name: react-native
  Paths: E:\my_project\node_modules\react-native-razorpay\node_modules\react-native\package.json collides with E:\my_project\node_modules\react-native\package.json

This error is caused by a @providesModule declaration with the same name across two different files.
    at setModule (E:\my_project\node_modules\metro\node_modules\jest-haste-map\build\index.js:462:17)
    at workerReply (E:\my_project\node_modules\metro\node_modules\jest-haste-map\build\index.js:512:9)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:188:7)
(node:13752) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 3)

Getting above error after upgrading to latest version (2.0.13) of the package.
clean and npm --reset-cache already tried but didn't work.

Issue is quite similar to:
#93
#42

[iThink32]

@sjenit this is due to a derived data issue , I request you to delete it and try again , moreover if you look closely at our package we do not have a node modules folder anymore.
Try deleting react-native-razorpay from your node modules folder and run npm install.

[sjenit]

@iThink32 Issue still persists. I tried deleting react-native-razorpay and running npm install.
Also, I can see node_modules folder inside react-native-razorpay package. Please let me know if i am missing anything. It is working absolutely fine when I downgrade to the older version 2.0.10.

[Balasnest]

@iThink32 There is no one time fix for this problem. Its keep arising whenever do npm install. We need to repeat the step again and again to resolve.

rm -rf ./node_modules && npm install
npm cache clean
npm start -- --reset-cache

After doing this, most of the time node_modules appear again.
@sjenit Currently what you can do it, when your project runs/resolved, immediately copy the react-native-razorpay from node_modules and keep it seperately. When this issue arise replace the package. That is how I resolved it temporarily.

[iThink32]

@Balasnest its a react-native issue , I told you in the beginning itself react-native is not at all stable for Xcode 10 , coming to our package as I mentioned we do not ship node_modules , you can have a look at the new package yourself.

[amrita019]

I just deleted the node module folder from react-native-razorpay, it worked for me, maybe will work for you too.

[iThink32]

@amrita019 our latest framework does not contain a node modules folder , please check our latest framework carefully.

[iThink32]

closing due to inactivity.

[Balasnest]

@iThink32 will that latest framework works in react-native: 0.56 and Xcode: 9.3 | 9.4 ? Which is stable one for 0.56?

[iThink32]

@Balasnest please reopen issues before commenting.Anyway our latest framework will only work on Xcode 10 , react-native i.e 0.57.1 ,react version 16.5.0 and above.

[salujaharkirat]

@iThink32 if I remove the react-native folder inside react-native-razorpay it works fine in development mode but while creating a production build in android, I am getting following error:-

> Could not list contents of '/Users/harkirat/wealthy/bumblebee-new/node_modules/react-native-razorpay/node_modules/.bin/react-native'. Couldn't follow symbolic link.

react-native 0.57.2
react 16.5.0
react-native-razorpay 2.0.14

Pleas help?

[Balasnest]

@jinxac Try removing react-native-razorpay/node_modules/ and project/node_modules/.bin/ folder

[iThink32]

@jinxac no this is not a good fix , it is working fine for me ,try the example on this repo on a separate folder.React-native is unstable for Xcode 10 , delete derived data , stop your metro bundler instance and try again.Also google for alternative solutions.
@Balasnest our latest package does not have a node modules folder , if you see a node modules folder in react-native-razorpay you are using an old version.

[iThink32]

closing due to inactivity.

[paddy57]

I'm getting the same error, how can i resolve it.
Duplicate module name: react-animated

[salujaharkirat]

remove node_modules/react-native-razorpay/node_modules/react-native @paddy57

[paddy57]

that just one time fix, next time if i do npm install the node module folder will regenerate again @jinxac

[Balasnest]

@paddy57 Try blacklisting the directory.
how-to-make-react-native-packager-ignore-certain-directories

[iThink32]

@paddy57 yes blacklisting is the right way forward but pls analyse the directories that you are blacklisting.

[ashutoshshubam]

use "react-native-razorpay": "https://github.com/ashutoshshubam/react-native-razorpay",
its working. In package.json file

[iThink32]

@ashutoshshubam I appreciate that you have forked react-native-razorpay and are trying to help but in such a case a user following your advice will not be able to run npm update and get the latest updates from us , it would be better if you could post your solution instead and give your repo's link as a reference to it.

[ashutoshshubam]

@iThink32 actually its not possible without forking because react-native-razorpay is using react-native": "0.57.1 and they have both have their own package.json so when ever you run npm install it will give error at run time so can you tell me a better way to do that.

[iThink32]

@ashutoshshubam what error are you facing? If it is an ambiguous reference issue then blacklist the conflicting directory , that's what I did.

[ashutoshshubam]

@iThink32 can you share you repo or some link.

[iThink32]

@ashutoshshubam you will easily get references regarding blacklisting , anyway I've just found one now
https://stackoverflow.com/questions/41813211/how-to-make-react-native-packager-ignore-certain-directories

The example folder of this repo contains a file called rn-cli.config.js in which I have blacklisted a particular directory.You can see that for reference.

[hsnMoghadasi]

it's work for me
amazon-archives/awsmobile-cli#172 (comment)

[erkrujjawal786]

Non of the solution fixes my error. I have the same error.

[ashutoshshubam]

@erkrujjawal786, for now, use this:-"react-native-razorpay": "https://github.com/ashutoshshubam/react-native-razorpay",
its working. In package.json file.
once the library is stable then replace it with the latest version.