Which docs were those?

> When using the nodejs_compat compatibility flag in local development, you must use wrangler dev --experimental-local instead of wrangler dev --local. --experimental-local will soon become the default for local development in Wrangler.

so yeah it was pretty clear about it 🤣

Hm...

Now I'm wondering if it will work...

it is working now, but the my first attempt to store a value and retrieve it didn't work

Yeah, then you might need

--experimental-local

after all. What OS are you on?

I'm pretty confident it is my mistake, because I've never used AsyncLocalStorage before it is not clear how to simply store

foo

and then access it in another file

Windows

don't judge me

That might be why.

workerd

was, until recently Unix(more like Ubuntu) only, and while a PR to add support to Windows was recently merged, there are probably still some issues to be ironed out...

oh it looks like I need to wrap all my code inside

run

to access the storage

ah I understand the docs a bit more now I think

this is more complex than I was hoping, and I'm not sure if it will let me access a global variable from any file

wouldn't I still need to pass around the

asyncLocalStorage

instance?

You shouldn't need to

wait, the storage isn't local to the request 😦

Isn't that the whole point?

The reason why they got rid of the whole "global bindings" thing was because it was slow, and required a full reboot of the isolate to use new bindings

I guess I didn't specify explicitly, but no because Sentry has tons of configuration that is done per request

I'm wanting request-local storage I can easily access

Then I think you just have to pass it around manually

but anyways when I do:

const asyncLocalStorage = new AsyncLocalStorage();
await asyncLocalStorage.getStore(); // undefined

from an inner function (like a route), this just returns undefined. so I think you do need to pass around the original

asyncLocalStorage

instance

or maybe I could expose a function to return it

oh yeah this works:

js
const asyncLocalStorage = new AsyncLocalStorage();
export const getLocalStorage = () => asyncLocalStorage.getStore();

let idSeq = 0;

export default {
  async fetch(request, env, context) {
    return asyncLocalStorage.run(idSeq++, async () => {
       ...

second file:

js
import { getLocalStorage } from "../index";

await getLocalStorage();

not 100% sure on a use case though tbh, but could come in handy

The exact error is "Response closed due to connection limit" ... got that wrong.

Are you reading the body of the responses?

If not, they will stay open and contribute to the limit.