Out-of-order statements… are out-of-order. about rollup HOT 3 CLOSED

Whoops. My understanding of [].sort was way off the mark, thanks for the explanation. The intent was just to make sure that...

var a = 1;
export default a;
a = 2;

...would maintain the same order, since (due to the fact that export default a isn't a live binding like export {a}) it effectively needs to be rewritten as this:

var a = 1;
var _a = a;
a = 2;

It's a bit of a nuisance edge case (and rare, as far as I can see) but specs are specs. Ordinarily statements preserve the correct order naturally, but export default trips things up.

I apologize if this is a distraction.

Far from it - being able to catch these things at this stage of the library's development is absolutely invaluable. I apologize for breaking your builds! Am working on a solution for this issue.

from rollup.

Okay, I've come up with what seems like a more appropriate solution - we have some special logic for dealing with cases like the above. Rather than attempting to reorder statements at a bundle level, the expansion of export default a is modified in place (if necessary) such that the export declaration appears before any later statements from the same module. The d3-color tests now pass, so I've released this as 0.7.4 - feel free to reopen this issue if it turns out the bug isn't quite squashed.

from rollup.

Thanks. Looks good!

from rollup.