(Node >16, RN <0.68) Metro has encountered an error: Cannot read properties of undefined (reading 'transformFie'): . . .

[nabtron]

Error while running react-native app on ios.

react-native version: 0.67.3

Metro has encountered an error: Cannot read properties of undefined (reading 'transformFie'): . . .

Tried changing node version to 17, 16.12, 14, etc. but no use.

Please help / guide. Thanks.

detailed error:

Metro has encountered an error: Cannot read properties of undefined (reading 'transformFile'): node_modules/metro/src/Bundler.js (48:30)

RCTFatal
__28-[RCTCxxBridge handleError:]_block_invoke
_dispatch_call_block_and_release
_dispatch_client_callout
_dispatch_main_queue_callback_4CF
__CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__
__CFRunLoopRun
CFRunLoopRunSpecific
GSEventRunModal
-[UIApplication _run]
UIApplicationMain
main
start_sim
0x0

[cosmosinnovate]

I am running into the same issues as above.

[robhogan]

Could someone who's experiencing this please post:

• Output of yarn list or npm list -a
• Contents of metro.config.js
• Contents of babel.config.js

This does look like we're trying to use Bundler._transformer before it's set, but although this code lives on the edge (relying on ordering of promise branches) - it should be ok, and I haven't been able to reproduce.

[nabtron]

metro.config.js

/**
 * Metro configuration for React Native
 * https://github.com/facebook/react-native
 *
 * @format
 */

module.exports = {
  transformer: {
    getTransformOptions: async () => ({
      transform: {
        experimentalImportSupport: false,
        inlineRequires: true,
      },
    }),
  },
};

babel.config.js

module.exports = {
  presets: ['module:metro-react-native-babel-preset'],
};

npm list -a is huge, with only one possible warning in it:

─┬ react-native-permissions@3.3.1
│ ├── UNMET OPTIONAL DEPENDENCY react-native-windows@>=0.62.0
│ ├── react-native@0.67.4 deduped
│ └── react@17.0.2 deduped

No other error.

[robhogan]

Thanks @nabtron

npm list -a is huge, with only one possible warning in it

I'm actually more interested in the package versions you have - my working theory is that this might be a transform bug in a recent minor dependency update, causing promise branches to execute out of order. That's partly because a cluster of recent reports against an old Metro version suggests the issue is in a recently released dependency rather than Metro itself.

You could post the output to a gist if you like, or filter down to babel-, @babel and metro- dependencies and post the versions here. Equivalently, uploading your package-lock.json would work.

Are you still regularly seeing this issue?

[nabtron]

@rh389

package-lock.json: https://gist.github.com/nabtron/3ab61e930e3ad997deaa54e294c3e154

[kidtzz]

This work for me

export NODE_OPTIONS=--openssl-legacy-provider

and i'm not downgrade my node

my node 17.7.1

i'm just install same node from package.json => dependencies => node on folder project react-native

[nabtron]

@kidtzz so issue is with metro or openssl?

[itta611]

Hi!
I solved this issue with downgrading node version. (In my case, v17.4.0 -> v16.13.0)

nodebrew install-binary 16.13.0
nodebrew use 16.13.0
npx react-native run-ios

[robhogan]

Yes, this is down to incompatibility of older versions of Metro with Node 17+. Contrary to the original issue report here, I haven't seen a reproduction for Node <17. The root cause is Node 17 using OpenSSL 3 (nodejs/node#40455), which drops support for MD4 hashing, which we used until #752.

Three options:

• Update to React Native 0.68 (Metro 0.67) or higher. That includes the Metro fix for Node 17+ compatibility.
• Use Node 16 or older.
• Set NODE_OPTIONS=--openssl-legacy-provider

[ez-tech-global]

This work for me

export NODE_OPTIONS=--openssl-legacy-provider

and i'm not downgrade my node

my node 17.7.1

i'm just install same node from package.json => dependencies => node on folder project react-native

It works for me too! thanks

[ChiuMungZitAlexander]

I solved this by switching to node v16.

[robhogan]

There are multiple possible root causes to this message, which indicates the transformer failed to load.

The cause at the time this issue was opened has been fixed for more than a year, and anyone still seeing this is likely experiencing a different bug for which we'll need details on how to reproduce. There's no way we can help with "+1" type responses. Please do open a new issue, and we can give this a fresh look.

@Martyneris - that's a different message and definitely not the same issue. Feel free to open a new one with a reproduction.

I'm locking this because the original root cause here is fixed, but please don't be discouraged from opening a new issue.