The Postgres development platform. Supabase gives you a dedicated Postgres database to build your web, mobile, and AI applications.
TypeScript aialternativeauthdatabasedenoembeddingsexamplefirebasenextjsoauth2pgvectorpostgispostgrespostgresqlpostgrestrealtimesupabasevectorswebsockets
docs: add cross-links to related guides (part 1) (#51856)
Kody Jackson1e7a5c3243cf
diff --git a/apps/docs/content/guides/ai-tools.mdx b/apps/docs/content/guides/ai-tools.mdxindex ec02d648deb..ced635f657d 100644--- a/apps/docs/content/guides/ai-tools.mdx+++ b/apps/docs/content/guides/ai-tools.mdx@@ -4,7 +4,7 @@ title: 'AI Tools'subtitle: 'Connect your AI coding agent to Supabase.'----Supabase provides everything you need to connect an AI coding agent to your project: a live connection to your database and platform (MCP), portable instructions your agent can reuse (Agent Skills), a one-step bundle of both (Plugin), and copy-paste prompts for tools that don't support any of the above.+Supabase provides everything you need to connect an AI coding agent to your project: a live connection to your database and platform (MCP), portable instructions your agent can reuse ([Agent Skills](/docs/guides/ai-tools/ai-skills)), a one-step bundle of both (Plugin), and copy-paste prompts for tools that don't support any of the above.<Admonition type="note">diff --git a/apps/docs/content/guides/ai/hybrid-search.mdx b/apps/docs/content/guides/ai/hybrid-search.mdxindex a2feb658b26..339be53b439 100644--- a/apps/docs/content/guides/ai/hybrid-search.mdx+++ b/apps/docs/content/guides/ai/hybrid-search.mdx@@ -204,7 +204,7 @@ Deno.serve(async (req) => {})```-This uses OpenAI's `text-embedding-3-large` model to generate embeddings (shortened to 512 dimensions for faster retrieval). Swap in your preferred embedding model (and dimension size) accordingly.+This uses OpenAI's `text-embedding-3-large` model to [generate embeddings](/docs/guides/ai/quickstarts/generate-text-embeddings) (shortened to 512 dimensions for faster retrieval). Swap in your preferred embedding model (and dimension size) accordingly.To test this, make a `POST` request to the function's endpoint while passing in a JSON payload containing the user's query. Here is an example `POST` request using cURL:diff --git a/apps/docs/content/guides/ai/langchain.mdx b/apps/docs/content/guides/ai/langchain.mdxindex 7fbb83ba4ba..7e9469ada43 100644--- a/apps/docs/content/guides/ai/langchain.mdx+++ b/apps/docs/content/guides/ai/langchain.mdx@@ -218,7 +218,7 @@ export const run = async () => {## Hybrid search-LangChain supports the concept of a hybrid search, which combines Similarity Search with Full Text Search. Read the official docs to get started: [Supabase Hybrid Search](https://js.langchain.com/docs/modules/indexes/retrievers/supabase-hybrid).+LangChain supports the concept of a hybrid search, which combines Similarity Search with [Full Text Search](/docs/guides/database/full-text-search). Read the official docs to get started: [Supabase Hybrid Search](https://js.langchain.com/docs/modules/indexes/retrievers/supabase-hybrid).You can install the LangChain Hybrid Search function through our [database.dev package manager](https://database.dev/langchain/hybrid_search).diff --git a/apps/docs/content/guides/ai/vector-indexes/hnsw-indexes.mdx b/apps/docs/content/guides/ai/vector-indexes/hnsw-indexes.mdxindex fb77fe5ffd8..ef733193dc3 100644--- a/apps/docs/content/guides/ai/vector-indexes/hnsw-indexes.mdx+++ b/apps/docs/content/guides/ai/vector-indexes/hnsw-indexes.mdx@@ -115,7 +115,7 @@ Like skip lists, search starts at the top layer and works its way down until itHNSW should be your default choice when creating a vector index. Add the index when you don't need 100% accuracy and are willing to trade a small amount of accuracy for a lot of throughput.-Unlike IVFFlat indexes, you are safe to build an HNSW index immediately after the table is created. HNSW indexes are based on graphs which inherently are not affected by the same limitations as IVFFlat. As new data is added to the table, the index will be filled automatically and the index structure will remain optimal.+Unlike [IVFFlat indexes](/docs/guides/ai/vector-indexes/ivf-indexes), you are safe to build an HNSW index immediately after the table is created. HNSW indexes are based on graphs which inherently are not affected by the same limitations as IVFFlat. As new data is added to the table, the index will be filled automatically and the index structure will remain optimal.## Filtering with HNSW indexesdiff --git a/apps/docs/content/guides/auth/auth-email-passwordless.mdx b/apps/docs/content/guides/auth/auth-email-passwordless.mdxindex 57ad1147672..7f742ea3187 100644--- a/apps/docs/content/guides/auth/auth-email-passwordless.mdx+++ b/apps/docs/content/guides/auth/auth-email-passwordless.mdx@@ -24,7 +24,7 @@ Magic Links are a form of passwordless sign-in where users click on a link sentEmail authentication methods, including Magic Links, are enabled by default.-Configure the Site URL and any additional redirect URLs. These are the only URLs that are allowed as redirect destinations after the user clicks a Magic Link. You can change the URLs on the [URL Configuration page](/dashboard/project/_/auth/url-configuration) for hosted projects, in the `config.toml` [file](/docs/guides/local-development/cli/config#auth.additional_redirect_urls) for local development, or in the `.env` configuration file for [self-hosted Supabase](/docs/guides/self-hosting/docker).+Configure the Site URL and any additional [redirect URLs](/docs/guides/auth/redirect-urls). These are the only URLs that are allowed as redirect destinations after the user clicks a Magic Link. You can change the URLs on the [URL Configuration page](/dashboard/project/_/auth/url-configuration) for hosted projects, in the `config.toml` [file](/docs/guides/local-development/cli/config#auth.additional_redirect_urls) for local development, or in the `.env` configuration file for [self-hosted Supabase](/docs/guides/self-hosting/docker).By default, a user can only request a magic link once every <SharedData data="config">auth.rate_limits.magic_link.period</SharedData> and they expire after <SharedData data="config">auth.rate_limits.magic_link.validity</SharedData>.diff --git a/apps/docs/content/guides/auth/auth-identity-linking.mdx b/apps/docs/content/guides/auth/auth-identity-linking.mdxindex ad8dc478e83..e2508f2df83 100644--- a/apps/docs/content/guides/auth/auth-identity-linking.mdx+++ b/apps/docs/content/guides/auth/auth-identity-linking.mdx@@ -118,7 +118,7 @@ In the example above, the user will be redirected to Google to complete the OAut><TabPanel id="js" label="JavaScript">-For native mobile applications, you can link an identity using an ID token obtained from a third-party OAuth provider. This is useful when you want to use native OAuth flows (like Google Sign-In or Sign in with Apple) rather than web-based OAuth redirects.+For native mobile applications, you can link an identity using an ID token obtained from a third-party OAuth provider. This is useful when you want to use native OAuth flows (like Google Sign-In or [Sign in with Apple](/docs/guides/auth/social-login/auth-apple)) rather than web-based OAuth redirects.```js// Example with Google Sign-In (using a native Google Sign-In library)diff --git a/apps/docs/content/guides/auth/general-configuration.mdx b/apps/docs/content/guides/auth/general-configuration.mdxindex 0bc629faf7b..d319fddc303 100644--- a/apps/docs/content/guides/auth/general-configuration.mdx+++ b/apps/docs/content/guides/auth/general-configuration.mdx@@ -29,6 +29,6 @@ Supabase Auth provides these [general configuration options](/dashboard/project/- This option can be found in the email provider under the provider-specific configuration.{/* - If you previously relied on this config to autoconfirm a user's email address, you can switch to use **Allow unverified email sign in** instead. This new option allows the user to sign in with an unverified email which you can keep track of through the user object. It provides more versatility if you require your users to verify their email address in the future since you can structure your RLS policies to check the user's `email_verified` field. */}-- **Allow anonymous sign-ins**: Allow anonymous users to be created.+- **Allow [anonymous sign-ins](/docs/guides/auth/auth-anonymous)**: Allow anonymous users to be created.- **Allow manual linking**: Allow users to link their accounts manually.diff --git a/apps/docs/content/guides/auth/rate-limits.mdx b/apps/docs/content/guides/auth/rate-limits.mdxindex 7b51ee6ec9a..77d927d9ac5 100644--- a/apps/docs/content/guides/auth/rate-limits.mdx+++ b/apps/docs/content/guides/auth/rate-limits.mdx@@ -36,7 +36,7 @@ curl -X PATCH "https://api.supabase.com/v1/projects/$PROJECT_REF/config/auth" \Supabase Auth uses a token bucket algorithm for endpoint operations that are limited by IP address.-Most buckets have a maximum capacity of 30 requests. When a bucket is full, brief bursts of up to 30 requests can be allowed in a short period. Anonymous sign-ins are an exception: the bucket capacity matches the configured number of anonymous sign-ins per hour. Once a bucket empties, requests are rate limited until tokens refill. The rate limit defines the rate at which the bucket is refilled.+Most buckets have a maximum capacity of 30 requests. When a bucket is full, brief bursts of up to 30 requests can be allowed in a short period. [Anonymous sign-ins](/docs/guides/auth/auth-anonymous) are an exception: the bucket capacity matches the configured number of anonymous sign-ins per hour. Once a bucket empties, requests are rate limited until tokens refill. The rate limit defines the rate at which the bucket is refilled.This means a client that has been idle will tolerate a brief spike in traffic, but sustained requests above the rate limit are denied. When rate limits are exceeded, a **429 Too Many Requests** error is returned.diff --git a/apps/docs/content/guides/auth/sessions.mdx b/apps/docs/content/guides/auth/sessions.mdxindex a7e2c6cc13f..dfd9e261413 100644--- a/apps/docs/content/guides/auth/sessions.mdx+++ b/apps/docs/content/guides/auth/sessions.mdx@@ -87,7 +87,7 @@ As your users continue using your app, refresh tokens are being constantly exchaThe general rule is that a refresh token can only be used once. However, strictly enforcing this can cause certain issues to arise. There are two exceptions to this design to prevent the early and unexpected termination of user's sessions:- A refresh token can be used more than once within a defined reuse interval. By default this is 10 seconds and we do not recommend changing this value. This exception is granted for legitimate situations such as:- - Using server-side rendering where the same refresh token needs to be reused on the server and soon after on the client+ - Using [server-side rendering](/docs/guides/auth/server-side) where the same refresh token needs to be reused on the server and soon after on the client- To allow some leeway for bugs or issues with serializing access to the refresh token request- If the parent of the currently active refresh token for the user's session is being used, the active token will be returned. This exception solves an important and often common situation:- All clients such as browsers, mobile or desktop apps, and even some servers are inherently unreliable due to network issues. A request does not indicate that they received a response or even processed the response they received.diff --git a/apps/docs/content/guides/auth/social-login/auth-google.mdx b/apps/docs/content/guides/auth/social-login/auth-google.mdxindex b011bdc1028..ea892e4c37c 100644--- a/apps/docs/content/guides/auth/social-login/auth-google.mdx+++ b/apps/docs/content/guides/auth/social-login/auth-google.mdx@@ -247,7 +247,7 @@ supabase.auth.signInWithOAuth({})```-For an implicit flow, that's all you need to do. The user will be taken to Google's consent screen, and finally redirected to your app with an access and refresh token pair representing their session.+For an [implicit flow](/docs/guides/auth/sessions/implicit-flow), that's all you need to do. The user will be taken to Google's consent screen, and finally redirected to your app with an access and refresh token pair representing their session.<$Partial path="oauth_pkce_flow.mdx" />diff --git a/apps/docs/content/guides/auth/third-party/firebase-auth.mdx b/apps/docs/content/guides/auth/third-party/firebase-auth.mdxindex fb9d28422b0..7119cc97228 100644--- a/apps/docs/content/guides/auth/third-party/firebase-auth.mdx+++ b/apps/docs/content/guides/auth/third-party/firebase-auth.mdx@@ -163,7 +163,7 @@ When using the Supabase hosted platform, following this step is optional.</Admonition>-Firebase Auth uses a single set of JWT signing keys for all projects. This means that JWTs issued from an unrelated Firebase project to yours could access data in your Supabase project.+Firebase Auth uses a single set of [JWT signing keys](/docs/guides/auth/signing-keys) for all projects. This means that JWTs issued from an unrelated Firebase project to yours could access data in your Supabase project.When using the Supabase hosted platform, JWTs coming from Firebase project IDs you have not registered will be rejected before they reach your database. When self-hosting implementing this mechanism is your responsibility. An easy way to guard against this is to create and maintain the following RLS policies for **all of your tables in the `public` schema**. You should also attach this policy to [Storage](/docs/guides/storage/security/access-control) buckets or [Realtime](/docs/guides/realtime/authorization) channels.diff --git a/apps/docs/content/guides/auth/third-party/overview.mdx b/apps/docs/content/guides/auth/third-party/overview.mdxindex 84dc91ccd0f..e50f7952732 100644--- a/apps/docs/content/guides/auth/third-party/overview.mdx+++ b/apps/docs/content/guides/auth/third-party/overview.mdx@@ -28,7 +28,7 @@ This is made possible if the providers are using JWTs signed with asymmetric keyThere are some limitations you should be aware of when using third-party authentication providers with Supabase.1. The third-party provider must use asymmetrically signed JWTs (exposed as an OIDC Issuer Discovery URL by the third-party authentication provider). The signed JWTs must have a `kid` header parameter to identify which key must be used. Using symmetrically signed JWTs is not possible at this time.-2. The JWT signing keys from the third-party provider are stored in the configuration of your project, and are checked for changes periodically. If you are rotating your keys (when supported) allow up to 30 minutes for the change to be picked up.+2. The [JWT signing keys](/docs/guides/auth/signing-keys) from the third-party provider are stored in the configuration of your project, and are checked for changes periodically. If you are rotating your keys (when supported) allow up to 30 minutes for the change to be picked up.3. It is not possible to disable Supabase Auth at this time.<$Show if="billing:all">diff --git a/apps/docs/content/guides/database/replication.mdx b/apps/docs/content/guides/database/replication.mdxindex a47c5d0291b..bf427c787a3 100644--- a/apps/docs/content/guides/database/replication.mdx+++ b/apps/docs/content/guides/database/replication.mdx@@ -53,7 +53,7 @@ You might use database replication for:For realtime features and syncing data to browsers and mobile apps, see [Realtime](/docs/guides/realtime).-Realtime also uses Postgres changes, but it is intended for broadcasting database updates to clients rather than maintaining a copy of your database in another system.+Realtime also uses [Postgres changes](/docs/guides/realtime/postgres-changes), but it is intended for broadcasting database updates to clients rather than maintaining a copy of your database in another system.## Concepts and termsdiff --git a/apps/docs/content/guides/deployment.mdx b/apps/docs/content/guides/deployment.mdxindex 12e3894cae0..17d86bb306f 100644--- a/apps/docs/content/guides/deployment.mdx+++ b/apps/docs/content/guides/deployment.mdx@@ -53,7 +53,7 @@ Database migrations in your `supabase/` directory, plus Edge Functions and Stora### Can you use your own CI/CD pipeline?-Yes. You can use the [Supabase CLI](/docs/guides/local-development) or the [Terraform provider](/docs/guides/deployment/terraform) in any CI/CD system (GitHub Actions, GitLab CI, CircleCI, etc.).+Yes. You can use the [Supabase CLI](/docs/guides/local-development) or the [Terraform provider](/docs/guides/deployment/terraform) in any CI/CD system ([GitHub Actions](/docs/guides/functions/examples/github-actions), GitLab CI, CircleCI, etc.).### How does collaboration with other developers work?diff --git a/apps/docs/content/guides/deployment/branching/working-with-branches.mdx b/apps/docs/content/guides/deployment/branching/working-with-branches.mdxindex f0f46e9896d..4962cac890e 100644--- a/apps/docs/content/guides/deployment/branching/working-with-branches.mdx+++ b/apps/docs/content/guides/deployment/branching/working-with-branches.mdx@@ -284,7 +284,7 @@ For improved security, we recommend not exposing the `public` schema automatical### Using ORM or custom seed scripts-If you want to use your own ORM for managing migrations and seed scripts, you will need to run them in GitHub Actions after the preview branch is ready. The branch credentials can be fetched using the following example GHA workflow.+If you want to use your own ORM for managing migrations and seed scripts, you will need to run them in [GitHub Actions](/docs/guides/deployment/managing-environments#configure-github-actions) after the preview branch is ready. The branch credentials can be fetched using the following example GHA workflow.```yaml name=.github/workflows/custom-orm.yamlname: Custom ORMdiff --git a/apps/docs/content/guides/deployment/terraform/reference.mdx b/apps/docs/content/guides/deployment/terraform/reference.mdxindex da8cd9ce05d..4089c649b79 100644--- a/apps/docs/content/guides/deployment/terraform/reference.mdx+++ b/apps/docs/content/guides/deployment/terraform/reference.mdx@@ -3,6 +3,6 @@ title: Terraform Provider referencesubtitle: Resources and data sources available through the Terraform Provider----The Terraform Provider provides access to [resources](https://developer.hashicorp.com/terraform/language/resources) and [data sources](https://developer.hashicorp.com/terraform/language/data-sources). Resources are infrastructure objects, such as a Supabase project, that you can declaratively configure. Data sources are sources of information about your Supabase instances.+The [Terraform Provider](/docs/guides/deployment/terraform) provides access to [resources](https://developer.hashicorp.com/terraform/language/resources) and [data sources](https://developer.hashicorp.com/terraform/language/data-sources). Resources are infrastructure objects, such as a Supabase project, that you can declaratively configure. Data sources are sources of information about your Supabase instances.<TerraformProviderSchema />diff --git a/apps/docs/content/guides/functions/ai-models.mdx b/apps/docs/content/guides/functions/ai-models.mdxindex be13fa2acbf..faee2f9bd08 100644--- a/apps/docs/content/guides/functions/ai-models.mdx+++ b/apps/docs/content/guides/functions/ai-models.mdx@@ -6,7 +6,7 @@ subtitle: 'Run AI models in Edge Functions using the built-in Supabase AI API.'tocVideo: 'w4Rr_1whU-U'----Edge Functions have a built-in API for running AI models. You can use this API to generate embeddings, build conversational workflows, and do other AI related tasks in your Edge Functions.+Edge Functions have a built-in API for running AI models. You can use this API to [generate embeddings](/docs/guides/ai/quickstarts/generate-text-embeddings), build conversational workflows, and do other AI related tasks in your Edge Functions.This allows you to:diff --git a/apps/docs/content/guides/functions/limits.mdx b/apps/docs/content/guides/functions/limits.mdxindex 1280d17302c..6de5dcfecee 100644--- a/apps/docs/content/guides/functions/limits.mdx+++ b/apps/docs/content/guides/functions/limits.mdx@@ -9,7 +9,7 @@ subtitle: "Limits applied Edge Functions in Supabase's hosted platform."- Maximum Memory: 256MB- Maximum Duration (Wall clock limit):- This is the duration an Edge Function worker will stay active. During this period, a worker can serve multiple requests or process background tasks.+ This is the duration an Edge Function worker will stay active. During this period, a worker can serve multiple requests or process [background tasks](/docs/guides/functions/background-tasks).- Free plan: 150s- Paid plans: 400s- Maximum CPU Time: 2s (Amount of actual time spent on the CPU per request - does not include async I/O.)diff --git a/apps/docs/content/guides/functions/quickstart-dashboard.mdx b/apps/docs/content/guides/functions/quickstart-dashboard.mdxindex a297ba2e862..0ad6183385c 100644--- a/apps/docs/content/guides/functions/quickstart-dashboard.mdx+++ b/apps/docs/content/guides/functions/quickstart-dashboard.mdx@@ -6,7 +6,7 @@ subtitle: 'Learn how to create, test, and deploy your first Edge Function usingtocVideo: 'EQ5h3NSWMbk'----Supabase allows you to create Supabase Edge Functions directly from the Supabase Dashboard, making it easy to deploy functions without needing to set up a local development environment. The Edge Functions editor in the Dashboard has built-in syntax highlighting and type-checking for Deno and Supabase-specific APIs.+Supabase allows you to create Supabase Edge Functions directly from the Supabase Dashboard, making it easy to deploy functions without needing to set up a [local development environment](/docs/guides/functions/development-environment). The Edge Functions editor in the Dashboard has built-in syntax highlighting and type-checking for Deno and Supabase-specific APIs.This guide will walk you through creating, testing, and deploying your first Edge Function using the Supabase Dashboard. You'll have a working function running globally in under 10 minutes.diff --git a/apps/docs/content/guides/getting-started/api-keys.mdx b/apps/docs/content/guides/getting-started/api-keys.mdxindex 5a2d16d088b..a6676ca6cda 100644--- a/apps/docs/content/guides/getting-started/api-keys.mdx+++ b/apps/docs/content/guides/getting-started/api-keys.mdx@@ -350,4 +350,4 @@ Publishable and secret keys aren't JWTs, which creates a few compatibility diffe- Send publishable and secret keys on the `apikey` header, not on `Authorization: Bearer`. Because the keys aren't JWTs, anything that tries to verify one as a JWT fails. For migration compatibility the `verify_jwt` platform check accepts them on either header, but passing that check doesn't authenticate the caller. See [Authorization headers](/docs/guides/functions/auth-headers).- Edge Functions need to authorize API keys in code. The `verify_jwt` check alone doesn't authenticate a caller that sends only an API key. Use the `@supabase/server` SDK, as shown in [Securing Edge Functions](/docs/guides/functions/auth), rather than relying on the platform check.-- Public Realtime connections last a maximum of 24 hours, unless the connection is upgraded to user-level authentication through Supabase Auth or a supported third-party auth provider.+- Public Realtime connections last a maximum of 24 hours, unless the connection is upgraded to user-level authentication through Supabase Auth or a supported [third-party auth provider](/docs/guides/auth/third-party/overview).diff --git a/apps/docs/content/guides/getting-started/architecture.mdx b/apps/docs/content/guides/getting-started/architecture.mdxindex 2e7fb2a4cc8..de704daf466 100644--- a/apps/docs/content/guides/getting-started/architecture.mdx+++ b/apps/docs/content/guides/getting-started/architecture.mdx@@ -59,7 +59,7 @@ A JWT-based API for managing users and issuing access tokens. This integrates wi### PostgREST (API)A standalone web server that turns your Postgres database directly into a RESTful API.-We use this with our [`pg_graphql`](https://github.com/supabase/pg_graphql) extension to provide a GraphQL API.+We use this with our [`pg_graphql`](https://github.com/supabase/pg_graphql) extension to provide a [GraphQL API](/docs/guides/graphql/api).- Official Docs: [postgrest.org](https://postgrest.org/)- Source code: [github.com/PostgREST/postgrest](https://github.com/PostgREST/postgrest)diff --git a/apps/docs/content/guides/getting-started/migrating-to-new-api-keys.mdx b/apps/docs/content/guides/getting-started/migrating-to-new-api-keys.mdxindex 4d73d1a45d4..02d2e5ea813 100644--- a/apps/docs/content/guides/getting-started/migrating-to-new-api-keys.mdx+++ b/apps/docs/content/guides/getting-started/migrating-to-new-api-keys.mdx@@ -212,7 +212,7 @@ A few behaviors differ from the legacy JWT-based keys. Plan for them during the- Send publishable and secret keys on the `apikey` header. For migration compatibility the `verify_jwt` check also accepts them on `Authorization: Bearer ...`, but passing that check doesn't authenticate the caller, and the keys aren't JWTs, so nothing downstream can verify them as one.- Edge Functions need to authorize API keys in code. The `verify_jwt` platform check alone doesn't authenticate a caller that sends only an API key, so authorize the key in your handler, as shown in [Step 4](#step-4-update-edge-functions).-- Public Realtime connections are limited to 24 hours unless the connection is upgraded with user-level authentication through Supabase Auth or a supported third-party auth provider.+- Public Realtime connections are limited to 24 hours unless the connection is upgraded with user-level authentication through Supabase Auth or a supported [third-party auth provider](/docs/guides/auth/third-party/overview).## Next stepsdiff --git a/apps/docs/content/guides/getting-started/quickstarts/astrojs.mdx b/apps/docs/content/guides/getting-started/quickstarts/astrojs.mdxindex 5e5244bb8cd..5038522c541 100644--- a/apps/docs/content/guides/getting-started/quickstarts/astrojs.mdx+++ b/apps/docs/content/guides/getting-started/quickstarts/astrojs.mdx@@ -23,7 +23,7 @@ cd my-app## 5. Install Supabase client library and Node adapter-Install the `supabase-js` client library and the `@astrojs/node` adapter to enable server-side rendering.+Install the `supabase-js` client library and the `@astrojs/node` adapter to enable [server-side rendering](/docs/guides/auth/server-side).```bashnpm install @supabase/supabase-js @astrojs/nodediff --git a/apps/docs/content/guides/getting-started/quickstarts/tanstack.mdx b/apps/docs/content/guides/getting-started/quickstarts/tanstack.mdxindex 6cc4ac7a1f9..c0cfcdfb3a3 100644--- a/apps/docs/content/guides/getting-started/quickstarts/tanstack.mdx+++ b/apps/docs/content/guides/getting-started/quickstarts/tanstack.mdx@@ -22,7 +22,7 @@ npx @tanstack/cli@latest create my-app## 5. Install the Supabase client libraries-Navigate to the TanStack Start app and install `supabase-js` and `@supabase/ssr`, the helper package that manages cookie-based sessions for server-side rendering.+Navigate to the TanStack Start app and install `supabase-js` and `@supabase/ssr`, the helper package that manages cookie-based sessions for [server-side rendering](/docs/guides/auth/server-side).```bashcd my-app && npm install @supabase/supabase-js @supabase/ssrdiff --git a/apps/docs/content/guides/getting-started/tutorials/with-nextjs.mdx b/apps/docs/content/guides/getting-started/tutorials/with-nextjs.mdxindex 8060eeec0a6..52108cc7e33 100644--- a/apps/docs/content/guides/getting-started/tutorials/with-nextjs.mdx+++ b/apps/docs/content/guides/getting-started/tutorials/with-nextjs.mdx@@ -53,7 +53,7 @@ You can find the full contents of this file [in the example repository](https://Next.js is a versatile framework offering pre-rendering at build time (SSG), server-side rendering at request time (SSR), API routes, and proxy edge-functions.-To better integrate with the framework, we've created the `@supabase/ssr` package for Server-Side Auth. It has all the functionalities to configure your Supabase project to use cookies for storing user sessions. Read the [Next.js Server-Side Auth guide](/docs/guides/auth/server-side/creating-a-client?queryGroups=package-manager&package-manager=npm&queryGroups=framework&framework=nextjs) for more information.+To better integrate with the framework, we've created the `@supabase/ssr` package for Server-Side Auth. It has all the functionalities to configure your Supabase project to use cookies for storing [user sessions](/docs/guides/auth/sessions). Read the [Next.js Server-Side Auth guide](/docs/guides/auth/server-side/creating-a-client?queryGroups=package-manager&package-manager=npm&queryGroups=framework&framework=nextjs) for more information.Install the package for Next.js.