eventemitter3 | EventEmitter3 - Because there's also a number 2 And we're faster | Runtime Evironment library

Recently I was reading about variadic templates and based on an example I've seen online I was trying to implement a basic event-system. So far it seems to work fine but I was trying to go a step further and allow N number of arguments to be passed to an event handler function / callback, unfortunately the build error I'm getting is the following and I'm not sure what I'm doing wrong. I looked into similar source codes but still cant figure out what's the issue.

I'm trying to implement an app that creates a ".message" for each lyric every time the beat ticks. However, it seems like I've hit a wall while trying to come up with an algorithm.

My code:

I have a custom module definition file for a dependency written in CoffeeScript in my typescript project.

It looks like the following and works great:

src/@types/dependency-name.d.ts

What I want to do:

1. Send a 'request' event to a websocket server.
2. Receive an immediate response event bundled with some additional data.
3. Keep receiving responses over time.

My question is:

• Is there a cleaner way of doing what I'm doing below? Without using setTimeout.

First, look at this simplified working example:

I am trying to implement a interceptor with axios so everytime I receive a response from a request, it checks if it has the field "msg" and if it has, it should show the message to the user.

To do this, I implemented a interceptor in axios, this interceptor should fire an event everytime it receives a response, then the App.js would be listening to this events to show the appropriate message.

My problem is that it seems the event is being fired twice, at first I though it was a problem with PubSub, which is the library that I was using, so I decided to try another framework (eventemitter3) and the exact same thing happened, so I'm totally lost, other people who had similar issues found out that their requests werte actually being fired twice by different components, I'm almost sure that this isn't the problem here, look at the logs when I make a request:

I am receiving Warning: componentWillReceiveProps has been renamed but I am not calling that method anywhere I can see.

The error stack is here - and it starts when a setState is called within componentDidMount which I would have thought is an okay thing to do:

Is it possible to redeclare an object with another interface, to provide overloading of the existing methods?

My specific example is using the EventEmitter (concretely I'm using the eventemitter3 package, but it follows all the NodeJS.EventEmitter specs).

So I have this file declaring the singleton instance:

I am trying to run a typescript express.js in a docker container. After running the docker I get the following error:

I need to update a useCallback hook on a certain event that is emitted by eventEmitter3. Right now I update a local state with the current time to trigger the useCallback. That works but looks crazy complicated. Is there a better solution?