@module-federation/bridge-react - react-router optionality

[crutch12]

Clear and concise description of the problem

I don't use react-router

Even if react-router-dom and react-router are marked as optional, these peerDeps are required for base @module-federation/bridge-react usage.

createRemoteAppComponent uses createLazyRemoteComponent, which uses withRouterData, which imports react-router-dom, so react-router-dom sneaks into js bundle

Also current implementation rewrites exportName and basename props, thus I'm not able to pass them (ironic, but I already provide my own basename prop)

Suggested solution

Provide analog for createLazyRemoteComponent and createRemoteAppComponent which wouldn't require react-router import

Example:

import { createRemoteAppComponent } from '@module-federation/bridge-react/base' // "react-router free", just render()

Alternative

No response

Additional context

No response

Validations

• Read the Contributing Guidelines.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

[danpeen]

@crutch12 Thanks for raising this! Let me take some time to think about the best way to address it.

[NGorteTC]

Making the router optional would be nice 👍
We also have some remote applications, which come with their own react version but do not require the router.

[danpeen]

@crutch12 @NGorteTC Could you please try this version of @module-federation/bridge-react@0.0.0-feat-bridge-react-router-free-20251120090200,

Set config: bridge.enableBridgeRouter to false in the consumer application to disable the bridge router capability, and observe whether the packaged chunk contains react-router:

 bridge: {
    enableBridgeRouter: false,
  },