You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The dbg variable that is attached to global by this module is making other projects that require this fail testing, when leaking globals are part of their test suite.
Is there any way that variable can be either optional, or removed from globals? I understand the reason is for aiding in console debugging but I can't help but think there's an alternative to that which doesn't require leaking globals.
The text was updated successfully, but these errors were encountered:
If you are using the browser built minified version, it should already have that removed. If you using it within a node environment, setting NODE_ENV to production will prevent it from being registered.
I've gone ahead and removed that line as well. I found a way to enable the debug using localStorage, so I don't need the global anymore.
The
dbg
variable that is attached to global by this module is making other projects that require this fail testing, when leaking globals are part of their test suite.Is there any way that variable can be either optional, or removed from globals? I understand the reason is for aiding in console debugging but I can't help but think there's an alternative to that which doesn't require leaking globals.
The text was updated successfully, but these errors were encountered: