Skip to content

Commit 26b9119

Browse files
Apply suggestions from code review
Co-authored-by: Victor Berchet <[email protected]>
1 parent cf9b45e commit 26b9119

File tree

2 files changed

+1
-4
lines changed

2 files changed

+1
-4
lines changed

.changeset/chilly-dryers-begin.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ introduce new `initOpenNextCloudflareForDev` utility and make `getCloudflareCont
66

77
this change introduces a new `initOpenNextCloudflareForDev` function that must called in the [Next.js config file](https://nextjs.org/docs/app/api-reference/config/next-config-js) to integrate the Next.js dev server with the open-next Cloudflare adapter.
88

9-
Also makes `getCloudflareContext` synchronous, so `await`ing such function is no longer necessary.
9+
Also makes `getCloudflareContext` synchronous.
1010

1111
Additionally the `getCloudflareContext` can now work during local development (`next dev`) in the edge runtime (including middlewares).
1212

packages/cloudflare/src/api/cloudflare-context.ts

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -86,9 +86,6 @@ export function getCloudflareContext<
8686
* Performs some initial setup to integrate as best as possible the local Next.js dev server (run via `next dev`)
8787
* with the open-next Cloudflare adapter
8888
*
89-
* (Currently all the setup that this function performs is making sure that `getCloudflareContext` works as intended,
90-
* in the future mode improvements might be added)
91-
*
9289
* Note: this function should only be called inside the Next.js config file, and although async it doesn't need to be `await`ed
9390
*/
9491
export async function initOpenNextCloudflareForDev() {

0 commit comments

Comments
 (0)