I haven't seen anything else, so I think this solution is the way to go. Mojs is not (to my knowledge) promise based at all, instead relies on callback functions. But maybe it could be a interesting feature. I personally never have needed something similar.

In what use case do you need this promise to resolve? Maybe we should always return a promise when the animation is finished?

USE CASE: I am designing a game and using frontend technology for rapid prototyping (similar to Zelda creating a 2D version for testing before implementing a full-fledged 3D version). An entity plays a burst animation once hit and only after that animation is done, the next animation shall be played (or updating the board state or stuff).

I am using animejs as well and it supports waiting by returning a promise, so I can do await someAnimation.finished. This feature could be nice for mojs as well.

So instead of the code above, I can do:

const burst = new mojs.Burst({
 radius: {30: 120},
 count: 10,
});

await burst.play().finished;

Thanks for the use case (and interesting use of the library 🙂).

But yeah, then I can understand it's a bit easier to to sequencial code if you can use it that way. We'll look into it.

I confirm I am using a Promise too with the onComplete event of mojs if I need to wait for the animation to complete because it does not support Promise for now 😉