getDefaultConfig from expo/metro-config compromise the sourceMappingURL and it has a wrong hash when exported for web platform

claudioviola commented 8 months ago

OS:

[ ] Windows
[ X] MacOS
[ ] Linux

Platform:

[ ] iOS
[ ] Android

"@sentry/react-native": "^5.17.0",
"expo": "^50.0.3",
"react-native": "0.73.2",
"react-native-web": "~0.19.6",
"@expo/metro-runtime": "~3.1.2",
"react": "18.2.0",
"react-dom": "18.2.0",

Are you using Expo?

[X ] Yes
[ ] No

This is the configuration of my metro.config.js placed in the root folder project

// This replaces `const { getDefaultConfig } = require('expo/metro-config');`
const { getSentryExpoConfig } = require('@sentry/react-native/metro');

// This replaces `const config = getDefaultConfig(__dirname);`
const config = getSentryExpoConfig(__dirname);

module.exports = config;

I have the following issue:

Steps to reproduce:

Build the web project by running this command npx expo export -p web --dump-sourcemap
check the dist folder

2 files are created AppEntry-9c58c4463ca3cfc79b6525f9cc37e942.js AppEntry-9c58c4463ca3cfc79b6525f9cc37e942.js.map

Actual result: Opening the first file for checking if the sourceMappingURL is correct Actually the sourceMappingURL is wrong and it contains a different hash for the Javascript bundled file //# sourceMappingURL=/_expo/static/js/web/AppEntry-c20e66115809b9d51b0088b809c85f32.js.map

Expected result:

Opening the first file for checking if the sourceMappingURL is correct the sourceMappingURL should contains the correct hash and it should points to the correct file //# sourceMappingURL=/_expo/static/js/web/AppEntry-9c58c4463ca3cfc79b6525f9cc37e942.js.map

if using in the metro.config.js const { getDefaultConfig } = require('expo/metro-config'); the issue disappears and the sourceMappingURL contains the correct file