Replies: 2 comments 3 replies
-
Hey @mertafor! Have you seen the docs on NextAuth.js? There are some hints in regard to this and there's also a link to a working example. Hope this helps! |
Beta Was this translation helpful? Give feedback.
3 replies
-
In case it helps someone :
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Apparently this library is using config to skip routes that will not be translated.
However, Next Auth library is also using matcher to secure certain routes. Apparently if I define matcher for the routes that should be secured by next auth, those routes will also be excluded from next-intl translations. Is there any way to set matcher for different cases like this?
By the way this is probably a NextJS middleware question rather than next-intl, but I'd appreciate any help.
Beta Was this translation helpful? Give feedback.
All reactions