Jason Walton

@bluebob Haha. Thanks. My ultimate solution to this, though, was to write a whole new project that supports OpenAPI 3.x.x: https://github.com/exegesis-js/exegesis

I've spent the past several weeks writing a new OpenAPI 3.x.x framework for node.js from the ground up. You can check it out [here](https://github.com/exegesis-js/exegesis/blob/master/README.md).

https://github.com/exegesis-js/exegesis is going strong - we're using it every day in production.

+1 - I'm running into this, too. :(

My test case, in case you're curious - if you connect with a heartbeat, then send a message, then suspend your worker process, wait for RabbitMQ to kill your connection,...

It would be nice if it didn't write it at all. If I have an existing key like "/foo/bar", I need to create a "/foo" directory in e3w or else...

Oh... And if I set the root key to "", I get: ``` panic: root key should not be empty or end with / ``` Why can't I see all...

Note that [`npm-run`](https://www.npmjs.com/package/npm-run) is an alternative to `npx`, which doesn't have this problem. This is a security issue that's been open for over a year - seems unlikely it will...

Thanks @mbround18! This solution got me going in the right direction. One disadvantage to @mbround18's solution above is that when you call `client.ws().connect()`, the client will always set the `Sec-WebSocket-Version`...

@nicholasgriffintn When you call `start()`, it calls into [`poll()` immediately and synchronously](https://github.com/bbc/sqs-consumer/blob/961e842c0f9091a944ee4dc4d18f0e241940ec26/src/consumer.ts#L112), so `this.stopped` will be false when we call into `poll()`. That test case validates that [handleMessage was called...