Skip to content
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion pages/cloudflare/_meta.json
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@
"examples": "",
"community": "Community projects",
"troubleshooting": "",
"migrate-from-0.3-to-0.4": "Migrate from 0.3",
"migrate-from-0.3-to-0.5": "Migrate from 0.3",
"0.3": "Release 0.3",
"migrate-from-0.2-to-0.3": "",
"0.2": "Release 0.2"
Expand Down
Original file line number Diff line number Diff line change
@@ -1,11 +1,13 @@
import { SITE } from '../../config';
import { Callout } from 'nextra/components';

### Migrate from 0.3 (to 0.4)
### Migrate from 0.3 (to 0.5)

The `@opennextjs/cloudflare@0.4.0` introduced a new `initOpenNextCloudflareForDev` utility and made `getCloudflareContext` synchronous,
`@opennextjs/cloudflare@0.4.0` introduced a new `initOpenNextCloudflareForDev` utility and made `getCloudflareContext` synchronous,
we'll explore those two differences below, and how they effect applications built using `0.3.x` versions of the adapter.

`@opennextjs/cloudflare@0.5.0` did not introduce any breaking change, meaning that there are no migration steps from `0.4` to `0.5`.

##### `initOpenNextCloudflareForDev`

`initOpenNextCloudflareForDev` is a new utility that needs to be added to the Next.js configuration file in order to integrate the adapter
Expand Down