Error "generateStaticParams()" so it cannot be used with "output: export" config.

[PedrooMota]

Summary

I can't build my project, because it gives the following error:

Page "/api/auth/[...nextauth]" is missing "generateStaticParams()" so it cannot be used with "output: export" config.

Even using use client or export const dynamic = 'force-static' in route.ts, my build still gives this error

I checked other discussions, but none of them solved my problem. If anyone knows what to do, I would be grateful.

versions used were:

1. next: 13.5.4
2. next-auth: 4.23.2

Additional information

No response

Example

No response

[icyJoseph]

Right, so if I make the assumption that you are using /api to create Route Handlers, and also use export mode, then I have to tell you that you are trying to combine two different things.

export mode builds a static HTML site, only HTML+JS+CSS to be sent by a "static files server" down to a browser, but the "static file server" doesn't do any other handling, in fact, you have to provide yourself, usually hosting providers do that.

To use Route handlers, you need a Node.js runtime running the Next.js Server (with next start). This is why the compiler wants you to define generateStaticParams so that it can try to build those during next build, and put them into the static HTML output.

[PedrooMota]

I understood. The issue is that locally the application works without using the output: "export", but when deploying to github pages, it requires that you use this command, and that the route.ts file is static. I would like to know if there is a way to deploy without this problem occurring, or if I use another method (Vercel), I can deploy smoothly.

[jeffreyschultz]

I need this ability because we have two deployment footprints. One is hosted within a container that is running nextjs server where next-auth is handling authentication, and another that is being hosted within nginx, where nginx is handling authentication as part of a more complex deployment.

Is there a way to turn off the API Routes for mode: export because when that is set, I don't need the API route functionality? All of my APIs are deployed separately, and this was purely for securing the webapp when serving with nextjs.

I guess the question would ultimately be, do I need to be using the App Router, and just go back to the Page Router?

[airtonix]

It has no server whatsoever.

clarification:

It has no runtime server, but it definitely is still a server... just one that only serves static assets matched from disk (and it has some restrictive ideals about what file extensions get served as what mimetype)

[airtonix]

@jeffreyschultz In your case I'd modify your build step so it deletes the app/api directory before making a build

[Tosinkoa]

@icyJoseph Pls what can I do in a case where I have [...nextauth] and I am trying to do a build. I've added all my credential logic to my app using next auth, and I need to know if I would have to remove next auth, or there is a workaround to this.