You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently if you are using next/dynamic it will return Loading... everywhere. I think that it should just return null by default that way you aren't forcing everyone to override Loading... (I assume everyone would). Instead if they want to create their own component they can. This would be super easy to do and I would be happy to add a PR for it.
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.
vercel
locked as resolved and limited conversation to collaborators
Jan 31, 2022
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently if you are using
next/dynamic
it will returnLoading...
everywhere. I think that it should just returnnull
by default that way you aren't forcing everyone to overrideLoading...
(I assume everyone would). Instead if they want to create their own component they can. This would be super easy to do and I would be happy to add a PR for it.Here is the line of code in question:
https://github.com/zeit/next.js/blob/canary/lib/dynamic.js#L32
The text was updated successfully, but these errors were encountered: