Jonas Pauthier

Google+ API is still in the Google Cloud Console:  From what I understood you need to active the API as a whole but perhaps I'm mistaken here.

I agree good idea. Compatibility with `system` and `boom` type matching, if that's what you meant @devinivy, also sounds good. 👍

If I may ask, why do you want to setup a different path for the callback in the first place? From what I understood when you query your endpoint, `/login`...

For the checks on your query parameter, depending on the checks you want to make you could validate them directly in your route configuration through `joi` schemas. If you want...

It seems that Eran deleted them from Medium. I'll reach out to him to check whether they're available somewhere else. Thanks for raising the issue.

Thanks @hueniverse. 👍

`@hapi/log` is not ready for usage right now. I believe we don't want to really deprecate `good` until we have something else to offer. Thanks for the reminder though.

@TinaHeiligers I believe there were changes in how streams were implemented in `node@18` which can be a reason for cleanup code not to be called. Depending on the node version...

I'm not currently using it. I couldn't make it work on my current project. If you want to make the PR, go for it. 😃

I thought of `NODE_OPTIONS` but this will be picked up no matter what version of `node` you're running thus causing errors on `node < 17`. It's not mention in `node`'s...