David Luecke

You should already be able to overwrite `host` and `protocol` in the [`oauth` configuration settings `defaults`](https://docs.feathersjs.com/api/authentication/oauth.html#configuration): ```js { "authentication": { "oauth": { "redirect": "/frontend", "defaults": { "host": "localhost", "protocol": "https"...

Personally, I am a fan of being explicitly able to see the entire hook flow in a single file (in hindsight, even being able call `.hooks` multiple times probably wasn't...

I'd love to add an example for the newest version to the Cookbook. Looks like there isn't a lot of resources on how to do this with NodeJS/Express in general...

There is currently not but it might be a good idea to be able to add some kind of middleware.

I know @claustres has been doing the work around `feathers-distributed` and had some great ideas around distributing so maybe he can chime in here, too. From my perspective on a...

Yeah, @ekryski has been a big proponent of this change, too. The only tricky part would be backwards compatibility with old services. I am not sure there is a way...

How does it bork without the TypeScript dependency? I just checked and I don't have it installed locally on the Linux or Mac machine I tested this on.

All good suggestions, here are the things that I'll try and address: - [ ] The `feathers g` alias currently doesn't exist but I also don't like that it just...

Sounds good. Will definitely revisit this for the next version as well.

I am not seeing any problems with your first code example so a complete example to reproduce would be helpful. Usually creating related entries would happen in a hook though...