Antoine Pultier

I'm migrating tests from Jest to Ava and we use [`.toMatchObject`](https://jestjs.io/docs/expect#tomatchobjectobject) that has an acceptable behaviour, it's like `like` in Ava, but it manages arrays. The order simply needs to...

I made the following code to reproduce the problem (still happening on alpine linux or debian buster with [email protected] and node 12 or 13). ```javascript const WebSocket = require('ws'); const...

The difficulty is to support "context takeover". The RFC defines it like this : > The term "LZ77 sliding window" used in this section means the buffer used by the...

The discussion about the performances is interesting, but I want to mention that the memory leak is still there with [email protected] and node 14.9.0. The current implementation may be faster...

I understand that `verifyClient` is deprecated for good reasons, but I also think it would be good to keep a similar high level API. The recommended alternative works but I...

> I'm trying to prevent upgrade if the origin does not match (CORS). Hi. I just want to be a bit pedantic and mention that WebSockets do not have CORS....

If you don't mind caching the data for no good reasons and wasting memory, `network-only` can be used instead of `no-cache` as it has the expected behaviour. Another workaround is...

A good alternative to request is [`got`](https://github.com/sindresorhus/got) IMHO.

What about [`got`](https://github.com/sindresorhus/got) ?

I am considering to develop a hybrid clustering layer, combining supercluster for static markers and prunecluster for dynamic markers. But if supercluster supports dynamic markers out of the box with...