Scott Spuler
Scott Spuler
BTW, I'm still using "@expo/metro-config": "^0.7.1" for everything right now for both web and mobile, and haven't encountered any issues with it so far, so I'm able to keep working.
@appsgenie the metro-config I was referring to is one of the devDependencies in package.json, and the jsEngine is hermes (this is declared in app.json, though I believe it's now not...
I am able to get it to work perfectly with 49 on a dev client. With 50 in a dev client, it (sometimes) doesn't trigger inline breakpoints, but respects things...
I did a little more digging, and by adding the following as a devDependency: "@expo/metro-config": "^0.7.1" which reverts metro-config to an older version, the problems go away.
Still an issue, and I'm having to use the downgraded metro config in order to keep working.
I've got the same issue as @balgamat, and it's preventing me from using React Hook Form and Metro together on the web. This consequently prevents me from using Expo Router,...
I have them working together fine on iOS & Android, but not on web.
I was able to get them working together on web by switching to webpack bundler instead of metro. There seems to be a fundamental incompatibility between metro for web and...
This doesn't work for me, whether I'm using remote debugging or not.