From 4d67e37615de71dc3c26121612f7093f3192cac6 Mon Sep 17 00:00:00 2001 From: rishabhpoddar Date: Tue, 23 Jul 2024 00:36:03 +0530 Subject: [PATCH] fixes broken link --- v2/emailpassword/nextjs/app-directory/about.mdx | 2 +- v2/passwordless/nextjs/app-directory/about.mdx | 2 +- v2/thirdparty/nextjs/app-directory/about.mdx | 2 +- v2/thirdpartyemailpassword/nextjs/app-directory/about.mdx | 2 +- v2/thirdpartypasswordless/nextjs/app-directory/about.mdx | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/v2/emailpassword/nextjs/app-directory/about.mdx b/v2/emailpassword/nextjs/app-directory/about.mdx index a82d63e1a..c4bcad3ef 100644 --- a/v2/emailpassword/nextjs/app-directory/about.mdx +++ b/v2/emailpassword/nextjs/app-directory/about.mdx @@ -40,7 +40,7 @@ npx create-supertokens-app@latest --frontend=next --recipe=^{codeImportRecipeNam Integrating SuperTokens with a Next.js app involves: - Calling the frontend and backend init functions -- Building the various auth flows as per the [custom UI setup guide](../custom-ui/init/frontend). +- Building the various auth flows as per the [custom UI setup guide](../../custom-ui/init/frontend). - Creating a serverless function to expose the auth related APIs which will be consumed by the frontend widgets (on `/api/auth/` by default) - Protecting website routes: Displaying them only when a user is logged in, else redirecting them to the login page - Performing session verification: diff --git a/v2/passwordless/nextjs/app-directory/about.mdx b/v2/passwordless/nextjs/app-directory/about.mdx index a82d63e1a..c4bcad3ef 100644 --- a/v2/passwordless/nextjs/app-directory/about.mdx +++ b/v2/passwordless/nextjs/app-directory/about.mdx @@ -40,7 +40,7 @@ npx create-supertokens-app@latest --frontend=next --recipe=^{codeImportRecipeNam Integrating SuperTokens with a Next.js app involves: - Calling the frontend and backend init functions -- Building the various auth flows as per the [custom UI setup guide](../custom-ui/init/frontend). +- Building the various auth flows as per the [custom UI setup guide](../../custom-ui/init/frontend). - Creating a serverless function to expose the auth related APIs which will be consumed by the frontend widgets (on `/api/auth/` by default) - Protecting website routes: Displaying them only when a user is logged in, else redirecting them to the login page - Performing session verification: diff --git a/v2/thirdparty/nextjs/app-directory/about.mdx b/v2/thirdparty/nextjs/app-directory/about.mdx index a82d63e1a..c4bcad3ef 100644 --- a/v2/thirdparty/nextjs/app-directory/about.mdx +++ b/v2/thirdparty/nextjs/app-directory/about.mdx @@ -40,7 +40,7 @@ npx create-supertokens-app@latest --frontend=next --recipe=^{codeImportRecipeNam Integrating SuperTokens with a Next.js app involves: - Calling the frontend and backend init functions -- Building the various auth flows as per the [custom UI setup guide](../custom-ui/init/frontend). +- Building the various auth flows as per the [custom UI setup guide](../../custom-ui/init/frontend). - Creating a serverless function to expose the auth related APIs which will be consumed by the frontend widgets (on `/api/auth/` by default) - Protecting website routes: Displaying them only when a user is logged in, else redirecting them to the login page - Performing session verification: diff --git a/v2/thirdpartyemailpassword/nextjs/app-directory/about.mdx b/v2/thirdpartyemailpassword/nextjs/app-directory/about.mdx index a82d63e1a..c4bcad3ef 100644 --- a/v2/thirdpartyemailpassword/nextjs/app-directory/about.mdx +++ b/v2/thirdpartyemailpassword/nextjs/app-directory/about.mdx @@ -40,7 +40,7 @@ npx create-supertokens-app@latest --frontend=next --recipe=^{codeImportRecipeNam Integrating SuperTokens with a Next.js app involves: - Calling the frontend and backend init functions -- Building the various auth flows as per the [custom UI setup guide](../custom-ui/init/frontend). +- Building the various auth flows as per the [custom UI setup guide](../../custom-ui/init/frontend). - Creating a serverless function to expose the auth related APIs which will be consumed by the frontend widgets (on `/api/auth/` by default) - Protecting website routes: Displaying them only when a user is logged in, else redirecting them to the login page - Performing session verification: diff --git a/v2/thirdpartypasswordless/nextjs/app-directory/about.mdx b/v2/thirdpartypasswordless/nextjs/app-directory/about.mdx index a82d63e1a..c4bcad3ef 100644 --- a/v2/thirdpartypasswordless/nextjs/app-directory/about.mdx +++ b/v2/thirdpartypasswordless/nextjs/app-directory/about.mdx @@ -40,7 +40,7 @@ npx create-supertokens-app@latest --frontend=next --recipe=^{codeImportRecipeNam Integrating SuperTokens with a Next.js app involves: - Calling the frontend and backend init functions -- Building the various auth flows as per the [custom UI setup guide](../custom-ui/init/frontend). +- Building the various auth flows as per the [custom UI setup guide](../../custom-ui/init/frontend). - Creating a serverless function to expose the auth related APIs which will be consumed by the frontend widgets (on `/api/auth/` by default) - Protecting website routes: Displaying them only when a user is logged in, else redirecting them to the login page - Performing session verification: