MrBBot

Ooops! Didn't mean to push that to this branch.

Hey! 👋 These are my thoughts: 1. I think it makes sense to keep [workers-types](https://github.com/cloudflare/workers-types) TypeScript (as it always has been), putting the generated Rust in this repo. Although with...

How's this? 🙂 ``` miniflare --repl > await new HTMLRewriter().on("p", { element(e) { e.setInnerContent("new") } }).transform(new Response("old")).text() 'new' > const id = env.COUNTER.newUniqueId() undefined > const stub = env.COUNTER.get(id) undefined...

Yep! ```js import { Miniflare } from "miniflare"; const mf = new Miniflare(...); mf.startREPL(); ```

Like the flag name. I think you should drop `in future` from the warning message since we're recommending this now. ~~What do you think about merging `--persist-to` into `--persist`, kinda...

Could we hold off on merging this right now? I'm planning some changes to the persistence format in the next version of Miniflare, and keeping this flag experimental will avoid...

https://github.com/cloudflare/miniflare/pull/328 (and more broadly using IDs as opposed to binding names for KV/R2 storage). Also potentially switching everything over to SQLite too to fix issues like this https://github.com/cloudflare/miniflare/issues/167. I'm kinda...

Hey! 👋 An extension to microsoft/TypeScript#38511 sounds awesome! In the short term though, since I imagine this would require some pretty fundamental changes to TypeScript, it might be sensible to...

We'll want to have a discussion about how we initially launch this. I think whilst Miniflare 3 doesn't support all the same features as Miniflare 2, having an `--experimental-local` flag...

Hey! 👋 Apologies for the delayed reply. Yes, this is intentional. All custom IDs need to be declared at the top level so they're the same across calls. Don't worry...