Ban the use of default exports?

Named exports are superior to default exports in a few ways:

It’s easier to find all uses of a function / property through the project, easier to rename across project, less confusion around names / mental load.

Adopting named exports will pay dividends down the road as the number of modules and exported properties are added.

More info: https://humanwhocodes.com/blog/2019/01/stop-using-default-exports-javascript-module/

// instead of this export / import
export default function AddChild (parent: IParent, child: IGameObject | IGameObject[])
import AddChild from '../src/gameobjects/container/AddChild';`

// I suggest we use named exports
export function AddChild (parent: IParent, child: IGameObject | IGameObject[])
import { AddChild } from '../src/gameobjects/container/AddChild';

// it's more consistent with importing from an index, ex:
import { AddChild, SetParent } from '../src/gameobjects/container';

Having 1 way of importing things is better than having 2 ways of importing things imo.

[bhgsbatista]

If nothing else, you made me very happy 😄

[photonstorm]

I’ve updated the whole codebase to use named exports. It took quite a while, this had better be worth it 😃