Astro: @astrojs/cloudflare@13.0.0-alpha.2 Release

Major Changes

• #15037 8641805 Thanks @matthewp! - Updates the Wrangler entrypoint

  Previously, the main field in wrangler.jsonc pointed to the built output, since Wrangler only ran in production after the build completed:

  {
    "main": "dist/_worker.js/index.js",
  }
  

  Now that Wrangler runs in both development (via workerd) and production, Astro provides a default entrypoint that works for both scenarios.

  What should I do?

  Update your wrangler.jsonc to use the new entrypoint:

  {
    "main": "@astrojs/cloudflare/entrypoints/server",
  }
  

  This single entrypoint handles both astro dev and production deployments.

Minor Changes

• #15037 8641805 Thanks @matthewp! - The Wrangler configuration file is now optional. If you don't have custom Cloudflare bindings (KV, D1, Durable Objects, etc.), Astro will automatically generate a default configuration for you.

  What should I do?

  If your wrangler.jsonc only contains basic configuration like this:

  {
    "main": "@astrojs/cloudflare/entrypoints/server",
    "compatibility_date": "2025-05-21",
    "assets": {
      "directory": "./dist",
      "binding": "ASSETS",
    },
  }
  

  You can safely delete the file. Astro will handle this configuration automatically.

  You only need a wrangler config file if you're using:

  • KV namespaces
  • D1 databases
  • Durable Objects
  • R2 buckets
  • Environment variables
  • Custom compatibility flags
  • Other Cloudflare-specific features

Patch Changes

• #15026 90c608c Thanks @matthewp! - Improves prebundling of internal Astro modules

• #15030 b5aa52b Thanks @ematipico! - Fixed an issue where the feature experimental.chromeDevtoolsWorkspace wasn't supported by the new version of the adapter.

• Updated dependencies []:

  • @astrojs/underscore-redirects@1.0.0