Hi pal,

How do you intentional close the websocket without reconnection execution, its necessary to pass event code to close method?

when manually invoke close method I think that the reconnection should not be done

ws.close()

thanks

Hi, awesome lib. Is there any way that we can disable reconnect programmatically ?

For example, we init a sockette instance with maxAttempts by default(always enable recconnecting), after a several times of connection failure, I would like to provide a way to disable the further reconnecting manually. Thanks.

In my project, I want to shutdown the connection when I leave out. However, no matter the code I passed to close method, it failed, e.g. ," ws.close(1000, 'out')". Why?

If the close frame contains no status code (payload length == 0), the close code is 1005. In this case sockette should not reconnect.

Ref: https://tools.ietf.org/html/rfc6455#section-7.1.5

Environment: React 16.2, webpack 4.10, sockette 2.0.0

in the react lifecycle method componentWillUnmount method, I will close the socket instance , the error occurs ,

the code blow

error blow

when I add annotation to the ws close method , it get ok,

How can I fix this problem , thx.

Hi, i have a problem when testing my component using mocha & chai, it says:

ReferenceError: WebSocket is not defined
    at module.exports.r.open (/Users/bcw-001/dev/sofia_fe_react/node_modules/sockette/src/index.js:25:32)
    at new module.exports (/Users/bcw-001/dev/sofia_fe_react/node_modules/sockette/src/index.js:48:7)

i use mock-websocket. anyone know what did i miss?

I've created a new Angular project using the Angular CLI and have installed and attempted to import Sockette into my project (an empty Angular project.)

I am getting the below error when trying to import/require Sockette.

TypeError: "Sockette is not a constructor"

1. Via import gets me the above error:

import {Component} from '@angular/core';
import {environment} from '../environments/environment';

import * as Sockette from 'sockette';

@Component({
  selector: 'app-root',
  templateUrl: './app.component.html',
  styleUrls: ['./app.component.scss']
})
export class AppComponent {
  constructor() {
    const socket = new Sockette(environment.websocket_server);
  }
}

2. Via require gets me the same error above:

import {Component} from '@angular/core';
import {environment} from '../environments/environment';

const Sockette = require('sockette');

@Component({
  selector: 'app-root',
  templateUrl: './app.component.html',
  styleUrls: ['./app.component.scss']
})
export class AppComponent {
  constructor() {
    const socket = new Sockette(environment.websocket_server);
  }
}

When I console.log the Sockette object, I get the following:

import {Component} from '@angular/core';
import {environment} from '../environments/environment';

const Sockette = require('sockette');

@Component({
  selector: 'app-root',
  templateUrl: './app.component.html',
  styleUrls: ['./app.component.scss']
})
export class AppComponent {
  constructor() {
    console.log(Sockette);
    const socket = new Sockette(environment.websocket_server);
  }
}

Object { default: default(), … }

Which lead me to try the following (which works!)

import {Component} from '@angular/core';
import {environment} from '../environments/environment';

const Sockette = require('sockette');

@Component({
  selector: 'app-root',
  templateUrl: './app.component.html',
  styleUrls: ['./app.component.scss']
})
export class AppComponent {
  constructor() {
    const socket = new Sockette.default(environment.websocket_server);
  }
}

I'm left assuming this is due to the way Sockette is being exported... any thoughts?

Thank you for making this package! It's great.

This is a feature request.

AWS API Gateway allows only a maximum size of 128kb of data to be sent across 4 x 32kb frames when using Websockets:

https://docs.aws.amazon.com/apigateway/latest/developerguide/limits.html

I would love it if this package allowed me to specify the maximum frame size somewhere and then it would automatically split up messages and re-combine them on the other side to overcome this.

I just tested v2.0.5 and unfortunately the issue is still there. This is my scenario:

1. Open WS connection A.
2. Close WS connection A.
3. Open WS connection B.
4. Close WS connection B.
5. Open WS connection C.

After a while WS connections A and B are reopened. They are initially closed, but re-opened.

Currently Sockette depends on a global WebSocket constructor, which is not the case when used on Node.js.

This PR adds options.WebSocket to allow passing a custom WebSocket constructor, for example from the ws module.

Arrow functions don't create a binding, and a quick look over the code doesn't show a single instance where the difference in bindings would matter. Every instance of this can be replaced with self.

I had to undo the 1000,1001,1005 exceptions in the onClose method. Some reverse proxies like Caddy close the ws with 1001 if you stop/start them, it's so it's annoying having to refresh the page at each reboot or simply reverse proxy config change. Please add an option where you bypass the 1000,1001,1005 check, some application want to keep retrying no matter what.

onclose: e => {
  console.log(`Closed with code: ${e.code}`);
  if (e.code === 1e3 || e.code === 1001 || e.code === 1005) {
    this.ws.reconnect(e);
  }            
},

This PR fixes the issue described in #66 by setting timer value to -1 which would still enable normal functionality of Sockette.reconnect, but at the same time, it will not by mistake clear any other timeouts/intervals.

Closes #66

Since the first call to window.setTimeout or window.setInterval is returning handle with ID 1 calling Sockette.close would unexpectedly clear that timeout, because timer=1 is still a valid handle ID.

As requested by issue #59 my use case is the same. I need to pass a token on every connection attempt and it's only possible to use the token once. So the url must change on every reconnect attempt.

If url param is a function invoke it passing the attempt number

Solution: Change the url param to be of type:

- string
- Promise<string>
- (attempt: number) => Promise<string>
- (attempt: number) => string

So the usage would look like:

// string as it is now
new Sockette('wss://address')
// promise style. just adding the setTimeout to simulate
new Sockette(new Promise((resolve) => {
  setTimeout(() => {
    resolve('wss://address')
  }, 5000)
}))

new Sockette(Promise.resolve('wss://address'))

new Sockette((attempt) => `wss://address?attempt${attempt}`)

new Sockette(async (attempt) => await Promise.resolve(`wss://address?attempt${attempt}`))

Right now in order to change websocket url you have to create a new instance of Sockette. This an issue for us because our url includes authorization token which expires after some time and when Sockette tries to reconnect it tries to reconnect using an expired token.

Here are a couple of possible solutions to this issue:

1. getUrl config which can be set to a function which either returns a string directly or a Promise<string>. Sockette would use this function every time it tries to automatically establish websocket connection.
2. setUrl() method on the Sockette class and ability to set onreconnect config to a function which returns a Promise. Sockette would wait for onreconnect promise to finish before it would try to reestablish connection.

@lukeed what do you think about it? Do you have any better suggestions?