Re:Debugging Node.js in Production
by spamizbad on Friday December 04, 2015 @12:26PM
(#10677626)
Does that only work with something like babel? Because using the node 5.1 repl (and chrome console) you get:
[ Parent
| on HN ]
Re:Debugging Node.js in Production
by lewisl9029 on Friday December 04, 2015 @12:45PM
(#10677778)
The .name property doesn't seem to get set in Firefox either, but error stack traces do show the variable name as the function name. That's the important part IMO.
Have you tried it with a « var » instead as Chrome imposes certain restrictions on the new ES6 keywords?
I also checked the online Babel REPL and verified that it works fine.
var results in the same behavior in chrome (empty string for a function name)
It looks like babel does this little nicety for stack-trace readability.
I think Babel converts the code to ES5 and then execute the statements and therefore the function's name is printed to the console just like what you expect from good old ES5 code.
The most direct ES5 translation of
let func = () => {}
would be var func = function() {}
But even in that case, func.name is going to be "". var func = function func() {};
That's what the Babel REPL spits when you input the « let » statement.