-
Notifications
You must be signed in to change notification settings - Fork 49.9k
Open
Labels
Status: UnconfirmedA potential issue that we haven't yet confirmed as a bugA potential issue that we haven't yet confirmed as a bugType: Bug
Description
What kind of issue is this?
- React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- eslint-plugin-react-hooks (build issue installing or using the eslint plugin)
- react-compiler-healthcheck (build issue installing or using the healthcheck script)
Link to repro
Repro steps
Link to the code that reproduces this issue
https://github.com/promer94/incorrect-memo-fn-nextjs
To Reproduce
- build the application with
next build - start the application with
next start - click the numbers to see the console log
function Test1() {
const [expire, setExpire] = useState(5)
useEffect(() => {
const timer = setInterval(() => {
setExpire((prev) => prev - 1)
}, 1000)
if (expire === 0) {
clearInterval(timer)
}
return () => clearInterval(timer)
}, [expire])
const onClick = () => {
console.log('isExpired', isExpired)
}
const isExpired = expire === 0
return <div onClick={onClick} className="text-red-500">{expire}</div>
}The onclick function should be able to access the latest value of isExpired
How often does this bug happen?
Every time
What version of React are you using?
19.2.0
What version of React Compiler are you using?
1.0.0 would cause this bug
But ^19.1.0-rc.3 works correctly
Metadata
Metadata
Assignees
Labels
Status: UnconfirmedA potential issue that we haven't yet confirmed as a bugA potential issue that we haven't yet confirmed as a bugType: Bug