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
In our, and Im sure others, webpack setup JS and CSS bundles are generated with the same chunkid. This means that when this plugin looks up the chunk using getChunkScriptFilename it returns the JS one, rather than the CSS one that caused the issue.
At a quick glance, theres no easy fix, however I will continue to investigate
The text was updated successfully, but these errors were encountered:
Raising this with the aim of coming back to it.
In our, and Im sure others, webpack setup JS and CSS bundles are generated with the same chunkid. This means that when this plugin looks up the chunk using
getChunkScriptFilename
it returns the JS one, rather than the CSS one that caused the issue.At a quick glance, theres no easy fix, however I will continue to investigate
The text was updated successfully, but these errors were encountered: