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
{{ message }}
This repository was archived by the owner on Oct 9, 2020. It is now read-only.
Hi Guy. I'm seeing what I think is a bug. Essentially, the plugin-css requires a fresh builder instance each time. If you create bundles with css dependencies on the same builder instance, some lines seem to get crossed, and css ends up in incorrect places.
Specifically, consider
for (let name of namesToOptimize) {
let builder = new Builder('../' + baseDirectory);
builder.config(configToUse);
Hi Guy. I'm seeing what I think is a bug. Essentially, the
plugin-cssrequires a fresh builder instance each time. If you create bundles with css dependencies on the same builder instance, some lines seem to get crossed, and css ends up in incorrect places.Specifically, consider
with calls to
below, inside the loop body. If I move
above the for loop, the problems described above surface.
Is this expected behavior? Do you need me to repro this somewhere in GitHub?