We're using this on our backend, but ran into a simple case where it would be very handy to use on the frontend. I can't find any mention of why this wouldn't be advisable to use on the frontend.
I've tried it for the case we need it for, and it works exactly as I'd expect. I also read through the source and can't find any reason why this would be problematic. It require Node's events, but there's a fill for that for browsers that it uses.
An official response would be nice though since I can't find anything via Google. I'm just asking because "Node" is literally in the name, which suggests that it has some dependency on Node.
Thank you
We're using this on our backend, but ran into a simple case where it would be very handy to use on the frontend. I can't find any mention of why this wouldn't be advisable to use on the frontend.
I've tried it for the case we need it for, and it works exactly as I'd expect. I also read through the source and can't find any reason why this would be problematic. It require Node's
events, but there's a fill for that for browsers that it uses.An official response would be nice though since I can't find anything via Google. I'm just asking because "Node" is literally in the name, which suggests that it has some dependency on Node.
Thank you