[FEATURE] Synchronous getCloudflareContext()

[james-elicx]

Is your feature request related to a problem?

The getCloudflareContext() utility cannot be used in certain places as it is async function, and therefore requires awaiting. Class constructors and global variables often depend on the expectation of being synchronous, and therefore are prevented from leveraging the utility for bindings, and have to use process.env instead.

Describe the solution you'd like

getCloudflareContext() should be able to be used synchronously.

Describe alternatives you've considered

N/A.

@opennextjs/cloudflare version

0.2.1

Additional context

The next-on-pages approach to this problem involved a way to setup the environment in the Next.js config file, and then interacting with a global symbol on process.env in dev mode.

https://github.com/cloudflare/next-on-pages/tree/main/internal-packages/next-dev

Before submitting

• I have checked that there isn't already a similar feature request
• This is a single feature (not multiple features in one request)

[vicb]

context: #136 (comment)
there we might be able to use the async API

[vicb]

Closing as it's ok for it to be async.
See the kvCache implementation in main / release 0.3.0

[LubomirGeorgiev]

@vicb With the async API using Drizzle and next-auth is impossible. Also this is an inconsistency between the production and local dev environment.

For example

import NextAuth from 'next-auth';
import { DrizzleAdapter } from '@auth/drizzle-adapter';
import { db } from './src/db';

export const { handlers, signIn, signOut, auth } = NextAuth({
  // The database connection here needs to be synchronous. There is no way to await it.
  adapter: DrizzleAdapter(db),
  providers: [
  ],
});

[vicb]

Re-opening this issue because of the previous comment.

With the async API using Drizzle and next-auth is impossible

I don't think a sync API would help with your code snippet.
It instantiates NextAuth at top level while env is only available in the request context on workers - as a parameter to the fetch handler.

So you would need to change that.

Note that NextAuth v5 allows lazy init

Also this is an inconsistency between the production and local dev environment.

Could you expand on that?

It is async so that next dev (dev workflow) and wrangler dev/deploy are consistent.

[LubomirGeorgiev]

Re-opening this issue because of the previous comment.

With the async API using Drizzle and next-auth is impossible

I don't think a sync API would help with your code snippet. It instantiates NextAuth at top level while env is only available in the request context on workers - as a parameter to the fetch handler.

So you would need to change that.

Note that NextAuth v5 allows lazy init

Also this is an inconsistency between the production and local dev environment.

Could you expand on that?

It is async so that next dev (dev workflow) and wrangler dev/deploy are consistent.

@vicb Thanks a lot for the response. Next-auth is a complete crap so I just gave up on it so I think we can close this issue.

Btw I forked https://github.com/flarelabs-net/workers-next/ and I am creating a fully featured SaaS template based on it. I will post it here and on Discord soon.

[dario-piotrowicz]

Closing this once again given the last comment from @LubomirGeorgiev 🙂