Dennis Kats

I agree, `Record.groupBy` or any other `Array.prototype.groupByToX` feels redundant if there’s eventually an easy way to convert between Objects and Records or other collection types. I personally don’t have any...

I'm not sure if this has already been fixed, but I can't reproduce this issue anymore; both edges are present in the output.

> I am thinking that in cases where `start` and `end` can be specified, it may already be possible to retrieve the `edge` as well @goccy Perhaps I missed it,...

> For inline code, `AsyncContext.Variable` already exists — “LexicalScope.Variable”. Yes, the fully inline case is trivial and not something that we can't already do with lexically-scoped variables. However, in other...

> We had actually discussed using `using` bindings and allowing general mutability of the context [a while ago](https://matrixlogs.bakkot.com/TC39_Async_Context/2022-11-18), but decided against it. Thank you for the link to that discussion,...

> The styles have an error, you seem to combine inline styles from jsx and html This issue is specifically about ill-formed inline styles, i.e. the error in the example...

> Yeah, The issue was with inline style which was not correct. **Corrected:** `style={{ backgroundColor: "orange", fontSize: "40px", color: "blue" }}` this and behaviour is now consistent. As mentioned before,...

This issue still exists in React 19: https://codesandbox.io/p/devbox/styles-bug-v19-mfw2ct

I'm speculating here, but I think what's going on is that in the same render pass as when the portal container state is initialized, the "new" `{ __html: html}` object...

I've been running into this quite a bit recently, so after a lot of digging, I discovered that Next/Webpack may _sometimes_ (not sure based on what heuristic) bundle `jsdom` and...