func-names
UnreleasedConfiguration
Rule Details
A pattern that's becoming more common is to give function expressions names to aid in debugging. For example:
Adding the second bar in the above example is optional. If you leave off the function name then when the function throws an exception you are likely to get something similar to anonymous function in the stack trace. If you provide the optional name for a function expression then you will get the name of the function expression in the stack trace.
This rule can enforce or disallow the use of named function expressions.
Examples of incorrect code for this rule with the default "always" option:
Examples of correct code for this rule with the default "always" option:
Options
This rule has a string option:
"always"(default) requires function expressions to have a name."as-needed"requires function expressions to have a name, if the name isn't assigned automatically per the ECMAScript specification."never"disallows named function expressions, except in recursive functions, where a name is needed.
This rule has an object option:
"generators": "always" | "as-needed" | "never""always"require named generators."as-needed"require named generators if the name isn't assigned automatically per the ECMAScript specification."never"disallow named generators where possible.
When a value for generators is not provided the behavior for generator functions falls back to the base option.
Function expressions and function declarations in export default declarations must have a name under both "always" and "as-needed".
as-needed
ECMAScript 6 introduced a name property on all functions. The value of name is determined by evaluating the code around the function to see if a name can be inferred. For example, a function assigned to a variable will automatically have a name property equal to the name of the variable. The value of name is then used in stack traces for easier debugging.
Examples of incorrect code for this rule with the "as-needed" option:
Examples of correct code for this rule with the "as-needed" option:
never
Examples of incorrect code for this rule with the "never" option:
Examples of correct code for this rule with the "never" option:
generators
Examples of incorrect code for this rule with the "always", { "generators": "as-needed" } options:
Examples of correct code for this rule with the "always", { "generators": "as-needed" } options:
Examples of incorrect code for this rule with the "always", { "generators": "never" } options:
Examples of correct code for this rule with the "always", { "generators": "never" } options:
Examples of incorrect code for this rule with the "as-needed", { "generators": "never" } options:
Examples of correct code for this rule with the "as-needed", { "generators": "never" } options:
Examples of incorrect code for this rule with the "never", { "generators": "always" } options:
Examples of correct code for this rule with the "never", { "generators": "always" } options: