Sebastian "Sebbie" Silbermann
Sebastian "Sebbie" Silbermann
In StrictMode, `useEffect` functions are executed twice. This catches race conditions e.g. when `num` changes but the first Promise takes longer than the second Promise. You can avoid this by...
> what I'm also confused about is that why the updater function has been executed twice even though the useEffect only executed once without using strict mode. Updater functions may...
PR has merge conflicts. Can you rebase this onto latest `main`?
> I saw that @testing-library/jest-dom is also using chalk but only in a test. However, it is listed as dependency. Maybe we can move it to devDependencies and also replace...
`Slider` is a controlled component. This would mean that we should only allow `onInput` but warn against `onChange`. That means we just drop `onDrag*`. I think this is what people...
@dpren > As a library user, I always assume the DOM spec first before checking how react does things. Preferably but with React Fire we won't have `onChange` anyway. I...
So this is still deduping double logs from StrictMode? We can't land this. We learned that already that people do not want to hide logs from StrictMode double invocation by...
This is documented behavior: https://react.dev/reference/react-dom/components/title We should have a warning though.
Thanks for the report. Can you reduce that to a smaller example? Try to remove as much code as possible until the issue no longer reproduces.
The error message being unhelpful is our bug though. Can you share a minimal reproduction?