Nextjs and seperate backend Nodejs server with Express.js

[Kepron]

Hi,

I'm editing my Nextjs project to migrate to the app folder. While doing this, I thought it would be good to get rid of redux, which was causing me a lot of problems, and decided to use auth.js. Due to build problems caused by SSG, I am using a separate nodejs project for the backend.

I don't want to use any API routes in Nextjs because I have an obsession with everything being neat and clean. I want to handle the API and server-side operations in the Nodejs project as much as possible.

TL;DR, I want to do auth operations with Express.js on my Node.js server. But the rest of my project will be on Nextjs.

• example.com - Port 3000 Nextjs server.
• api.example.com - Port 3001 Nodejs server

Is it possible to do this? If possible, can you share a short example that explains the logic?

[hillac]

I think this issue is related and has a similar setup to what you want: #10389 (comment) . This comment seems to suggest it can work as long as you ensure you install v5.

[hillac]

So add a credentials provider?

[Kepron]

The repo in the link is quite complicated. Also, next-auth v4 is used. I want to use v5. It would be quite a problem to switch from v4 to v5 later.

[hillac]

It looks very straight forward. v5 next-auth front end, @auth/express backend, and configure the api rewrite in next config. I'm not suggesting you fork their repo.

[Kepron]

It looks very straight forward. v5 next-auth front end, @auth/express backend, and configure the api rewrite in next config. I'm not suggesting you fork their repo.

Is it really that simple? But how will this work?

import { auth } from "../auth"
 
export default async function UserAvatar() {
  const session = await auth()
 
  if (!session.user) return null
 
  return (
    <div>
      <img src={session.user.image} alt="User Avatar" />
    </div>
  )
}

Since auth will be in nodejs, it will not be possible to use it this way.

[hillac]

I haven't tried so not sure. I'm just going off the comment of the person in that thread that said they were successful. Have a go and see. To get the session it will call the api which I'm guessing will get re-written to your node server.