-
Notifications
You must be signed in to change notification settings - Fork 179
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why singleton? #31
Comments
Technically it doesn't have to be a singleton. I will plan on changing this in a future release. In the mean time below is the workaround for you to try.
I dont personally like this but something to get you going while I get this change done. |
@pvela any help required? |
@pvela @wertlex - I've experimented in a branch that does a few things:
Any thoughts on this? e.g.
Edit: Here's the branch https://github.com/Nexmo/nexmo-node/tree/namespaces |
I am ok to move to ES2015. Thats the future 👍 . |
We are moving away from the singleton approach. Closing this question as answered. |
How to deal with two nexmo accounts or several instances for different purposes?
Is it solution by design or am I missing something?
Why not just:
The text was updated successfully, but these errors were encountered: