Nico Domino
Nico Domino
Yeah so that's the default thing your node process running next.js will expose. So your node process is running on a VM or container or whatever in Amplify and its...
Hmm very weird, but that error object is coming from Google, so something seems wrong there as well. Maybe it's with what we send them, but the Google provider in...
@Nuno111 I see yuo're using `[email protected]`, have you tried the latest `-beta.17`?
So first of all, thanks for contributing this! I'm working on a fastify application as we speak and had been putting off integrating Auth.js :joy: Anyway, I did some testing...
@hillac okay great, thanks for the repo example. Turns out I was just having some issues with the fastify autoload plugin. Seems to all work now!
Regarding your question about the decorator - while I agree, we should try to get as much as possible in the plugin itself, this `"authenticate"` decorator seems like it would...
Also looks like the `toFastifyReply` behaviour was correct when using an async cb - https://fastify.dev/docs/latest/Reference/Routes/#promise-resolution
> Should we register @fastify/formbody in the plugin, and include it as a peer dependency? This would make setup easier. Yeah so this is to auto-parse `x-www-form-urlencoded` bodies correctly, right?...
Yeah I mean if its going to fail in its current state without it installed, I'd say go for it. What I was implying in my previous comment also is...
Hey yeah this looks pretty good already! We'd really appreciate some prep in the new docs for Fastify as well Can you add support for a fastify docs tabs for...