Adrien

hmm it seems though that in a "real" setup not all queries are logged... Not sure yet where the issue is :thinking:

we overwrite `handler.onquery`, but the handler is shared among many queries

I updated the patch above to copy the `onquery` handler on each `Query` instance, that query can then do whatever it wants with it.

There's actually a difference between using `forEach` and `entries` with sparse arrays: forEach will skip them, while entries will include them: ``` > const a = []; undefined > a[0]...

Hi, thanks for opening the issue! I guess that ideally, we should take the official Go AWS SDK into use, and use its request signing facilities... I'll try to have...

Same issue here, running Remix 2.3.1

OK I found the issue in my case: the Promise was nested inside the loader data. Looking at [the code](https://github.com/kiliman/remix-typedjson/commit/4c2d41de1ed5242b0fbc08f559458c0a428be19e#diff-1d888e71b15aa4550c13c48d3cdbd173e8daa8e70d53b9711491e32e4b1c106bR60), it seems that `typeddefer` only looks at top level properties.

Here are the relevant entries in `deno.lock`: ``` "https://esm.sh/[email protected]": "18fd758068f2d70564c790791073f22fa6d63922f08e8c7ba5554cf8b8a52470", "https://esm.sh/v120/[email protected]/deno/dcmjs.mjs": "63d7d710335da06c486b60085b0116324b7831a1a3ab542db3acced26faba222" ```

I was bitten by the same issue after changing my Dragonfly command line so that the admin port would only listen on `127.0.0.1` 😅 I've left the port open for...

Yup, I'm aware that you can have many values, but thanks for clarifying :) My point was more that, with the current API I believe there's no way to distinguish...