How to fix React Native error "jest-haste-map: Haste module naming collision"?

Question

When I installed react-native-popup-menu, I faced such error.

This is error code

Looking for JS files in
E:\react-native\.............\

Loading dependency graph...(node:9460) UnhandledPromiseRejectionWarning: Error: jest-haste-map: Haste module naming collision: Duplicate module name: react-native Paths: E:\react-native\.............\node_modules\react-native-twitter-signin\node_modules\react-native\package.json collides with E:\react-native\.............\node_modules\react-native\package.json

This error is caused by hasteImpl returning the same name for different files. at setModule (E:\react-native\.............\node_modules\jest-haste-map\build\index.js:551:17) at workerReply (E:\react-native\.............\node_modules\jest-haste-map\build\index.js:613:9) at process._tickCallback (internal/process/next_tick.js:68:7) (node:9460) 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:9460) [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:9460) UnhandledPromiseRejectionWarning: Error: jest-haste-map: Haste module naming collision: Duplicate module name: react-native Paths: E:\react-native\.............\node_modules\react-native-twitter-signin\node_modules\react-native\package.json collides with E:\react-native\.............\heybuddy\node_modules\react-native\package.json

This error is caused by hasteImpl returning the same name for different files. at setModule (E:\react-native\.............\node_modules\jest-haste-map\build\index.js:551:17) at workerReply (E:\react-native\.............\node_modules\jest-haste-map\build\index.js:613:9) at process._tickCallback (internal/process/next_tick.js:68:7) (node:9460) 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)

I tried to find the way to solve this error, but I can't find any solution.

yudhiesh · Accepted Answer · 2020-12-23 15:16:51Z

3

I solved it by creating a metro.config.js file in the root of the folder with this:

module.exports = {
  resolver: {
    blacklistRE: /#current-cloud-backend\/.*/,
  },
};

answered Dec 23, 2020 at 15:16

yudhiesh

6,8774 gold badges25 silver badges56 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Mahantesh. N. Hadimani. Over a year ago

didn't work to me

Biranchi · Accepted Answer · 2019-05-29 01:31:34Z

1

I solved it by adding a new file named "rn-cli.config.js" in the project root folder, with the following contents.

const blacklist = require('metro-config/src/defaults/blacklist');
module.exports = {
    resolver: {
        blacklistRE: blacklist([
            /node_modules\/.*\/node_modules\/react-native\/.*/,
        ])
    },
};

answered May 29, 2019 at 1:31

Biranchi

16.4k23 gold badges128 silver badges164 bronze badges

1 Comment

Mahantesh. N. Hadimani. Over a year ago

didn't work to me

Luan Caius · Accepted Answer · 2020-10-15 17:21:30Z

1

I had this problem and I created a backup of the source files and deleted everything, the whole folder. Deleting node_modules wasn't enough. After getting the files back and using npm install for the packages, it worked.

edited Oct 15, 2020 at 17:21

answered Feb 10, 2019 at 0:46

Luan Caius

339 bronze badges

2 Comments

Narendra Singh Over a year ago

What 'everything' you deleted?

Luan Caius Over a year ago

The whole folder. That's why I did a backup of the source files.

Jamal Basha · Accepted Answer · 2021-12-27 17:39:49Z

0

Just update the below in metro.config.js file in the root of the folder with this:

module.exports = {
  resolver: {
    blacklistRE: /#current-cloud-backend\/.*/,
  },
};

answered Dec 27, 2021 at 17:39

Jamal Basha

5085 silver badges11 bronze badges

Collectives™ on Stack Overflow

How to fix React Native error "jest-haste-map: Haste module naming collision"?

4 Answers 4

1 Comment

1 Comment

2 Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

4 Answers 4

1 Comment

1 Comment

2 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related