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
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!).
@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.
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: