elderapo

Any preference between object (or maybe other keys?) vs tuple approach?

It's been 2 years, `async_hooks` are still experimental but maybe we could get this feature behind the `experimental` flag?

I suggest api similar to [genql](https://genql.vercel.app/docs/usage/selecting-fields#querying-all-fields)'s one: ```ts import { everything } from "./zeus-graphql" Gql.query({ animals:{ ...everything, age: false, } }) ```

Haven't had much experience with rust but will try. Thinking of adding typescript definitions for better DX aswell.

> Hello, > It returns the following error message: > Uncaught Error: Cannot find module 'dns' > webpackMissingModule dns.js:16 > js dns.js:16 Don't think this error is relevant to this...

I believe these should return channels or utilize some API that allows chaining. ```ts const numbersChannel = new Channel(() => {}); const oddNumbersChannel = filterChannel(numbersChannel, item => item % 2...

Actually, now that I think about this “no differences between async generators and channels” rule it does not make much sense in a sense of extending possibilities of async generators....

Async generators do not have utilities for manipulating them ex.: filtering, mapping, combining/merging, etc. I believe filtering/mapping can be easily done but more complicated scenarios of merging are much easier...

I am pretty sure it worked fine in the past so probably https://explorers.api.live.ledger.com/blockchain/v3/bch/addresses/bitcoincash:qz00gq5knkfc9m4ejepcawzgl2fxzznvquc5cnfnkf/transactions just used to not include OP_RETURN outpoints.

Can this get addressed? I am not able to use my wallet because of that.