-
Notifications
You must be signed in to change notification settings - Fork 27.3k
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
react-loadable-manifest can be missing needed modules in some cases #22741
Milestone
Comments
2 tasks
This comment has been minimized.
This comment has been minimized.
Please don't spam issues. |
kodiakhq bot
pushed a commit
that referenced
this issue
Apr 21, 2021
Co-authored-by: JJ Kasper <jj@jjsweb.site> ## Bug - [x] Related issues linked using `fixes #number` - [x] Integration tests added Closes: #22741
SokratisVidros
pushed a commit
to SokratisVidros/next.js
that referenced
this issue
Apr 21, 2021
Co-authored-by: JJ Kasper <jj@jjsweb.site> ## Bug - [x] Related issues linked using `fixes #number` - [x] Integration tests added Closes: vercel#22741
This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When using
next/dynamic
, the react-loadable-manifest plugin can fail to include modules that should be included.We need to update the react-loadable-manifest plugin to handle these cases as well as attempt to add a test for this as well.
This was initially noticed while using
next/dynamic
on the Vercel blog and is currently the only reproduction. This occurs with both webpack 4 and webpack 5.When these modules aren't included in the react-loadable-manifest it can cause hydration issues since we aren't waiting for all of the needed modules to be loaded before hydrating.
The text was updated successfully, but these errors were encountered: