Jesse Kelly

Oops yep. Now it's public :) It's been a while since I wrote it lol. I decided to use `{ start: Date, duration: Duration }` instead of `{ start: Date,...

I have an implementation of this here if you're interested https://github.com/jessekelly881/effect-idb. I could probably create a PR to add this to the /platform package.

+1 would be helpful. My wrapper is basically just duct tape and hope lol.

Not sure if this is relevant to this issue or if I should create a separate one but being able to return an array from ```ts validators={{ onChange: ["err1", "err2"]...

I think Loggers should probably just be extended to have better support for `Error` types so that`.pipe(Effect.tapError(Effect.logError))` is sufficient.

That's what I mean, yeah. I think all loggers, logDebug, etc. should have better support for logging an instance of an `Error` type if that's what's provided to it. https://github.com/Effect-TS/effect/pull/2667

Relevant: https://github.com/Effect-TS/effect/issues/1589 (specifically, the overuse of `_tag`)

You should be able to replace hyper-ts with @effect/platform/HttpServer. I'm not aware of any routing solutions at the moment though. I'd love to see something like tanstack router on top...

As a side note, a port of zio-parser would probably be a better long-term/general solution. You could easily build a bi-directional param/query parser like fp-ts-routing using it. https://zio.dev/zio-parser/

Nice! I have my own "abandoned" port of zio-parse as well jajaja. https://github.com/jessekelly881/effect-parser I think your version is much closer to complete though. Why have you abandoned it? :P