Brian Kim

Sorry for the lack of response. Doing a little bit of housekeeping. No hook-like API is planned, but you can emulate it yourself using context methods / generators.

Added in 0.5.0

@rubiesonthesky This appears to have been fixed since 4.2.2. Thanks.

Thanks for the opening this issue! This appears to be a bug insofar as any push which is done against an open buffer should resolve to `undefined`. It appears that,...

I’m in agreement about web streams. I still think the constructor with the double object arguments are a bit awkward, but you can’t beat built ins. I think they’re also...

Gentle reminder that we’re looking for reproductions. I greatly prioritize any issue which I can run, and I got a lot of issues on my plate at the moment. If...

Also seeing this bug. ``` System: OS: macOS 11.2.2 CPU: (8) arm64 Apple M1 Binaries: Node: 14.6.0 npm: 7.19.1 npmPackages: jest: ^27.0.4 ```

@MichalLytek I use it and have been stuck on 26 for a while now. It’s mildly disturbing how little attention this has gotten though.

@canadaduane The `key` and `ref` props have been removed from props, a tradition started by React. On the use-case side of actually being able to access `key` and `ref` in...

>Personally, I would use two sets like so (since we already have $-prefixed props): > - keep $key, $ref: assign the key and ref, but do not pass as props...