Dan Abramov made a convincing (to me) argument for using the named function style. Stack traces will give a more immediately useful information. It’s not a deal breaker, so in a work context I would tend towards following the existing style as some people are really attached to anonymous functions

Not a stupid question at all.

Other than the syntax, there is a very important functional difference between the two: function definitions are hoisted, consts are not. What this means in practice is that you can use a function you define later in the file if it’s defined using the function f() { ... } syntax, but const f = () => { ... } functions can only be used after their definitions.

function f() { g() } // OK
function g() {}

const f = () => { g() } // Error
const g = () => {}

Personally, I like breaking up React components into smaller helper subcomponents and use them in a main component. I only export the main component, the helpers are private to the module. For better readability, I like the main component to be at the top of the file and then put the helpers in decreasing order of complexity. This style is only possible with classic function definitions, using consts forces you to use bottom-up instead of top-down order.

Arrows are cooler so

Arrow, definitely arrow, because they look cool.

No diff with typescript, tho declared is more flexible because you can overload it. Declared (classic) functions are hoisted and can be used prior to their declaration. Not sure on perf differences