jest-haste-map: Haste module naming collision: -> namefunction <- #3295

esuarezz · 2020-01-28T23:03:15Z

To Reproduce

amplify add function
function is created locally correctly
amplify push and pushed correctly
when I run expo I get:

INFO
22:55
Starting Metro Bundler on port 19001.
ERROR
22:55
jest-haste-map: Haste module naming collision: funcionlambdaparadietas
  The following files share their name; please adjust your hasteImpl:
    * <rootDir>/amplify/#current-cloud-backend/function/funcionlambdaparadietas/src/package.json
    * <rootDir>/amplify/backend/function/funcionlambdaparadietas/src/package.json

ERROR
22:55
Failed to construct transformer:  { Error: Duplicated files or mocks. Please check the console for more info
    at setModule (/Users/elio/WebstormProjects/Hapsto-app/node_modules/jest-haste-map/build/index.js:620:17)
    at workerReply (/Users/elio/WebstormProjects/Hapsto-app/node_modules/jest-haste-map/build/index.js:691:9)
    at process._tickCallback (internal/process/next_tick.js:68:7)
  mockPath1:
   'amplify/#current-cloud-backend/function/funcionlambdaparadietas/src/package.json',
  mockPath2:
   'amplify/backend/function/funcionlambdaparadietas/src/package.json' }
ERROR
22:55
(node:61503) UnhandledPromiseRejectionWarning: Error: Duplicated files or mocks. Please check the console for more info
    at setModule (/Users/elio/WebstormProjects/Hapsto-app/node_modules/jest-haste-map/build/index.js:620:17)
    at workerReply (/Users/elio/WebstormProjects/Hapsto-app/node_modules/jest-haste-map/build/index.js:691:9)
    at process._tickCallback (internal/process/next_tick.js:68:7)
(node:61503) 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: 1)
(node:61503) [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.
INFO
22:55
Tunnel ready.

The text was updated successfully, but these errors were encountered:

dantasfiles · 2020-01-29T02:43:04Z

Related: amazon-archives/awsmobile-cli#172 (comment)

yuth · 2020-01-30T18:43:44Z

Amplify CLI puts all the backend resources in a <project-root>/amplify/ folder. This folder does not contain any files that will be used in the frontend code and should be ignored when building/testing frontend code.

radhikathakkar · 2020-04-20T06:32:14Z

Amplify CLI puts all the backend resources in a <project-root>/amplify/ folder. This folder does not contain any files that will be used in the frontend code and should be ignored when building/testing frontend code.

" so what is the solution for this?? "

miekassu · 2020-04-21T14:55:15Z

@radhikathakkar this worked for me.
create rn-cli-config.js to root folder of ur project.

const blacklist = require('metro').createBlacklist;

module.exports = {
  resolver: {
    blacklistRE: blacklist([/#current-cloud-backend\/.*/]),
  },
};

found from: amazon-archives/awsmobile-cli#172

bilal-korir · 2020-04-26T05:31:38Z

In my case, I'm using ReactNative CLI. Updating the metro.config.js file with the following has worked for me:

module.exports = {
  resolver: {
    blacklistRE: /#current-cloud-backend\/.*/,
  },
  transformer: {
    getTransformOptions: async () => ({
      transform: {
        experimentalImportSupport: false,
        inlineRequires: false,
      },
    }),
  },
};

I'm not using Expo, but seems like if you are using Expo you should update/create rn-cli.config.js at the root of your project, instead.

lissau · 2020-04-27T07:02:54Z

For React Native 0.6x configure the blacklist in metro.config.js instead of rn-cli.config.js, as per this answer

const blacklist = require('metro-config/src/defaults/blacklist');
module.exports = {
  resolver: {
    blacklistRE: blacklist([/#current-cloud-backend\/.*/]),
  },
  transformer: {
    getTransformOptions: async () => ({
      transform: {
        experimentalImportSupport: false,
        inlineRequires: false,
      },
    }),
  },
};

PatidarParth · 2020-07-19T02:50:16Z

@miekassu I have tried the expo solution but now get this error when I try to run the app. Any idea?

Invariant Violation: "main" has not been registered. This can happen if:
* Metro (the local dev server) is run from the wrong folder. Check if Metro is running, stop it and restart it in the current project.
* A module failed to load due to an error and `AppRegistry.registerComponent` wasn't called.

runApplication
    AppRegistry.js:189:6
callFunctionReturnFlushedQueue
    [native code]:0

miekassu · 2020-07-19T08:20:33Z

@PatidarParth after Expo 38 SDK update I had same error.
I needed to update rn-cli.config.js as following:

const blacklist = require('metro-config/src/defaults/blacklist')
module.exports = {
  resolver: {
    blacklistRE: blacklist([/#current-cloud-backend\/.*/]),
  },
};

PatidarParth · 2020-07-19T15:26:31Z

@miekassu Do you call the rn-cli.config.js anywhere? For example, do I need to include it in the projectOpts within the app.json like below?

    "packagerOpts": {
      "config": "./rn-cli.config.js"
      },

miekassu · 2020-07-20T01:15:47Z

@PatidarParth file is just included in root. Metro picks it up automatically. Good luck!

JosephVasse · 2021-04-29T09:55:12Z

Hello, i tried to add the blacklist as mentionned below,

For React Native 0.6x configure the blacklist in metro.config.js instead of rn-cli.config.js, as per this answer

const blacklist = require('metro-config/src/defaults/blacklist');
module.exports = {
  resolver: {
    blacklistRE: blacklist([/#current-cloud-backend\/.*/]),
  },
  transformer: {
    getTransformOptions: async () => ({
      transform: {
        experimentalImportSupport: false,
        inlineRequires: false,
      },
    }),
  },
};

but it seems that i do not have "blacklist.js" file in my metro-config/src/defaults/ :

`error Cannot find module 'metro-config/src/defaults/blacklist'
Require stack:

/Users/josephvasse/Desktop/Villeo/metro.config.js
/Users/josephvasse/Desktop/Villeo/node_modules/cosmiconfig/node_modules/import-fresh/index.js
/Users/josephvasse/Desktop/Villeo/node_modules/cosmiconfig/dist/loaders.js
/Users/josephvasse/Desktop/Villeo/node_modules/cosmiconfig/dist/createExplorer.js
/Users/josephvasse/Desktop/Villeo/node_modules/cosmiconfig/dist/index.js
/Users/josephvasse/Desktop/Villeo/node_modules/@react-native-community/cli/build/tools/config/readConfigFromDisk.js
/Users/josephvasse/Desktop/Villeo/node_modules/@react-native-community/cli/build/tools/config/index.js
/Users/josephvasse/Desktop/Villeo/node_modules/@react-native-community/cli/build/commands/install/install.js
/Users/josephvasse/Desktop/Villeo/node_modules/@react-native-community/cli/build/commands/index.js
/Users/josephvasse/Desktop/Villeo/node_modules/@react-native-community/cli/build/index.js
/Users/josephvasse/Desktop/Villeo/node_modules/react-native/cli.js.
Error: Cannot find module 'metro-config/src/defaults/blacklist'
Require stack:
/Users/josephvasse/Desktop/Villeo/metro.config.js
/Users/josephvasse/Desktop/Villeo/node_modules/cosmiconfig/node_modules/import-fresh/index.js
/Users/josephvasse/Desktop/Villeo/node_modules/cosmiconfig/dist/loaders.js
/Users/josephvasse/Desktop/Villeo/node_modules/cosmiconfig/dist/createExplorer.js
/Users/josephvasse/Desktop/Villeo/node_modules/cosmiconfig/dist/index.js
/Users/josephvasse/Desktop/Villeo/node_modules/@react-native-community/cli/build/tools/config/readConfigFromDisk.js
/Users/josephvasse/Desktop/Villeo/node_modules/@react-native-community/cli/build/tools/config/index.js
/Users/josephvasse/Desktop/Villeo/node_modules/@react-native-community/cli/build/commands/install/install.js
/Users/josephvasse/Desktop/Villeo/node_modules/@react-native-community/cli/build/commands/index.js
/Users/josephvasse/Desktop/Villeo/node_modules/@react-native-community/cli/build/index.js
/Users/josephvasse/Desktop/Villeo/node_modules/react-native/cli.js
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:880:15)
at Function.Module._load (internal/modules/cjs/loader.js:725:27)
at Module.require (internal/modules/cjs/loader.js:952:19)
at require (internal/modules/cjs/helpers.js:88:18)
at Object. (/Users/josephvasse/Desktop/Villeo/metro.config.js:8:20)
at Module._compile (internal/modules/cjs/loader.js:1063:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)
at Module.load (internal/modules/cjs/loader.js:928:32)
at Function.Module._load (internal/modules/cjs/loader.js:769:14)
at Module.require (internal/modules/cjs/loader.js:952:19)
info Run CLI with --verbose flag for more details.
Process terminated. Press to close the window`

I checked as i found on the the net that is could be somewhere else, but it seems that there is no "blacklist.js" file in my project at all ...

Can someone help me ?

flogy · 2021-05-06T16:01:39Z

@JosephVasse in newer versions of metro-config the function is now called exclusionList. So the resulting code would now look like this:

const exclusionList = require('metro-config/src/defaults/exclusionList');
module.exports = {
  resolver: {
    blacklistRE: exclusionList([/#current-cloud-backend\/.*/]),
  },
  transformer: {
    getTransformOptions: async () => ({
      transform: {
        experimentalImportSupport: false,
        inlineRequires: false,
      },
    }),
  },
};

I also had to manually install metro-config as a dev dependency: npm i -D metro-config

JosephVasse · 2021-05-07T12:28:13Z

Yes, i finally figured it out.
I wasn't able to find this issue back to add the answer

Thank you for replying though

miekassu · 2021-05-27T01:45:18Z

After updating to Expo SDK41 this issue came back.
I needed to change previous rn-cli.config.js to metro.config.js (even though Im not using TS) and install @expo/metro-config as devDependency.

github-actions · 2021-07-26T01:48:14Z

This issue has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs.

Looking for a help forum? We recommend joining the Amplify Community Discord server *-help channels for those types of questions.

ashika01 transferred this issue from aws-amplify/amplify-js Jan 29, 2020

SwaySway added functions Issues tied to the functions category pending-triage Issue is pending triage labels Jan 30, 2020

yuth added platform Issues tied to the general CLI platform question General question and removed functions Issues tied to the functions category pending-triage Issue is pending triage labels Jan 30, 2020

esuarezz closed this as completed Feb 5, 2020

waltermvp mentioned this issue Jun 21, 2021

How to ignore files (blacklist or exclusionlist)? infinitered/ignite#1707

Closed

github-actions bot locked as resolved and limited conversation to collaborators Jul 26, 2021

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

jest-haste-map: Haste module naming collision: -> namefunction <- #3295

jest-haste-map: Haste module naming collision: -> namefunction <- #3295

esuarezz commented Jan 28, 2020

dantasfiles commented Jan 29, 2020 •

edited

Loading

yuth commented Jan 30, 2020

radhikathakkar commented Apr 20, 2020

miekassu commented Apr 21, 2020

bilal-korir commented Apr 26, 2020 •

edited

Loading

lissau commented Apr 27, 2020 •

edited

Loading

PatidarParth commented Jul 19, 2020 •

edited

Loading

miekassu commented Jul 19, 2020

PatidarParth commented Jul 19, 2020

miekassu commented Jul 20, 2020

JosephVasse commented Apr 29, 2021

flogy commented May 6, 2021 •

edited

Loading

JosephVasse commented May 7, 2021

miekassu commented May 27, 2021

github-actions bot commented Jul 26, 2021

jest-haste-map: Haste module naming collision: -> namefunction <- #3295

jest-haste-map: Haste module naming collision: -> namefunction <- #3295

Comments

esuarezz commented Jan 28, 2020

dantasfiles commented Jan 29, 2020 • edited Loading

yuth commented Jan 30, 2020

radhikathakkar commented Apr 20, 2020

miekassu commented Apr 21, 2020

bilal-korir commented Apr 26, 2020 • edited Loading

lissau commented Apr 27, 2020 • edited Loading

PatidarParth commented Jul 19, 2020 • edited Loading

miekassu commented Jul 19, 2020

PatidarParth commented Jul 19, 2020

miekassu commented Jul 20, 2020

JosephVasse commented Apr 29, 2021

flogy commented May 6, 2021 • edited Loading

JosephVasse commented May 7, 2021

miekassu commented May 27, 2021

github-actions bot commented Jul 26, 2021

dantasfiles commented Jan 29, 2020 •

edited

Loading

bilal-korir commented Apr 26, 2020 •

edited

Loading

lissau commented Apr 27, 2020 •

edited

Loading

PatidarParth commented Jul 19, 2020 •

edited

Loading

flogy commented May 6, 2021 •

edited

Loading