●Change8

@cloudflare/vitest-pool-workers@0.20.0

Breaking Changes
📦 cloudflare-workersView on GitHub →
⚠ 2 breaking🐛 1 fixes⚡ 1 deprecations🔧 8 symbols

Summary

This release removes several `miniflare` override options and deprecates the `cache` option in favor of `cacheAPI`. It also ensures backward compatibility for the `cache` option and stops enabling the removed `unsafeStickyBlobs` option.

⚠️ Breaking Changes

  • Removed several options from the `miniflare` override options: `wrappedBindings`, `cacheWarnUsage`, `fetchMock`, and `containerEngine`. For `fetchMock`, use `outboundService` instead. For `containerEngine`, consider using `createTestHarness()` if you need to test against actual containers.
  • The `unsafeStickyBlobs` Miniflare option has been removed and is no longer enabled by the pool. This change has no impact on behavior as the feature it supported was dropped previously.

Migration Steps

  1. Replace `fetchMock` with `outboundService` in `miniflare` override options.
  2. If using `containerEngine` for `miniflare` overrides, consider migrating to `createTestHarness()` for testing against actual containers.
  3. Update `miniflare` configurations to use `cacheAPI` instead of the deprecated `cache` option.

🐛 Bug Fixes

  • Preserved the deprecated Miniflare `cache` option, translating it to `cacheAPI` for backward compatibility. New configurations should use `cacheAPI` directly.

Affected Symbols

miniflare override optionsminiflare.wrappedBindingsminiflare.cacheWarnUsageminiflare.fetchMockminiflare.containerEngineminiflare.cacheminiflare.cacheAPIminiflare.unsafeStickyBlobs

⚡ Deprecations

  • The `cache` option in `miniflare` has been deprecated and renamed to `cacheAPI`. However, `cache` remains functional for backward compatibility.