Open ddennis opened 7 years ago
This is still an issue with v7.1.1.
Looking at the code, it is really not resolvable, but adding 'request' as a reserved event name to Primus should stop "primus-emit" fro intercepting "request" event, like below:
const socket = new primus(server, { transformer: ..., parser: ... });
socket.reserved.events['request'] = 1;
Hi
I am currently using Primus 5.2.2 with the primus-emit plugin.
I am trying to add your plugin to an exiting project to provide better validation on user interaction in the backend.
Disabling the "primus-emit" plugin, everything seems to work fine. Are there any way these two plugins can work together? /Dennis