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

[claudioviola]

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

[krystofwoldrich]

Hi @claudioviola,
thank you for the message,
I was able to reproduce it in our sample app, we will investigate it.

[Fwang36]

Hey Krystof,

Support received a request in Zendesk from a user with the same issue. Do you have an update for this problem?

Link to Zendesk ticket

[krystofwoldrich]

Hi @Fwang36,
no updates yet, I'll keep you posted here.

[amir-dropit]

@krystofwoldrich is it resolved in v5.22.0?

[krystofwoldrich]

@amir-dropit No, 5.22.0 doesn't fix this particular issue.

[amir-dropit]

How is this not fixed yet?

[YishaiGr]

@krystofwoldrich can you please update on the manner? our source maps were not uploaded for 3 weeks because of this bug

[krystofwoldrich]

Hi, I'm sorry to hear that, I've opened a PR fixing this today.

• fix(metro-config): incorrect sourceMappingURL file path when when using beforeAssetSerializationPlugins expo/expo#29054

I'll also post here a workaround which you can use until the fix is released.

[YishaiGr]

Thanks a lot! 🙏

[krystofwoldrich]

Until the fix is released, you can apply the changes from the fix PR using https://www.npmjs.com/package/patch-package

[ricklove]

This breaks dynamic modules with React.lazy

[krystofwoldrich]

This was fixed in expo/expo#30980