fix: symbolicate Module Federation remote stack frames

[MikitasK]

Summary

Closes #1433

Fixes development stack-trace symbolication for Module Federation bundles served by a separate Re.Pack dev server.

Previously, the host tried to find remote source maps in its own compiler assets, resulting in:

Source map for __federation_expose_MiniAppNavigator.chunk.bundle is missing

this change:

• follows remote bundle’s declared sourceMappingURL
• supports both Rspack & Webpack dev servers
• symbolicates frames independently so one invalid frame doesn't discard complete stack
• handles malformed generated webpack:// source URLs
• uses matching source map’s sourcesContent for code frames
• isolates source-map consumers between concurrent requests
• logs first useful symbolicated runtime frame as a terminal fallback
• affects development tooling only & doesn't modify production bundles

Recording

mf_error_symbolication_fix.mp4

Test Plan

1. open apps/tester-federation-v2
2. add an error inside mini app:

throw new Error('MINI APP ERROR');

3. start both dev servers:

pnpm --filter tester-federation-v2 start:hostapp
pnpm --filter tester-federation-v2 start:miniapp

4. run the application:

pnpm --filter tester-federation-v2 ios
pnpm --filter tester-federation-v2 android

5. navigate to the mini app & verify that:

• error overlay points to the original mini-app source file
• correct source code frame is displayed
• pressing stack frame opens correct source file
• terminal logs symbolicated source location
• no source map is missing error is reported for the remote chunk

6. run automated checks:

pnpm --filter @callstack/repack test
pnpm --filter @callstack/repack typecheck
pnpm --filter @callstack/repack build
pnpm --filter @callstack/repack-dev-server test
pnpm --filter @callstack/repack-dev-server typecheck
pnpm --filter @callstack/repack-dev-server build

[vercel]

@MikitasK is attempting to deploy a commit to the Callstack Team on Vercel.

A member of the Team first needs to authorize it.

[changeset-bot]

🦋 Changeset detected

Latest commit: 9f0555a

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 6 packages

Name	Type
@callstack/repack	Patch
@callstack/repack-dev-server	Patch
@callstack/repack-plugin-expo-modules	Patch
@callstack/repack-plugin-nativewind	Patch
@callstack/repack-plugin-reanimated	Patch
@callstack/repack-init	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[bartekkrok]

Well done job !

[dannyhw]

how does the performance compare? seems like we had this sourceMapConsumerCache for performance reasons.

is it not possible now that subsequent requests will have to recalculate? or am I misunderstanding?

[MikitasK]

basically, we shouldn’t lose any work across calls because old cache was already destroyed & cleared after every process() call
just to be safe, I double-checked this & didn’t observe any performance regression. also, I added tests covering same-request reuse, refresh between requests & concurrent requests