Getting Module Not Found Error for next/server

[bwheeele]

I have been trying to use the new auth.js so I have "next": "^14.1.0",
"next-auth": "^5.0.0-beta.11", I am still using pages though as well. I am trying to migrate from using Next.js 13.4 and MSAL to using next-auth. I have an auth.ts, auth.config.ts, my nextauth api and a middleware. I keep getting this error though while trying to login or calling getSession() as it seems when my app hits the api/auth/error I get a 500 and the error reads:

Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/node_modules/next/server' imported from /node_modules/next-auth/lib/env.js
Did you mean to import "next/server.js"?

I have tried looking everywhere but can't find any information about this error and what might be causing it. Hopefully I can find someone here who knows what the deal might be. Thank you!

[CommanderRedYT]

Did you get anything here yet? I have this exact same error...

[santiagotri]

Same here, with same environment (pages architecture) "next-auth": "^5.0.0-beta.11"

[choosenname]

I fixed it by using "next": "14.1.4"

[CommanderRedYT]

I fixed it by using "next": "14.1.4"

Had 14.2.3 before, you think it was broken after 14.1.4?

[choosenname]

Yap, 14.1.4 is the latest version that worked for me

[sKopheK]

I fixed it by using "next": "14.1.4"

14.2.16 here, i don't want to go back with next js because of an error in a library

[sKopheK]

i like the comment in next-auth/lib/env.js just before the failing import

// @ts-expect-error Next.js does not yet correctly use the `package.json#exports` field
import { NextRequest } from "next/server";

[GNRSN]

I'm also having this issue, it works with next 15 but it fails in integration-tests run through vitest (vite).

i like the comment in next-auth/lib/env.js just before the failing import

// @ts-expect-error Next.js does not yet correctly use the `package.json#exports` field
import { NextRequest } from "next/server";

Is there an upstream github issue?

[rinarakaki]

Does this #9385 (comment) solve your problem?

[GNRSN]

It did, thanks!

[shahargl]

is there any workaround for that? why should I go back to 14.1.4 for that? :(

[yaman3bd]

I have the same error. Im currently migrating from Pages Router to App Router. My approach is to first upgrade Next.js and all related libraries, adapt to the new APIs, and ensure everything works as expected with the Pages Router. Once that’s stable, I’ll proceed with the migration to the App Router.

⨯ [Error: Cannot find module '/node_modules/next/server' imported from /node_modules/next-auth/lib/env.js
Did you mean to import next/server.js?] {
  code: 'ERR_MODULE_NOT_FOUND',
  url: 'file:///node_modules/next/server'
}

my dependencies:

{
  "next": "15.0.3",
  "next-auth": "^5.0.0-beta.25"
}

[andrewdownss]

Has anyone found a work around?

[trainerkelly]

Hey there! I wrote about the fix (workaround?) I found below. Take a look and let me know if it solves your issues – it solved mine!

[trainerkelly]

Hey there! Thank you so much for posting this – I ran into the same error last night and for some reason, the formatting of the message in your post really clarified what the error was saying. I became determined to fix it and...I think I did! Or at least I have some sort of work-around.

Please read this full post because I ran into some additional errors once the original one was fixed.

MODAL NOT FOUND Fix

The error message specifies a file location and a suggested import. Go to the folder indicated after the "imported from" wording (in the case of the original post, it was /node_modules/next-auth/lib/). Open the following files:

• env.js
• index.js
• actions.js

(Yes, the .js files – NOT the other ones ending in .ts(.map)!)

Update the following imports by adding ".js" at the end of them:

• Inside "env.js":
  • import { NextRequest } from "next/server"; --> import { NextRequest } from "next/server.js”;
• Inside "index.js":
  • import { headers } from "next/headers"; --> import { headers } from "next/headers.js”;
  • import { NextResponse } from "next/server"; --> import { NextResponse } from "next/server.js”;
• Inside "actions.js":
  • import { headers as nextHeaders, cookies } from "next/headers"; --> import { headers as nextHeaders, cookies } from "next/headers.js”; -
  • import { redirect } from "next/navigation"; --> import { redirect } from "next/navigation.”js;

You can also search for the comment "ts-expect-error Next.js does not yet correctly use the package.json#exports field" because each path you need to update has that as the comment above it.

This should resolve that specific issue.

That being said, I ran into two additional issues after I resolved this one that you may want to resolve first.

Additional Issues

⨯ Error: Could not parse module '[project]/node_modules/next/dist/server/route-modules/app-route/vendored/contexts/app-router-context.js'

I'm happy to say that this is an easy enough fix – remove Turbopack (--turbo) from the next dev command in package.json. (Credit to a comment on Reddit for this. It does look like a know issue that will be fixed sometime in the next release, so Turbopack doesn't have to stay off forever.)

⨯ TypeError: (0 , react__WEBPACK_IMPORTED_MODULE_1__.cache) is not a function at uncachedAuth (src/server/auth/index.ts:8:19)

const auth = cache(uncachedAuth); was throwing me that error. I resolved this error by uninstalling the React and React-Dom version I had installed (18.3.1) and reinstalling them to the latest version (19.0.0). It worked beautiful and fixed problem. (Credit to a comment left on Stack Overflow for this idea.)

Everything else ran as expected.

I hope this is helpful to somebody!

[schumacher-jan]

Solved my solution. Thx!