You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
@babel/runtime/ helpers/interopRequireDefault after upgrade from 0.72.3 to 0.82.1 #1624
changed the title [-]@babel/runtime/ helpers/interopRequireDefault after upgrade from 0.73.3 to 0.82.1[/-][+]@babel/runtime/ helpers/interopRequireDefault after upgrade from 0.72.3 to 0.82.1[/+]on Nov 24, 2025
I’m not sure if you’ve already resolved this, but if using a monorepo is the root cause, you can fix the issue by adding the workspace root node_modules path to watchFolders in Metro.
metro.config.js
constpath=require("path");const{ getDefaultConfig, mergeConfig }=require("@react-native/metro-config");constworkspaceRoot=path.resolve(__dirname,"../../../");constprojectRoot=__dirname;constconfig={watchFolders: [path.resolve(workspaceRoot,"packages"),path.resolve(workspaceRoot,"libs"),// In a pnpm workspace, node_modules is not located at the project root,// so it must be explicitly added.// https://metrobundler.dev/docs/local-developmentpath.resolve(workspaceRoot,"node_modules"),],resolver: {nodeModulesPaths: [path.resolve(projectRoot,"node_modules"),path.resolve(workspaceRoot,"node_modules"),],},};module.exports=mergeConfig(getDefaultConfig(projectRoot),config);
When resolving packages, paths that are not included in watchFolders are not added to Metro’s file system tree, so Metro cannot find those packages.
After applying this configuration, I confirmed that pnpm symlinks work correctly and module resolution issues were resolved.
Activity
[-]@babel/runtime/ helpers/interopRequireDefault after upgrade from 0.73.3 to 0.82.1[/-][+]@babel/runtime/ helpers/interopRequireDefault after upgrade from 0.72.3 to 0.82.1[/+]dexical30 commentedon Dec 15, 2025
Hello, I’m experiencing the same issue as well.
Are you using a monorepo by any chance?
In my case, this happens when using a pnpm-based monorepo.
dexical30 commentedon Dec 20, 2025
I’m not sure if you’ve already resolved this, but if using a monorepo is the root cause, you can fix the issue by adding the workspace root
node_modulespath towatchFoldersin Metro.When resolving packages, paths that are not included in watchFolders are not added to Metro’s file system tree, so Metro cannot find those packages.
After applying this configuration, I confirmed that pnpm symlinks work correctly and module resolution issues were resolved.