David Luecke

There are no more verifiers in v4. Strategies are now customized by extending them as is documented in - [The authentication guide](https://docs.feathersjs.com/guides/basics/authentication.html) for GitHub oAuth - In the API docs...

Can probably be improved by pointing to the [`parseStrategies` and `authStrategies` configuration option](https://docs.feathersjs.com/api/authentication/service.html#configuration) where the name of the strategy you want to use has to be added.

I would see how AJV does this since the error is coming from there. We could work around it but I'm pretty sure someone needed to do hot module reloading...

This should be fixed in the next prerelease via https://github.com/feathersjs/feathers/pull/2702. Thank you for the PR!

To be honest I'd rather have it the other way around so you won't be able to register hooks multiple times in the future. It's also difficult to formalize what...

All good, this isn't a bad suggestion, it would just be a breaking change since people might now rely on it being replaced.

As you mentioned, some libraries allow customizing the settings through `params.connection` (or additionally `request.defaults` for requests). Since the default request type is `application/json`, converting JSON back usually makes sense. For...

_From @eric-burel on June 8, 2018 17:7_ Hi, thanks for your feedback. Will you enjoy authentication when using a link, given that the auth token is stored in the localStorage...

True, you'd have to add the token as a query parameter. How would the request and download look using plain fetch? I'm not opposed to making the `.json()` call optional...

_From @eric-burel on June 9, 2018 20:38_ Using fetch and the FileSaver lib you will simply write something like ```js fetch('my-file') .then(res => res.blob()) .then(blob => FileSaver.saveAs(blob, "myzip.zip") ``` Yeah...