From e035161ab652abdd5fb1bc45d5f8139c924a4f53 Mon Sep 17 00:00:00 2001 From: Matthew Stibbard Date: Wed, 3 Jul 2024 11:09:36 +1000 Subject: [PATCH] docs: add note to vercel isr --- documentation/docs/25-build-and-deploy/90-adapter-vercel.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/documentation/docs/25-build-and-deploy/90-adapter-vercel.md b/documentation/docs/25-build-and-deploy/90-adapter-vercel.md index f911d3b7f4f9..b9436a9f742c 100644 --- a/documentation/docs/25-build-and-deploy/90-adapter-vercel.md +++ b/documentation/docs/25-build-and-deploy/90-adapter-vercel.md @@ -125,6 +125,8 @@ export const config = { The `expiration` property is required; all others are optional. +> Do not specify [prerender page options](/docs/page-options#prerender) on ISR routes as they take precedence over ISR configuration. + ## Environment variables Vercel makes a set of [deployment-specific environment variables](https://vercel.com/docs/concepts/projects/environment-variables#system-environment-variables) available. Like other environment variables, these are accessible from `$env/static/private` and `$env/dynamic/private` (sometimes — more on that later), and inaccessible from their public counterparts. To access one of these variables from the client: