metro: HELP error index.js: The "id" argument must be of type string. Received undefined.

@walidhousni30 It looks like flipper-server and flipper-pkg-lib are the dependencies bringing in an older version of Metro. Is this a dependency you can update or eliminate?

Do also try:

• Removing any explicit metro dependencies or devDependencies in your project’s package.json (per @bartolkaruza’s fix).
• As a fallback, using Yarn "resolutions" to force the current version of Metro: 0.76.5.

I have just migrated to 72.4 and started getting the same error. Downgrading @react-native/metro-config to 0.72.9 helped me.

With @react-native/metro-config 0.72.11 I get the following error when building the project:

TypeError: The "id" argument must be of type string. Received undefined error index.js: The "id" argument must be of type string. Received undefined

I had the same issue just now, the solution was removing "metro-config" from "dependencies": {}. (not dev-dependencies)

and there’s literally no answer for that tho

@huntie MAAAAN ITT WOOOORKS THANK YOU SOOO MUCH @bartolkaruza your method works as well i cant thank you enough guys

I commented too soon, glad it’s working for you!

@bartolkaruza i have it only on my dev dependency like so

even if it’s in your dev dependencies, it may cause this issue. Try removing it entirely from package.json, then yarn install to clear it from node_modules

@walidhousni30 Great — worth digging up why metro@npm:0.70.4 is there (old version), by trying yarn why metro etc. Really, there should only be one version of Metro (metro@npm:0.76.5) in your project.

From the line numbers reported in the stack trace, it looks like while you’re on metro@0.76.5, you have metro-transform-worker 0.71.1 or older installed.

Please can you run the below and share the result here?

yarn why metro-transform-worker

I also note that you are depending on an old version of React Native CLI — React Native 0.72 requires (and depends on) @react-native-community/cli@11.3.2.

npmPackages:
"@react-native-community/cli":
installed: 10.0.0
wanted: 10.0.0

⬆️ Sometimes, this can be caused by installed libraries which (problematically) depend on react-native directly. It could also be from forced dependency versions (e.g. Yarn resolutions — please revert these).

To be sure your dependencies are as specified, try also:

rm -rf node_modules
yarn

Effectively a duplicate of facebook/react-native#34315