This repository has been archived by the owner on May 14, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 465
Wrong event names after uglify-ing the code #406
Labels
Comments
Hi, The fix in #407 worked. Hope this gets merged soon. |
🔔 Ping @pfmooney 😊 |
I've also created pull request to fix this issue. #492 |
I am unclear why one would even need to minify/uglify this library. The intention of this library is to be used in a Node.js environment. Minification does nothing in such an environment. |
👋 On February 22, 2023, we released version 3 of this library. As a result, we are closing this issue/pull request. Please see issue #839 for more information, including how to proceed if you feel this closure is in error. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have an issue with the ldap client.
In one of my build step, the javascript code gets uglyfied. In that step, functions getting renamed etc. Normally that's not a problem, but because the event name in the client is generated off of the message name, a wrong event will be raised.
I think instead of getting the name from
msg.constructor.name
, getting it withmsg.type
would fix the problem.I'll create a PR with my solution.
The text was updated successfully, but these errors were encountered: