Pier Bover

> The main issue with supporting phonegap/cordova at the moment is the need to support android @alazier can you expand on that?

Ok I see the problem. Probably the best way to go for Cordova/Phonegap is making a native plugin (since you already have native iOS and Android libraries) with a JS...

IMO the big advantage of using an action like `use:form` is that it would return control of the whole form to the parent component. No more styling issues but also,...

> Btw, this doesn't work if you remove bind:value. Why? Because `input.validity` is not reactive. I'm guessing when `value` updates, it forces a render of the if block.

> Gotcha. So I guess there has to be a working example (unlike mine) in the docs. It should be trivial to create an action that updates a reactive writable...

> You could also add an `input` or `change` listener (or both) on the form and use event delegation to get the values. That's what I meant with "when these...

> Here's an old library I made once upon a time. It has an action that serialises and deserialises the form data (based on lukeeds excellent library btw!): https://github.com/svelteschool/svelte-forms/blob/master/src/actions/form/getValues.js Cool...

> Found a simple workaround for this - just define an "index" function which then calls your other functions for local development @dupski AFAIK by bundling multiple functions together you...

Is there a way to use `-r module-alias/register` while defining the aliases from JS instead of `package.json`?

> Try using `Pool` instead of `Client` (solved my problem). I've been having this error when using `Pool` too. I'm handling the `error` event on the pool and yet Node...