-
Notifications
You must be signed in to change notification settings - Fork 60
plugin-css requires a fresh builder instance each time #102
Comments
There may well be bugs with running multiple builds at the same time as the individual plugin instance is designed to work against a single build. We may need some way to key the build instance itself in the internal plugin cache layer here. |
Simpler solution might be to just error out if the plugin is run more than once on the same builder instance. |
The issue shouldn't actually be the instance, but rather having multiple builds running at the same time? Or even with waiting for the build to complete are you getting issues using the same builder instance? |
I just checked - every call to |
I've done some further testing and can confirm this is entirely to do with parallel builds not being supported. I think I have some ideas going forward, but it will require some changes to the builder API so don't want to rush this. |
This tool is pretty outstanding as is. Preventing parallel builds is easy with the simplest of helper methods - the best work to reward ratio may be to just error out on parallel build attempt. My $0.02 :) |
Thanks, unfortunately the detection problem is just as hard though! |
I've included a fix for this in 6be8e64, although there may still be some race conditions remaining. Let me know if it helps though! |
Sure - thanks much! |
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
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?
The text was updated successfully, but these errors were encountered: