Incorrect nested import ordering

[adam-h]

I just discovered this bug, where two imports that both import the same file can end up with the imported file out-of-order intermittently (due to parallel loading).

For example, if two separate files import base.css, in some cases the second file will process first and actually include it. Whereas the first file will not (due to de-duping) and then the result will be out-of-order and can affect the resulting applied styles (or variable definitions).

I have a full test case in my branch: adam-h@569ea1e

Note how the first import is delayed so that the second will always process first (removing the randomness of occurance due to the filesystem).

[jednano]

Can you create a PR with a breaking test?

[adam-h]

Done :) #169

What is the status on this issue? I am also affected by it.

[MoOx]

The status of an opened issue is: the issue is still open, so not fixed.

No worries, does anybody has a workaround for this issue? Perhaps disabling de-duping?

For anyone looking at this issue, temporary fix is to set skipDuplicates: false.

[simplesmiler]

skipDuplicates: false does not solve the issue for me.

---

EDIT: maybe there could be an option to disable parallel loading?