Document how to access the cloudflare env/bindings from defineWebSocketHandler()

[snickell]

Because cloudflare does not set process.env (ugh, I wish they did, but that's another story), to access any bindings, secrets etc you need access to the cloudflare env, passed with every request.

This is well documented for regular HTTP requests: https://nitro.build/deploy/providers/cloudflare#direct-access-to-cloudflare-bindings

It would be great to document the right way to access the cloudflare env, like bindings, from a websocket handler.

[snickell]

For anyone else really struggling with this, if you're using the cloudflare_durable nitro preset, here's the best "hack" I've been able to find, using as server/plugins/cache-durable-object.js:

let durableObject = null
export const getDurableObject = () => durableObject
export const getDurableObjectEnv = () => durableObject?.env

export default defineNitroPlugin((nitroApp) => {
  nitroApp.hooks.hook('cloudflare:durable:init', (_durableObject, ...args) => {
    durableObject = _durableObject
  })
})

Then you can:

import { getDurableObjectEnv } from '@/server/plugins/cache-durable-object'

export default defineWebSocketHandler({
  async message(peer, body) {
    const env = getDurableObjectEnv()
    console.log("available keys on env: ", Object.keys(env))
  }
})

But.... YUCK, this pollutes with global state vs "serverless", and much complex too. It would be much better to have easy access the event passed in to crossws in the first place, but it doesn't expose it, only on peer._internal.

[pi0]

Have you tried to access bindings from process.env? (Nitro exposes env (with bindings) as process.env for cloudflare)

[snickell]

Hello, thanks for the suggestion.

Looking closer, its entirely possible the issue I'm having is with the cloudflare_durable preset? Specifically, I don't seem to have these bindings set when my websocket responds from a durable object. You're absolutely correct that if I run without a durable object, I do have access to the bindings on process.env.

The other approach I've found is on the cloudflare side, you can now (recently) set wrangler.toml like:

compatibility_flags = ["nodejs_compat", "nodejs_compat_populate_process_env"]

Setting nodejs_compat_populate_process_env instructs cloudflare to populate process.env itself directly.

[acidjazz]

Would really love a solution for this issue, going down the same road

[marr]

Inside your fetch you can access this.env. Inside your handler you can access event.req.cf. Do either of those help?

[acidjazz]

Inside your fetch you can access this.env. Inside your handler you can access event.req.cf. Do either of those help?

how do i access event.req.cf inside defineWebSocketHandler though?