Skip to content

Releases: opennextjs/opennextjs-cloudflare

@opennextjs/[email protected]

20 Nov 13:32
b53a046

Choose a tag to compare

Patch Changes

@opennextjs/[email protected]

18 Nov 17:12
4d2271c

Choose a tag to compare

Minor Changes

Patch Changes

@opennextjs/[email protected]

11 Nov 09:08
c1a045f

Choose a tag to compare

Minor Changes

@opennextjs/[email protected]

06 Nov 17:02
efc095b

Choose a tag to compare

Patch Changes

  • #968 ddb0589 Thanks @rgembalik! - fix: Compiled config is now imported using pathToFileURL to avoid crashes on Windows.

  • #958 7edf91c Thanks @vicb! - fix: add missing awaits

  • #978 d7ad53e Thanks @vicb! - error early when a node middleware is detected

  • #976 93f4c8a Thanks @rgembalik! - fix: shell quoting on windows machines to avoid upload errors for routes with [...path] segments

@opennextjs/[email protected]

15 Oct 08:23
0060399

Choose a tag to compare

Minor Changes

  • #925 62fee71 Thanks @krzysztof-palka-monogo! - feature: optional batch upload for faster R2 cache population

    This update adds optional batch upload support for R2 cache population, significantly improving upload performance for large caches when enabled via .env or environment variables.

    Key Changes:

    1. Optional Batch Upload: Configure R2 credentials via .env or environment variables to enable faster batch uploads:

      • R2_ACCESS_KEY_ID
      • R2_SECRET_ACCESS_KEY
      • CF_ACCOUNT_ID
    2. Automatic Detection: When credentials are detected, batch upload is automatically used for better performance

    3. Smart Fallback: If credentials are not configured, the CLI falls back to standard Wrangler uploads with a helpful message about enabling batch upload for better performance

    All deployment commands support batch upload:

    • populateCache - Explicit cache population
    • deploy - Deploy with cache population
    • upload - Upload version with cache population
    • preview - Preview with cache population

    Performance Benefits (when batch upload is enabled):

    • Parallel transfer capabilities (32 concurrent transfers)
    • Significantly faster for large caches
    • Reduced API calls to Cloudflare

    Usage:

    Add the credentials in a .env/.dev.vars file in your project root:

    R2_ACCESS_KEY_ID=your_key
    R2_SECRET_ACCESS_KEY=your_secret
    CF_ACCOUNT_ID=your_account

    You can also set the environment variables for CI builds.

    Note:

    You can follow documentation https://developers.cloudflare.com/r2/api/tokens/ for creating API tokens with appropriate permissions for R2 access.

Patch Changes

@opennextjs/[email protected]

10 Oct 19:47
98f0dd3

Choose a tag to compare

Patch Changes

@opennextjs/[email protected]

10 Oct 09:38
b2d14c7

Choose a tag to compare

Minor Changes

  • #937 32ba91a Thanks @vicb! - feat: retrieve CLI environment variables from process.env and .env* files

    Recommended usage on CI:

    • Add your secrets to process.env (i.e. CF_ACCOUNT_ID)
    • Add public values to the wrangler config wrangler.jsonc (i.e. R2_CACHE_PREFIX_ENV_NAME)

    Recommended usage for local dev:

    • Add your secrets to either a .dev.vars* or .env* file (i.e. CF_ACCOUNT_ID)
    • Add public values to the wrangler config wrangler.jsonc (i.e. R2_CACHE_PREFIX_ENV_NAME)

Patch Changes

@opennextjs/[email protected]

08 Oct 15:06
0ada6dc

Choose a tag to compare

Patch Changes

@opennextjs/[email protected]

01 Oct 13:14
5783285

Choose a tag to compare

Patch Changes

@opennextjs/[email protected]

26 Sep 08:35
e0886d1

Choose a tag to compare

Minor Changes

Patch Changes

  • #907 ba4cac5 Thanks @vicb! - refactor: only try to purge the cache when invalidation is configured