-
Notifications
You must be signed in to change notification settings - Fork 4
umi3.5 umi4/max didn't worker #12
Comments
Which plug-in are you using? Please provide a minimal reproducible example. |
that's all~ |
The umi template requires no additional configuration, and the react-refresh-webpack-plugin is automatically configured. And I saw the demo you sent me, using @umijs/react-refresh-webpack-plugin instead of @pmmmwh/react-refresh-webpack-plugin has solved the problem? |
no , error still , |
the remoteEntry code looks like that,my umi demo's code is less than demo app2's code |
The demo you gave me started normally when I started it locally. The problem cannot be reproduced. In addition, this problem should occur whether you use the single-react-refresh-plugin or not. It should not be related to this plug-in. |
The error message seems to have nothing to do with the single-react plug-in, and it should be purely an error of the react-refresh plug-in. Can you complete the demo to reproduce the problem so that I can troubleshoot it? |
use umi4 to init a project . configer your project with moduleFederation with umi4. then the problem should be there |
errors like$ReactRunTime$ has already been declared
The text was updated successfully, but these errors were encountered: