|
1 | 1 | # @opennextjs/cloudflare |
2 | 2 |
|
| 3 | +## 1.19.6 |
| 4 | + |
| 5 | +### Patch Changes |
| 6 | + |
| 7 | +- [#1246](https://github.com/opennextjs/opennextjs-cloudflare/pull/1246) [`5d2014f`](https://github.com/opennextjs/opennextjs-cloudflare/commit/5d2014f09afa24eed983d2ddcd568ac118a728fd) Thanks [@vicb](https://github.com/vicb)! - fix: do not log expected expected D1 errors |
| 8 | + |
| 9 | + The `populateCache` command adds columns to the D1 tag cache for SWR support. |
| 10 | + This is required for older deployments made before those column were added. |
| 11 | + SQLite errors when the columns exist and we should not log those errors. |
| 12 | + |
| 13 | +- [#1244](https://github.com/opennextjs/opennextjs-cloudflare/pull/1244) [`01babce`](https://github.com/opennextjs/opennextjs-cloudflare/commit/01babce15c28d7a81797d6fbaebe281e930b92f5) Thanks [@tahmid-23](https://github.com/tahmid-23)! - fix: drop streaming wasm calls in Turbopack runtime |
| 14 | + |
| 15 | + Turbopack replaces wasm imports using `WebAssembly.compileStreaming` and |
| 16 | + `WebAssembly.instantiateStreaming`. These functions are not available in |
| 17 | + the workerd runtime. |
| 18 | + |
| 19 | + We add a helper `loadWasmChunkFn`. This is a generated switch statement |
| 20 | + that contains an import for each wasm chunk. We use static strings for |
| 21 | + all imports to ensure that all necessary wasm chunks will be detected |
| 22 | + and bundled for the final build. |
| 23 | + |
| 24 | + The Turbopack patcher replaces the invocations in `loadWebAssembly` and |
| 25 | + `loadWebAssemblyModule`, using the synchronous `WebAssembly.instantiate` |
| 26 | + and redirecting to `loadWasmChunkFn`. |
| 27 | + |
| 28 | +- [#1243](https://github.com/opennextjs/opennextjs-cloudflare/pull/1243) [`1c815de`](https://github.com/opennextjs/opennextjs-cloudflare/commit/1c815de96abbabbd4e5ff81ab299f2b4f3aa77db) Thanks [@tahmid-23](https://github.com/tahmid-23)! - fix: detect object-valued conditions |
| 29 | + |
| 30 | + The pre-existing build condition transform logic had subtle errors: |
| 31 | + |
| 32 | + - failed to recognize object conditions |
| 33 | + (e.g. "workerd": { "import": ..., "require": ... }) |
| 34 | + - sibling pruning only applied to strings, not objects |
| 35 | + |
| 36 | + Now, we fully support object conditions. Furthermore, we prune siblings, |
| 37 | + unless its subtree also contains the build condition. |
| 38 | + |
3 | 39 | ## 1.19.5 |
4 | 40 |
|
5 | 41 | ### Patch Changes |
|
0 commit comments