Works with "next export"?

[all-the-rice]

Excuse me if I'm missing something simple. Is it possible to use next-auth when using next export?

Maybe I just need a dynamic routing stub in next.congig.js?

Not having any luck yet. Looking really good other than that. Thank you!

[all-the-rice]

Current behavior is it builds and exports fine but then 404 on /api/auth/signin even when I add '/api/auth/signin': { page: '/api/auth/[...nextauth]', }, or '/api/auth/signin': { page: '/api/auth/signin', }, to exportPathMap in next.config.js

[shaunchander]

If I'm not mistaken, next export only works for when all pages on your website can be pre-rendered (generated to static HTML). Because Next Auth requires some level of server-side rendering for the signin pages, I don't believe next export would work.

[stale]

Hi there! It looks like this issue hasn't had any activity for a while. It will be closed if no further activity occurs. If you think your issue is still relevant, feel free to comment on it to keep ot open. Thanks!

[stale]

Hi there! It looks like this issue hasn't had any activity for a while. To keep things tidy, I am going to close this issue for now. If you think your issue is still relevant, just leave a comment and I will reopen it. (Read more at #912) Thanks!

[ElanHasson]

Hi @balazsorban44,

To clarify, next-auth isn't appropriate to use when using next export? I'm able to get my jwt token returned for my client-side only app by using response_type = id_token token, access_type = 'online'.

Should I change my redirect URI to point to my own page with client side logic?