YThere is no
QueueEvent type on "@cloudflare/workers-types": "^4.20230321.0", any help?
HIIRC, Queues aren’t compatible with Service Worker syntax
Yis there any reason for that?
HService Worker syntax is maintained for backwards compatibility, but in general, new features/invocations will only be deployed to Module Syntax, as it is more efficient
YIn the addEventListener documentation, it says to use the QueueEvent type.
Am I misunderstanding something?
Am I misunderstanding something?
HUm…
HThat may or may not be a typo?
HLet me check
HOh, just noticed the queue section underneath
YI used to use
Module Syntax but suddenly I decided to use Service Worker Syntax because I want to use Environment Variables in globalThis scope.HLooks like the types only support Module Syntax
YBut I cannot bind any
Environment variables in global scope when I'm using Module syntaxHWhich may or may not mean that the runtime doesn’t support them
HIn general, we don’t recommend binding variables into the global scope(unless necessary for old dependencies), as it slows down execution
HAnd affects the reusability of an isolate
Yoh I see
YThank you
Yfor quick reply
HThere is the AsyncLocalStorage API, which is sort of similar?
HIn the root of your app, you place your environment variables into the storage, and then where you need it in other places, you can pull it back down
YI cannot bind env variables to global scope when I'm using module syntax
because env variables only provide by wrangler (when arrive Request) through
because env variables only provide by wrangler (when arrive Request) through
envYso on initial run (if any Request comes yet), I cannot access to
envHIIRC, that’s what https://developers.cloudflare.com:2083/workers/runtime-apis/nodejs/asynclocalstorage/ is for. You push the environment into the store, and then you can pull it down somewhere else and use the bindings
Cloudflare Workers provides an implemenation of a subset of the Node.js AsyncLocalStorage API for creating in-memory stores that remain coherent …
Yyea I mean.. I cannot push to store bc I cannot access
env because any first Request comes yetHOh, you mean on initialization?
Yyes
YI'm initialize db connection in global scope like this:
Ythe function
isProd, isLocal is trying to access environment variablesYou can do that directly in the function that calls it. Basically, initialize the DB on the first request, and then leave it open
Yok I see
YThanks!
