globalThis.als = new AsyncLocalStorage would work
globalThis.als = new AsyncLocalStorage
K
M
globalThis
HHMM
importglobalThis.als = new AsyncLocalStorage(); seems to work tooK
K
Kd7d6d2f4 isn't overwritten by 987f4e92 like it would be if you just stored them on globalThisglobalThisglobalThisfoo=1 and request 2 hooking foo=2 will be preserved within the scope of their respective requests, using ALS?K
K
magic MglobalThis.foo set in one file and read in another file risks mutation/leakage from other requestsglobalThis.als, where als is a store with {foo: <something>} set on it, avoids that problemKK
KMKfetchals.run(..., async () => { ... }); inside your fetchals keeps track of what context it was called in (this specific call of the fetchals.getStore(), those modules were called within that run callback - it's tied to that invocation of the fetchals.getStore() within the fetchrun callback, it'd be undefinedrun stores what you pass to it in a context that's only available to the callback, and other calls to run by other requests doesn't mutate our store since als knows that is a separate invocation of the fetch
A
U
wrangler dev --remoteAUUA
!
I!HHM
als aren't susceptible to mutation from other requests, but other things e.g. on globalThis.myObj are. I never really "got" that until now. Appreciate the explanation!
P
Mnode:async_hooks?platform is not a documented config property that I can seecompatibility_flags = [ "nodejs_als" ] in the TOML but that raises the error _"No such compatibility flag: nodejsals"HPPPM
fs. Filesystem doesn't really make sense as a concept when using Workers. I haven't had any other issues using node modules.P
FM
D
Fimport { als } from ".";globalThis.als = new AsyncLocalStorage();d7d6d2f4987f4e92foo=1foo=2globalThis.fooglobalThis.alsalsalsalsals{foo: <something>}als.run(..., async () => { ... });als.getStore()als.getStore()runrunrunrunwrangler dev --remoteglobalThis.myObjnode:async_hooksplatformcompatibility_flags = [ "nodejs_als" ]fsfs