@astrojs/cloudflare

2.0.0

Major Changes

#4815 ce0b92ba7 Thanks @AirBorne04! - adjusted esbuild config to work with worker environment (fixing solid js ssr)

1.0.2

Patch Changes

#4558 742966456 Thanks @tony-sull! - Adding the withastro keyword to include the adapters on the Integrations Catalog

1.0.1

Patch Changes

#4232 bfbd32588 Thanks @Ekwuno! - Update README

1.0.0

Major Changes

04ad44563 - > Astro v1.0 is out! Read the official announcement post.

No breaking changes. This package is now officially stable and compatible with [email protected]!

0.5.0

Minor Changes

#3806 f4c571bdb Thanks @nrgnrg! - add support for compiling functions to a functions directory rather than _worker.js

0.4.0

Minor Changes

#4068 54b33d50f Thanks @matthewp! - Add explicit errors when omitting output config

Patch Changes

#4072 a198028b0 Thanks @matthewp! - Fixes Cloudflare throwing an error for process

0.3.0

Minor Changes

#4015 6fd161d76 Thanks @matthewp! - New output configuration option

This change introduces a new "output target" configuration option (output). Setting the output target lets you decide the format of your final build, either:
- "static" (default): A static site. Your final build will be a collection of static assets (HTML, CSS, JS) that you can deploy to any static site host.
- "server": A dynamic server application. Your final build will be an application that will run in a hosted server environment, generating HTML dynamically for different requests.
If output is omitted from your config, the default value "static" will be used.

When using the "server" output target, you must also include a runtime adapter via the adapter configuration. An adapter will adapt your final build to run on the deployed platform of your choice (Netlify, Vercel, Node.js, Deno, etc).

To migrate: No action is required for most users. If you currently define an adapter, you will need to also add output: 'server' to your config file to make it explicit that you are building a server. Here is an example of what that change would look like for someone deploying to Netlify:
```
import { defineConfig } from 'astro/config';
import netlify from '@astrojs/netlify/functions';

export default defineConfig({
  adapter: netlify(),
+ output: 'server',
});
```

#4018 0cc6ede36 Thanks @okikio! - Support for 404 and 500 pages in SSR

#3973 5a23483ef Thanks @matthewp! - Adds support for Astro.clientAddress

The new Astro.clientAddress property allows you to get the IP address of the requested user.
This property is only available when building for SSR, and only if the adapter you are using supports providing the IP address. If you attempt to access the property in a SSG app it will throw an error.

0.2.4

Patch Changes

#3885 bf5d1cc1e Thanks @delucis! - Integration README fixes

0.2.3

Patch Changes

#3854 b012ee55 Thanks @bholmesdev! - [astro add] Support adapters and third party packages

0.2.2

Patch Changes

#3777 976e1f17 Thanks @tony-sull! - Disables HTTP streaming in Cloudflare Pages deployments

0.2.1

Patch Changes

#3695 0d667d0e Thanks @nrgnrg! - fix custom 404 pages not rendering

0.2.0

Minor Changes

#3600 7f423581 Thanks @nrgnrg! - add SSR adaptor for Cloudflare Pages functions