8000 Console warning when use React 18 and bridge-react · Issue #3663 · module-federation/core · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Console warning when use React 18 and bridge-react #3663

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to 8000 bottom
Open
5 tasks done
eli-wang-avepoint opened this issue Apr 2, 2025 · 4 comments
Open
5 tasks done

Console warning when use React 18 and bridge-react #3663

eli-wang-avepoint opened this issue Apr 2, 2025 · 4 comments

Comments

@eli-wang-avepoint
Copy link

Describe the bug

Image

Host app: React 18.3 webpack 5.88.2
Remote app: React 18.2 vite 6.2.3

"@module-federation/bridge-react": "^0.11.2",
"@module-federation/enhanced": "^0.11.2",
"@module-federation/vite": "^1.2.6"

when I upgrade to 0.11.2, console show this waning. What should I do?

Reproduction

Host & Remote app use react 18 ,

Used Package Manager

npm

System Info

System:
    OS: Windows 11 10.0.22621
    CPU: (8) x64 AMD EPYC 9354 32-Core Processor
    Memory: 1.31 GB / 16.00 GB
  Binaries:
    Node: 20.17.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.22 - C:\Program Files\nodejs\yarn.CMD
    npm: 10.8.2 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 134.0.6998.178
    Edge: Chromium (127.0.2651.74)
    Internet Explorer: 11.0.22621.1

Validations
@einarq
Copy link
einarq commented Apr 2, 2025

I get the same issue in an app using React Router 7

@ScriptedAlchemy
Copy link
Member

might be tricky to solve as importing react-dom/client in a app where that doesnt exist will break the build. Will have to look at the options

@danpeen
Copy link
Contributor
danpeen commented Apr 10, 2025

I have noticed this issue, let me fix it.

@danpeen
Copy link
Contributor
danpeen commented Apr 29, 2025

@eli-wang-avepoint Can you upgrade to the latest @module-federation/bridge-react version 0.13.1 to test if this issue has been fixed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@einarq @danpeen @ScriptedAlchemy @eli-wang-avepoint
0