This feels janky to me. I think I'd rather have the Biome warning suppression, because it feels more "honest" about this not being a properly-defined synchronization effect

I think there's a "deeper" fix we can reach for to remove the effect entirely. I just don't know if it makes to do it now. ForBuildLogsDrawer at least, we could:

1. Update the logs component to accept a forwarded ref, and get rid of the old ref + layout logic
2. Define the ref inBuildLogsDrawer
3. UpdateuseWatchVersionLogs to accept anonMessage callback that fires each time a new message comes in
4. HaveBuildLogsDrawer pass the ref down to the logs component, and also pass anonMessage callback to the hook that handles the scrolling behavior

The big problem right now is that ideally these scrolls would be handled in an event handler, but the state isn't defined in a way that gives you a state setter function that's easy to wrap

Plus, there's five components currently using this

one day we'll get signals...

I mean, the problem with the React team is that they legitimately think that they don't need signals, and that the compiler is going to solve all of React's problems (which it probably won't). They've turned down a few signal proposals already

it'll take a while, but I'm pretty sure the web platform will get signals soon, and then the react team will be forced to reckon with them.

also preact even jumped the gun and added signals. angular has signals now. the tide is turning!