0
Fork 0
mirror of https://github.com/withastro/astro.git synced 2024-12-23 21:53:55 -05:00
astro/packages/integrations/cloudflare
Fred K. Bot 005d53145f
[ci] release (#4555)
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
2022-08-31 18:03:27 -04:00
..
src [ci] format 2022-08-08 17:12:48 +00:00
test chore: skip cloudflare test for now (#4117) 2022-08-02 10:26:00 -05:00
CHANGELOG.md [ci] release (#4555) 2022-08-31 18:03:27 -04:00
package.json [ci] release (#4555) 2022-08-31 18:03:27 -04:00
README.md Note private env var handling with cloudflare builds (#4490) 2022-08-26 09:03:22 -04:00
tsconfig.json feat: add SSR adaptor for cloudflare pages functions (#3600) 2022-06-16 10:12:25 -04:00

@astrojs/cloudflare

An SSR adapter for use with Cloudflare Pages Functions targets. Write your code in Astro/Javascript and deploy to Cloudflare Pages.

In your astro.config.mjs use:

import { defineConfig } from 'astro/config';
import cloudflare from '@astrojs/cloudflare';

export default defineConfig({
  output: 'server',
  adapter: cloudflare()
});

Options

Mode

mode: "advanced" | "directory"

default "advanced"

Cloudflare Pages has 2 different modes for deploying functions, advanced mode which picks up the _worker.js in dist, or a directory mode where pages will compile the worker out of a functions folder in the project root.

For most projects the adaptor default of advanced will be sufficiant, when in this mode the dist folder will contain your compiled project. However if you'd like to use pages plugins such as Sentry for example to enable logging, you'll need to use directory mode.

In directory mode the adaptor will compile the client side part of you app the same way, but it will move the worker script into a functions folder in the project root. The adaptor will only ever place a [[path]].js in that folder, allowing you to add additional plugins and pages middleware which can be checked into version control.

// directory mode
export default defineConfig({
  adapter: cloudflare({ mode: "directory" }),
});

Enabling Preview

In order for preview to work you must install wrangler

$ pnpm install wrangler --save-dev

It's then possible to update the preview script in your package.json to "preview": "wrangler pages dev ./dist".This will allow you run your entire application locally with Wrangler, which supports secrets, environment variables, KV namespaces, Durable Objects and all other supported Cloudflare bindings.

Streams

Some integrations such as React rely on web streams. Currently Cloudflare Pages functions are in beta and don't support the streams_enable_constructors feature flag.

In order to work around this:

  • install the "web-streams-polyfill" package
  • add import "web-streams-polyfill/es2018"; to the top of the front matter of every page which requires streams, such as server rendering a React component.

Environment Variables

As Cloudflare Pages Functions provides environment variables differently, private environment variables needs to be set through vite.define to work in builds.

// astro.config.mjs
export default {
  vite: {
    define: {
      'process.env.MY_SECRET': JSON.stringify(process.env.MY_SECRET),
    },
  },
}