11 ms·
Does that only work with something like babel? Because using the node 5.1 repl (and chrome console) you get: > let func = () => {} undefined > func
by spamizbad 11y ago
Does that only work with something like babel? Because using the node 5.1 repl (and chrome console) you get:
> let func = () => {}
undefined
> func.name
''
> function longfunc() {}
undefined
> longfunc.name
'longfunc'
- Scarbutt 11y agosadly, babel is taken for granted these days.
- lewisl9029 11y agoThe .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.
- gotchange 11y agoHave 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.
- spamizbad 11y agovar 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.
- gotchange 11y agoI 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.