Geoff Dutton

I don't really have any experience either, but maintainers not merging their own patches makes sense to me. I'd suggest we utilize the "request review" feature too.

I added a very simple comparison of with and without Laconia [here](https://github.com/geoffs-uncategorized-forks/laconiajs-examples/tree/sls-vanilla-update/examples/serverless-vanilla#comparison-with-and-without-laconiajs). Might help @chris-kobrzak.

Agreed, I was going to suggest we just add it to the CI and perhaps update the root `.nvmrc`.

I'm working on the merge conflicts for the latest master branch (1.2.0). I should've updated it before I opened this PR--my bad.

I have it up to 98% coverage now: https://coveralls.io/github/geoffdutton/chromeless?branch=jest-tests Any thoughts around this? Should I create some more functional tests?

Instead of reloading the whole tab, we can just make sure they've been added to the `tabContexts`. Otherwise, it'll return the `behind-the-scenes` url until the tab is reload.

I've started using it for this Electron project: [DesktopLftp](https://github.com/geoffdutton/desktop-lftp) It works quite well. I'm happy to answer any specifics as best I can.

Cool, yeah I think it's because the `Promise.all` gets executed right away before the first promise resolves. So I think in practice it's probably actually deleting messages before knowing if...

I've been using this in a production lambda, it's working well. Let me know what you think about my latest changes. Basically I pass all the items to the item...

According to our recurly rep, starting with Api v2.10 the responses are different, and some endpoints have changed. @janiscp What endpoint is that screenshot hitting, and what’s the value of...