Handling connection errors about rxjs-websockets HOT 11 CLOSED

There could be multiple connections (the observable is cold) so there is no one error status (unless you make the observable hot or shared). The errors are reported on the messages stream, check the "reconnect on error" example from the readme.

from rxjs-websockets.

onclose can be detected by the connectionStatus stream decrementing, which is easy using the pairwise operator, and extra easy if you make the messages observable shared/hot (in which case the connection status can only increment to one or decrementing to zero).

from rxjs-websockets.

You can also just detect the end of the messages stream for onclose.

from rxjs-websockets.

retryWhen is undefined even when I import it:
import { retryWhen } from 'rxjs/operators'

from rxjs-websockets.

That requires rxjs 5.5 or above.

from rxjs-websockets.

I do have 5.5.6?

from rxjs-websockets.

Try stack overflow or debugging.

from rxjs-websockets.

Maybe you're confusing pipeable operators with the old style, I dunno, I can't see your code.

from rxjs-websockets.

See https://github.com/ReactiveX/rxjs/blob/master/doc/pipeable-operators.md

from rxjs-websockets.

Thanks. I had to import rxjs/Rx, instead of rxjs/Observable.
But now I could not see how I would detect the error. Yes, it repeats the message but I never see console.log(message).

this.conn.messages.retryWhen(errors => errors.delay(1000)).subscribe(message=>{console.log(message)})

from rxjs-websockets.

You should not be importing rxjs/Rx. This will balloon your build size. You should be using pipeable operators now, not instance methods.

It really sounds like you need to learn rxjs before learning rxjs-websockets.

from rxjs-websockets.