Reanimated babel error after migrating to Expo Router about expo HOT 8 CLOSED

With some more exploration I was able to find that other instances of using react-native-animated trigger the error, but typically importing react-native-gesture-handler is the earliest so it takes precedent.

I believe this is an issue caused by Expo Router and not by the other libraries/bun since it didn't occur until I migrated to Expo Router from the old webpack setup.

from expo.

+1
Glad to find someone else having this issue; because I fully thought it was on my side of the keyboard. It started for us two days ago and have been trying to figure it out since.

from expo.

and we use Yarn

from expo.

This is how it manifests in our project.

from expo.

Turns out the issue on my end was a babel plugin @legendapp/state/babel.
Once I remove it the app starts loading again.

Might be worth checking the plugins in your babel.config.js file @dawsonbooth

from expo.

Ah, glad you could get it working.

The only plugin I'm using (as well as the minimal reproducible example) is react-native-reanimated/plugin which is required for the react-native-animated setup, so it can't be resolved that way for me unfortunately.

from expo.

@dawsonbooth I have

'expo-router/babel',

and I still get

iOS Bundling failed 48ms node_modules/expo-router/entry.js (1 module)
error: node_modules/expo-router/entry.js: You appear to be using a native ECMAScript module configuration file, which is only supported when running Babel asynchronously.

from expo.

Bun appears to be providing incorrect dependencies.

Removing your lock file and using npm to install the project works fine. When I use your lockfile, the dependency tree looks like this

[email protected] /Users/mark/Github/dawsonbooth/expo-router-babel-reanimated-crash
├─┬ [email protected]
│ └─┬ [email protected]
│   └─┬ @react-native/[email protected]
│     └── @babel/[email protected]
└─┬ [email protected]
  └── @babel/[email protected] invalid: "^7.0.0-0" from node_modules/react-native-reanimated

Expo has reported similar issues to the bun team recently (oven-sh/bun#8406). I'm not sure if this is the same issue or another issue. In the mean time, you can lock the version of @babel/plugin-transform-shorthand-properties or use a different package manager

from expo.