is this not fixed now with the requirement for domain lockdown if using workers?
is this not fixed now with the requirement for domain lockdown if using workers?

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.--remote flag with wrangler dev? I am not sure how it works with DO but that is the standard way for interacting with remote bindingsimport { 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...
}
}