I am using neon, do you know how I can set that up?
I am using neon, do you know how I can set that up?
context.waitUntil on the global to improve it's ergonomics or does it need to be coupled with a specific request? e.g.
ctx or waitUntil / env into various modules, creating a lot of boilerplate for call sites
itty-durableitty-durable is not needed, it just makes the code way shorter).fetch on a Service Worker binding do anything with the cache-control header?
wrangler dev), that goes to Worker #2 in remote mode (wrangler dev --remote)?pages dev. Even if it is planned to add the functionality in future, right now the instruction is rather confusing than helpful.context.waitUntil// worker.js
import { myFetch } from './my-fetch';
export default {
async fetch(request, env, context) {
global.waitUntil = context.waitUntil;
return fetch(request);
},
};
// my-fetch.js
export const fetch = async (request) => {
const response = await fetch(request);
response.headers.append("Cache-Control", "s-maxage=10");
waitUntil(caches.default.put(request, response.clone()));
return response;
}AsyncLocalStorageitty-durableitty-durable.fetchcache-controlpages devimport { createDurable } from "itty-durable";
export class Scheduler extends createDurable({ autoPersist: true }) {
constructor(state, env) {
super(state, env);
}
create(name, doEverySeconds = 30) {
this.name = name;
this.doEverySeconds = doEverySeconds;
this.setAlarm(Date.now());
}
async alarm() {
console.log(`Doing ${this.name}...`);
this.setAlarm(Date.now() + this.doEverySeconds * 1000);
// do the thing...
}
}