-
-
Notifications
You must be signed in to change notification settings - Fork 26.9k
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.
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
Update @pmmmwh/react-refresh-webpack-plugin to 0.5.0-rc.3 #11316
Conversation
@hasanayan the workbox fix is now on main, tests fail due to the broken workbox package |
@hasanayan try merging in main - I think we also need to update the compiled yarn lockfile as a dependency was updated 'yarn compile:lockfile' |
@raix yarn.lock files seem to be ignored in this project. I merged main and now everything seem to be fine |
Super @hasanayan thanks! Yeah the yarn.lock files are not checked in but we do generate a yarn.cached.lockfile in the create-react-app package - updated by running 'yarn compile:lockfile' (disclaimer I'm yet to figure out the reason behind it) |
@raix here is the output I am getting from yarn compile:lockfile <ref *1> Error: spawnSync yarn ENOENT |
@hasanayan what version of node are you on? |
@raix 14.17.5 |
@hasanayan can't replicate 14.17.5 works fine for me It's running the |
@raix my yarn version was 1.22.11 but I also tried your now and the result is the same. Anyway, I don't wanna bother you with this anymore. I am on my sister's laptop now and I hope my own machine will not have the same problem. Thanks for the support! 👊 |
@hasanayan no worries - thanks again! :) |
@hasanayan you are welcome. I am a CRA contributor now YAY!!! |
there were some updates on
@pmmmwh/react-refresh-webpack-plugin
for webpack 5 and module federation compability. This PR upgrades the dependency to its last version.Currently react-scripts is using
@pmmmwh/[email protected]
, this seems to cause problems with module federation and those problems were fixed in the last version of the plugin. With this PR we aim to upgrade the dependency version to0.5.0-rc.3
and resolve those issues.#11241 (comment)