Support emitting multiple arguments about mitt HOT 8 CLOSED

You can easily do both.

• .emit(type, ...rest)
• .on(type, (type, ...rest) => {})
• .on('*', (type, ...rest) => {})

from mitt.

You might be surprised how convenient * is! Some uses I've had for it over the years:

• logging (example: on('*', console.log))
• refiring modified or aggregate events (example: on('log:debounced'))
• collating events between two emitters (example: inside/outside a worker)
• implementing rudimentary event bubbling (listen to child's *, refire if e.bubble)
• even implementing case-insensitive event handling 💃

from mitt.

hmm.. yep, forgot about that

from mitt.

So finally, I just tried to see what I'll get if I merge everything ( #8, #11, #12 + this one #13 ) and it is 210 bytes which looks good number :P :)

from mitt.

Nice! Though I might have an interesting thought that changes your mind about the multiple arguments thing from @bevacqua:

from mitt.

FWIW, I would use support for multiple arguments before using *.

from mitt.

I'm absolutely agree. Working (emitting) only one argument is cool and very clean. So yea, I can agree to remove that extra second argument from #19, but we should mention that in the docs that emit can only emit one argument. :)

from mitt.

Yea. Closing per f4c60f4

from mitt.