mitt VS EVT

Mitt is a small (200 bytes) library that provides the same functionality. It doesn't have many updates, because it's simply perfect and there are not many things to improve there. It gets the job done. Don't be frightened, if in 2 years npm will say it's 2 years old. This library is just perfect with no bloatware. In the worst case, just copy-paste its code to your app.

The implementation can vary widely depending on the requirements. For our application, we will take a small library that will do almost everything for us:

You can use an event bus for this, looks like they removed this functionally from vue 3 so you'll need a 3rd party package like mitt

then we need to install an external library implementing the event emitter interface, in this case mitt

date-fns and mitt (event emitter) are also frequent helpers, but I'm considering dayjs and nanoevents for these cases.

Not sure I understood the post right, bit you may want to check Mitt. It's popular event emitter package that quite nicely deals with this very issue.

As suggested in official docs you could use mitt library to dispatch events across components.

You can use it mitt library. https://github.com/developit/mitt

For situations like this, I use simple event emitter / pubsub library called mitt. It's small and lightweight, however there are many similar libraries that would work.

In this article I want to show you how I have implemented this pattern in my Nuxt 3 applications using Mitt which already provides full TypeScript support. To fully understand what's happening under the hood I recommend to have a quick read of Mitt documentation before continue reading.

The next step will be to instantiate the event emitter that will be used in the API, when we use the dependency evt we can create a totally typesafe client and the only thing we need is define a type and pass it as a generic in the .create() method, like this: