Repository navigation
Do not assign const variable in error case #20056
Description
Activity
FWIW, this is also valid for Chrome and Firefox DevTools Console:
@TimothyGu for me it is not about spec compliance but about a better way to handle it in the repl. So this issue should be about evaluating to diverge from the spec. I am not sure about the current implementation details and if that is even possible.
Mime keeps const unable to be reassigned, but separate inputs can rebind the variable name to a new binding.
When using the repl and e.g., writing:
const foo = bar()whilebaris undefined is going to cause an error. So far so good. The problem is thatfoois now assigned even though it would be super nice if that would not be the case due to the error while assigning the variable.I tried to see how to fix this on my own but it is somewhere in runInContext if I am not mistaken and I have never looked at that part before.
@nodejs/vm @nodejs/repl