Turns out the latest version of ordered-read-streams, 2.0.0, does not always order the files as they were given.
Looks like the issue is inside the new used streamx lib. It seems the given order is modified internally by the end of the file read, so larger files are merged at the end rather than the desired position.
For example the large emoji.css was always set to the end of the order although the order of that file was given much earlier in the stream array.
Reverting back to to v 1.0.1 fixes that (as it does not use streamx, but readable-stream instead of streamx)
Description
Turns out the latest version of ordered-read-streams, 2.0.0, does not always order the files as they were given. Looks like the issue is inside the new used streamx lib. It seems the given order is modified internally by the end of the file read, so larger files are merged at the end rather than the desired position. For example the large emoji.css was always set to the end of the order although the order of that file was given much earlier in the stream array. Reverting back to to v 1.0.1 fixes that (as it does not use streamx, but readable-stream instead of streamx)