Karl Vito Lam

No exception handling

2

Currently the library just return None for catched exception, which is super difficult to debug. It is suggested to change to return the error to the caller.

Here's the fix for the issue when we run `yarn build`. Fixing this would help the newbies to test easily. @thlorenz ``` $ yarn build yarn run v1.22.19 $ yarn...

fixes #358 - the connection:opened event should be emited after all operations ?

3

Creating receiver link right after 'connection:opened' event will get duplicated messages. Using process.nextTick() to create the link can avoid the issue. Please review whether this fix is appropriate or not......