Rule proposal: `default-export-function-style`

Whether to prefer a default export as a named function or a const variable with an arrow function.

It should default to function style.

It should be auto-fixable.

Fail

// "unicorn/default-export-function-style": ["error", "function"]

const foo = () => {};
export default foo;

// "unicorn/default-export-function-style": ["error", "variable"]

export default function foo() {}

Pass

// "unicorn/default-export-function-style": ["error", "function"]

export default function foo() {}

// "unicorn/default-export-function-style": ["error", "variable"]

const foo = () => {};
export default foo;

---

Open question. What should happen to:

export default () => {};

Should we have a separate style for that or just disallow it for both function and variable style?

[sindresorhus]

I used to prefer non-inline so I could use arrow functions, but lately I’m preferring inline export default function foo () {}.

[fregante]

I use inline exports all the time. For defaults, I still prefer inline exports if they can be named inline (functions, classes)