The complexity of this problem is astonishing.

So, I had to step back from the v1.0.5.
The v1.0.5 also known as "The completist", was pushed too fast.

Yes, with the help of @leonderijke, I noticed that the mixin after-each() were using a bad syntax, not bad, but it has a selector specified, and we needed none.

However, fixing it, I noticed that the mixin was not optimal, nor working as expected.
So, I had to remove it, until I got it to work as I want.

So, for this release, the changelog will be very light.

v1.0.6

• each-after() mixin removed, re-opening #37