Use with Cloudflare Workers: The need for "node:async_hooks"?

[PizzaConsole]

Hey, amazing project!

I was just wondering on the need for the "node:async_hooks". Specifically because I want to use this in a Cloudflare workers project and I do not really want to have to enable "nodejs_compat"

X [ERROR] Build failed with 1 error:

   X [ERROR] Could not resolve "async_hooks"

       ../../node_modules/.pnpm/@gqloom+core@0.8.2_graphql@16.10.0/node_modules/@gqloom/core/dist/index.js:58:34:
         58 │ import { AsyncLocalStorage } from "async_hooks";
            ╵                                   ~~~~~~~~~~~~~

     The package "async_hooks" wasn't found on the file system but is built into node.
     - Add the "nodejs_compat" compatibility flag to your project.

[xcfox]

Thank you for using GQLoom!

The Context of GQLoom makes use of async_hooks.

The greatest advantage is that this allows us to get the context during the validation step of zod and valibot.

Perhaps in the future, we can use Async Context to pass the Context. At this stage, node:async_hooks is the only method that allows us to implicitly get the context within an asynchronous function.

I have tested it on Node.js, Bun, and Deno, and AsyncLocalStorage works well.
For Cloudflare workers, you can enable only AsyncLocalStorage

[xcfox]

Thank you for your feedback, which made me realize that GQLoom currently can't run everywhere, such as Cloudflare Workers and browsers.

I realized that we can optionally enable AsyncLocalStorage through additional global middleware, thereby implicitly passing context.
If we explicitly pass context by default, it will result in a lot of template code. Although many frameworks such as tRPC, hono, and elysiajs all show passing parameters, implicitly passing context can greatly improve the development experience.

[PizzaConsole]

Awesome! Thanks! I can enable just AsyncLocalStorage in CF workers for now and that should work well enough!