Repository navigation
repl: variables becoming undefined #59798
Description
Version
24.x
Platform
All
Subsystem
repl
What steps will reproduce the bug?
jasnell@FF4V42X6YN ~ % nvm use 22
Now using node v22.19.0 (npm v10.9.3)
jasnell@FF4V42X6YN ~ % node
Welcome to Node.js v22.19.0.
Type ".help" for more information.
> m = {}
{}
> delete m.n
true
> m
{}
> .exit
jasnell@FF4V42X6YN ~ % nvm use 24
Now using node v24.7.0 (npm v11.5.1)
jasnell@FF4V42X6YN ~ % node
Welcome to Node.js v24.7.0.
Type ".help" for more information.
> m = {}
{}
> delete m.n
Uncaught ReferenceError: m is not defined
> m
Uncaught ReferenceError: m is not defined
>
How often does it reproduce? Is there a required condition?
Always
What is the expected behavior? Why is that the expected behavior?
m should not be ReferenceError
What do you see instead?
See the repro
Additional information
No response
Activity
targos commentedon Sep 7, 2025
This is possibly fixed by #59774
BridgeAR commentedon Sep 11, 2025
This is fixed by now (I just verified that).