You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Destructuring Assignment Parse Error - works in Chrome & Safari but not Node #11480
Not regularly. I think the process for these cases is to look for which commit(s) in V8 fixed the problem, see if is feasible to apply them to the old V8 branch and then cherry-pick them back.
Activity
shanebdavis commentedon Feb 21, 2017
It also works in: Babel 6.23.1
addaleax commentedon Feb 21, 2017
@shanebdavis Fwiw, it also works in Node 7.x, which means it was likely fixed during a V8 upgrade.
/cc @nodejs/v8
shanebdavis commentedon Feb 21, 2017
@addaleax Thanks! That makes sense. I was wondering why it worked in Chrome and not Node.
Is 6.x scheduled to get V8 updates?
addaleax commentedon Feb 21, 2017
Not regularly. I think the process for these cases is to look for which commit(s) in V8 fixed the problem, see if is feasible to apply them to the old V8 branch and then cherry-pick them back.
Fishrock123 commentedon Feb 21, 2017
Eh I suppose we can keep the label on it if backporting is at all viable.
targos commentedon Feb 21, 2017
I Identified v8/v8@dfb8d33 as the commit that fixes it using
git bisect.targos commentedon Feb 21, 2017
#11483
deps: backport dfb8d33 from V8 upstream
test: add regression test for V8 parse error
targos commentedon Mar 8, 2017
Fixed by d0e934f
deps: backport dfb8d33 from V8 upstream
test: add regression test for V8 parse error