-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
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
Possibly helpful correlation in docs for class names + multiple chunk builds #12435
Comments
@atrauzzi Oh yes! I think that we should be documenting the fact that bundlers might duplicate modules when code splitting 👍. Thanks for raising the issue. |
Do you want to update the docs? |
I can try! What do I have to do? 😄 |
I believe we can add this other source of potential issue in the documentation section you linked: https://material-ui.com/getting-started/faq/#how-to-fix-a-class-names-conflict-in-production- |
On it! Stay tuned. |
Hey everyone (awesome) at MUI!
I just finished successfully troubleshooting a JSS styling issue largely in thanks to a lot of the existing discussion and documentation provided in this repo.
There was one facet of my issue that wasn't covered however that I feel like the docs could be expanded which is to include a mention about the
runtimeChunk
option in WebPack.Briefly -- my scenario is that I'm producing a collection of components-per-chunk scripts that all rely on a common chunk. All normal functionality in WebPack, but I realized that I was running the bootstrap stub multiple times. Which of course for MUI meant I was getting multiple instances of the JSS css name generator (oops!).
What I think would be great is to link to this page in the docs somewhere near the FAQ item I linked above: https://webpack.js.org/configuration/optimization/#optimization-runtimechunk
The text was updated successfully, but these errors were encountered: