summaryrefslogtreecommitdiff
path: root/packages/integrations/netlify/README.md
diff options
context:
space:
mode:
Diffstat (limited to 'packages/integrations/netlify/README.md')
-rw-r--r--packages/integrations/netlify/README.md18
1 files changed, 18 insertions, 0 deletions
diff --git a/packages/integrations/netlify/README.md b/packages/integrations/netlify/README.md
index 86fff4fd2..5e7895217 100644
--- a/packages/integrations/netlify/README.md
+++ b/packages/integrations/netlify/README.md
@@ -72,6 +72,24 @@ export default defineConfig({
});
```
+### Per-page functions
+
+The Netlify adapter builds to a single function by default. Astro 2.7 added support for splitting your build into separate entry points per page. If you use this configuration, the Netlify adapter will generate a separate function for each page. This can help reduce the size of each function so they are only bundling code used on that page.
+
+```js
+// astro.config.mjs
+import { defineConfig } from 'astro/config';
+import netlify from '@astrojs/netlify/functions';
+
+export default defineConfig({
+ output: 'server',
+ adapter: netlify(),
+ build: {
+ split: true,
+ },
+});
+```
+
### Static sites
For static sites you usually don't need an adapter. However, if you use `redirects` configuration (experimental) in your Astro config, the Netlify adapter can be used to translate this to the proper `_redirects` format.