pub.dev
AA
KKK
Authorization
J
V
HVVVHJJHHVHJJHJVHVH
R
II
CC
M
global.js, containing a {}
foo=1, and I want to hook that onto a global object so other files can use it, rather than laboriously having to pass it around to all functions. But the next request may send QS foo=2. Sounds like I'll be OK based on what you say. (But presumably in a non-serverless/Worker environment this would be problematic?)HICMMH
MglobalObject.localStorage wouldn't work? If so, using AsyncLocalStorage, am I right that it would look something like this, to store a global property for later reading downstream?CK
run takes the object you want to store, and then a callbackMKK // Fetch the resource using childWorker1
const childWorker1Response = await env.childWorker1.fetch(request.clone());
// Fully consume the response body of childWorker1
const childWorker1ResponseBody = await childWorker1Response.text();
// Fetch a resource using childWorker2, passing the response body of childWorker1 as the POST body
const childWorker2Response = await env.childWorker2.fetch(request.clone(), {
method: 'POST',
body: childWorker1ResponseBody
});global.jsfoo=1foo=2globalObject.localStorageimport { AsyncLocalStorage } from 'node:async_hooks';
const fooStore = new AsyncLocalStorage();
fooStore.run('bar'); //<-- running in some async middlewareimport { AsyncLocalStorage } from 'node:async_hooks';
const fooStore = new AsyncLocalStorage();
const fooVal = fooStore.getStore(); //"bar"runimport { AsyncLocalStorage } from "node:async_hooks";
const asyncLocalStorage = new AsyncLocalStorage();
async function doStuff() {
const { req, env, ctx } = asyncLocalStorage.getStore();
const obj = await env.KV.get("foo");
// ...
}
export default {
async fetch(req, env, ctx) {
return asyncLocalStorage.run({ req, env, ctx }, async () => {
await doStuff();
return new Response("Hello World!");
});
},
};