Matt Mulder
Matt Mulder
It still reproduces with `next@canary`. No errors or warnings in the terminal. By "refresh", I mean a Cmd+R. Something I just discovered is that it reproduces in Node.js 18 but...
I see this breaking change in the Node.js 18 release notes. I wonder if it could be related?: > (SEMVER-MAJOR) stream: remove thenable support (Robert Nagy) [#40773](https://github.com/nodejs/node/pull/40773)
FWIW we worked around this by walking the dependency tree in our `yarn.lock` to detect any dependency chains that flowed through an NPM dependency, and using that to augment the...
This is a feature request, and I think its still worth consideration.
Let's implement this, and get rid of the tagRef prop in a v2 release.
consider using ref: https://react.dev/blog/2024/04/25/react-19#ref-as-a-prop
Thanks, but I think this misses the point. This bug report is about React failing to batch a render caused by an immediate state change - your fix only removes...
A workaround that does work is to wrap the state change with `flushSync`, like: ```jsx React.useLayoutEffect(() => { requestAnimationFrame(() => { ReactDOM.flushSync(() => { setMessage("Ready"); }); }); }); ``` But...