next-auth VS next-connect

NextAuth.js is not perfect. One of the shortcomings is that it currently does not implement federated logout. This means that even if a user signs out of the Next.js app, he does NOT get signed out of the Cognito user pool client. As a consequence, the user is not really being logged out (i.e he is able to login again without providing the credentials). You can read more about this problem in this Github thread.

NextAuth for adding auth

Let's learn a bit about Descope and how to use it with Auth.js (next-auth) to protect our Next.js app with role-based access control (RBAC).

https://github.com/nextauthjs/next-auth/issues/5647#issuecom...

Next Auth CognitoProvider Internal Library: https://github.com/nextauthjs/next-auth/blob/v4/packages/next-auth/src/providers/cognito.ts

I mentioned this in an age-old discussion on NextAuth GitHub repo.

Authentication is a fundamental part of most web applications. Integrating authentication into your Next.js app can be simplified with NextAuth, a powerful authentication library that supports various authentication methods. However, the documentation around setting up NextAuth with the "Credentials" auth provider might not be as clear as you'd hope. My implementation is greatly enriched and partially based on Next-Auth docs and the following github thread.

For Auth: https://authjs.dev/ - works like a charm with Svelte https://authjs.dev/reference/sveltekit

NextAuth.js

I'm surprised nobody mentioned https://authjs.dev/

Try next-connect

Same. I found this example [1] particularly helpful, although I don't know how good this [2] library it uses is. Overall, I've seen multiple OSS projects [3] that try to support a missing functionality in Next.js seem to just give up trying to keep up with their breaking changes.

[1] https://stackblitz.com/edit/github-mwzv1t?file=README.md

[2] https://github.com/hoangvvo/next-connect

[3] https://github.com/cyrilwanner/next-optimized-images

import { getMongoClient } from 'lib/mongodb'; async function createHandler(req, res) { const { text } = req.body; const createdAt = new Date(); if (!text) { res.status(400).json({ message: 'Validation errors', errors: { text: ['Please add a text value'], }, }); return; } const goals = (await getMongoClient()).db.collection('goals'); const { insertedId: _id } = await goals.insertOne({ text, createdAt, }); res .status(201) .json({ _id, text, createdAt }); } async function listHandler(req, res) { const goals = (await getMongoClient()).db.collection('goals'); const list = []; const cursor = goals.find({}, { sort: { createdAt: 1 }, }); if ((await goals.estimatedDocumentCount()) === 0) { res.status(204).send(undefined); return; } while (await cursor.hasNext()) { const goal = await cursor.next(); list.push(goal); } res.json(list); } // Instead of this you should use https://github.com/hoangvvo/next-connect export default function handler(req, res) { if (req.method === 'POST') { createHandler(req, res); } else { listHandler(req, res); } }

Interesting approach. I am personally not a fan of how it plays out. I think next-connect provides a cleaner approach to this problem. https://github.com/hoangvvo/next-connect

Hey, thanks for the feedback! The genesis of this library is that I used next-connect in one of my apps but I personally didn't like combining routing with middleware layer and I had some issue related to matching although I wasn't matching multiple routes in one file. I didn't find workaround to this and honestly I didn't had motivation to search more. Instead I thought making utility for middleware that would fit to my needs would be really cool thing, and extracting it from my app source to separate public library would be even cooler since I'm beginner open sourcerer but i plan to go further into this direction so I guess its a good start 😄

I think what you're looking for is a way to access your DB via middleware, if so take a look at: https://github.com/hoangvvo/next-connect.

I use next-connect to use connect-like middlewares. A traditional API route handler in Next.js is like:

Are you trying to run some middleware before the api functions? If so, this may help next-connect