Hikari Hayashi

:wave: Hi, is there any eta for this feature? Our scroll restoration implementation heavily depends on it. Currently, we expose the whole history instance by implementing a custom router component,...

@diegohaz > [There's a lot of problems with the as prop](https://youtu.be/_kyv3tnQKfg?t=949), but I don't understand why that would be one, especially comparing to asChild: It's not only about git-diff stuff,...

@diegohaz > You don't need to merge the props yourself. Just pass them to TooltipAnchor, which will merge them internally. It's not type-safe either. ```ts ^ type error {(props) =>...

@diegohaz > I'm curious about this one. I remember doing a lot of experiments with React.cloneElement a while ago, and the incompatibility with React.memo was one of the biggest issues....

https://github.com/microsoft/TypeScript/issues/47118 ```ts import type { X } from "..."; import { type X } from "..."; ``` These two lines of code behave differently. Perhaps we should add a special...

You might want to have a try on my rewritten version, which has better performance and supports more features like variable fonts. It respects XDG dirs and could run as...

I'm glad to hear that! I don't have a strong opinion about naming. Both are acceptable to me.

https://github.com/typescript-eslint/typescript-eslint/issues/6338 I posted more details at the link above. I'm not sure which plugin this should be handled in. It's a mess. We may need two or more passes of...

@benoitgrelard You misunderstood what I meant. The native one and yours do not behave in the same way. For example, if I press the mouse at the center of the...

The third picture is just for reference. It's not related to this issue.