astro/packages/integrations/cloudflare/CHANGELOG.md

@astrojs/cloudflare

4.1.1

Patch Changes

• #5534 fabd9124b Thanks @bluwy! - Update esbuild dependency

• Updated dependencies [9082a850e, 4f7f20616, 05915fec0, 1aeabe417, 795f00f73, 2c836b9d1, 8f3f67c96]:

  • astro@1.6.14

4.1.0

Minor Changes

• #5347 743000cc7 Thanks @AirBorne04! - Now building for Cloudflare directory mode takes advantage of the standard asset handling from Cloudflare Pages, and therefore does not call a function script to deliver static assets anymore. Also supports the use of _routes.json, _redirects and _headers files when placed into the public folder.

Patch Changes

• Updated dependencies [936c1e411, 4b188132e, f5ed630bc]:
  • astro@1.6.11

4.0.1

Patch Changes

• #5301 a79a37cad Thanks @bluwy! - Fix environment variables usage in worker output and warn if environment variables are accessedd too early

• Updated dependencies [88c1bbe3a, a79a37cad]:

  • astro@1.6.5

4.0.0

Major Changes

• #5290 b2b291d29 Thanks @matthewp! - Handle base configuration in adapters

  This allows adapters to correctly handle base configuration. Internally Astro now matches routes when the URL includes the base.

  Adapters now also have access to the removeBase method which will remove the base from a pathname. This is useful to look up files for static assets.

Patch Changes

• Updated dependencies [b2b291d29, 97e2b6ad7, 4af4d8fa0, f6add3924, 247eb7411]:
  • astro@1.6.4

3.1.2

Patch Changes

• #5230 69a532ab6 Thanks @matthewp! - Exports new runtime entrypoint's types

3.1.1

Patch Changes

• #5103 d151d9f3f Thanks @AirBorne04! - enable access to Cloudflare runtime [KV, R2, Durable Objects]
  • access native Cloudflare runtime through import { getRuntime } from "@astrojs/cloudflare/runtime"; now you can call getRuntime(Astro.request) and get access to the runtime environment.

3.1.0

Minor Changes

• #5056 e55af8a23 Thanks @matthewp! - # New build configuration

  The ability to customize SSR build configuration more granularly is now available in Astro. You can now customize the output folder for server (the server code for SSR), client (your client-side JavaScript and assets), and serverEntry (the name of the entrypoint server module). Here are the defaults:

  import { defineConfig } from 'astro/config';
  
  export default defineConfig({
    output: 'server',
    build: {
      server: './dist/server/',
      client: './dist/client/',
      serverEntry: 'entry.mjs',
    },
  });
  

  These new configuration options are only supported in SSR mode and are ignored when building to SSG (a static site).

  Integration hook change

  The integration hook astro:build:start includes a param buildConfig which includes all of these same options. You can continue to use this param in Astro 1.x, but it is deprecated in favor of the new build.config options. All of the built-in adapters have been updated to the new format. If you have an integration that depends on this param we suggest upgrading to do this instead:

  export default function myIntegration() {
    return {
      name: 'my-integration',
      hooks: {
        'astro:config:setup': ({ updateConfig }) => {
          updateConfig({
            build: {
              server: '...',
            },
          });
        },
      },
    };
  }
  

3.0.0

Major Changes

• #4888 2dc582ac5 Thanks @AirBorne04! - adjusting the build settings for cloudflare (reverting back to platform browser over neutral) adjusting the ssr settings for solidjs (to build for node)

2.1.0

Minor Changes

• #4876 d3091f89e Thanks @matthewp! - Adds the Astro.cookies API

  Astro.cookies is a new API for manipulating cookies in Astro components and API routes.

  In Astro components, the new Astro.cookies object is a map-like object that allows you to get, set, delete, and check for a cookie's existence (has):

  ---
  type Prefs = {
    darkMode: boolean;
  };
  
  Astro.cookies.set<Prefs>(
    'prefs',
    { darkMode: true },
    {
      expires: '1 month',
    }
  );
  
  const prefs = Astro.cookies.get<Prefs>('prefs').json();
  ---
  
  <body data-theme={prefs.darkMode ? 'dark' : 'light'}></body>
  

  Once you've set a cookie with Astro.cookies it will automatically be included in the outgoing response.

  This API is also available with the same functionality in API routes:

  export function post({ cookies }) {
    cookies.set('loggedIn', false);
  
    return new Response(null, {
      status: 302,
      headers: {
        Location: '/login',
      },
    });
  }
  

  See the RFC to learn more.

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 astro@1.0.0!

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