While deploying - A Node.js API is used (process.exit at line: 1451) which is not supported in..

While deploying my next.js app on vercel it's giving this error

./node_modules/better-auth/dist/chunk-62MWLLEG.js
A Node.js API is used (process.exit at line: 1451) which is not supported in the Edge Runtime.
Learn more: https://nextjs.org/docs/api-reference/edge-runtime

./node_modules/better-auth/dist/chunk-62MWLLEG.js
A Node.js API is used (process.exit at line: 1451) which is not supported in the Edge Runtime.
Learn more: https://nextjs.org/docs/api-reference/edge-runtime

./node_modules/better-auth/dist/chunk-62MWLLEG.js
A Node.js API is used (process.exit at line: 1451) which is not supported in the Edge Runtime.
Learn more: https://nextjs.org/docs/api-reference/edge-runtime

./node_modules/better-auth/dist/chunk-62MWLLEG.js
A Node.js API is used (process.exit at line: 1451) which is not supported in the Edge Runtime.
Learn more: https://nextjs.org/docs/api-reference/edge-runtime

Jjoseph013318 While deploying my next.js app on vercel it's giving this error `./node_module...

bekacru•3/1/25, 6:15 PM

better auth doesn't work on edge

Bbekacru better auth doesn't work on edge

joseph013318OP•3/2/25, 4:22 AM

How to resolve the issue? I am deploying in vercel with better-auth as authentication

lonelyplanet•3/2/25, 4:57 AM

most likely your either setting the runtime to edge in a route with export const runtime = 'edge';export const runtime = 'edge'; along with using better auth which doesnt work.

or your using better-auth in you

middleware.ts

middleware.ts

lonelyplanet•3/2/25, 4:57 AM

@joseph013318 Read up what the edge runtime is and also how nextjs middleware works

Llonelyplanet most likely your either setting the runtime to edge in a route with `export cons...

Ping•3/2/25, 4:58 AM

most likely either a export const runtime = 'edge';

Better Auth doesn't work on edge.

PPing > most likely either a export const runtime = 'edge'; Better Auth doesn't work o...

lonelyplanet•3/2/25, 4:58 AM

I know? Im saying that mostly likely the issue?

Ping•3/2/25, 4:59 AM

I missunderstood you, sorry.

Llonelyplanet most likely your either setting the runtime to edge in a route with `export cons...

joseph013318OP•3/3/25, 3:44 AM

@Ping @lonelyplanet Yes using it in middleware. This is the exact code I used as in the better-auth docs

https://www.better-auth.com/docs/integrations/next#middleware

I need protected routes with auth! How do I solve the issue?

Next.js integration | Better Auth

Integrate Better Auth with Next.js.

lonelyplanet•3/3/25, 5:10 AM

Care to share your middleware?

Llonelyplanet Care to share your middleware?

joseph013318OP•3/4/25, 4:31 PM

@lonelyplanet Sure.


import { getSessionCookie } from "better-auth/cookies";
import { NextResponse } from "next/server";
 
export async function middleware(request) {
    const sessionCookie = getSessionCookie(request); 
    console.log("sessionCookie", sessionCookie);
    // Optionally pass config as the second argument if cookie name or prefix is customized.
    if (!sessionCookie) {
        return NextResponse.redirect(new URL("/login", request.url));
    }
    return NextResponse.next();
}
 
export const config = {
    matcher: ["/dashboard"],
};


import { getSessionCookie } from "better-auth/cookies";
import { NextResponse } from "next/server";
 
export async function middleware(request) {
    const sessionCookie = getSessionCookie(request); 
    console.log("sessionCookie", sessionCookie);
    // Optionally pass config as the second argument if cookie name or prefix is customized.
    if (!sessionCookie) {
        return NextResponse.redirect(new URL("/login", request.url));
    }
    return NextResponse.next();
}
 
export const config = {
    matcher: ["/dashboard"],
};

Only in build time the error is occuring

import { getSessionCookie } from "better-auth/cookies"; import { NextResponse } from "next/server"; export async function middleware(request) { const sessionCookie = getSessionCookie(request); console.log("sessionCookie", sessionCookie); // Optionally pass config as the second argument if cookie name or prefix is customized. if (!sessionCookie) { return NextResponse.redirect(new URL("/login", request.url)); } return NextResponse.next(); } export const config = { matcher: ["/dashboard"], };

While deploying - A Node.js API is used (process.exit at line: 1451) which is not supported in..

Similar Threads

Similar Threads

Similar Threads