Have you actually seen this in real code?
Anders Ringqvist

There are a few internal libraries at my company that have made this mistake.

We are also considering moving away from default exports, but the counter argument always seems to be that in many cases you end up with repetition.

import { foo } from ‘./foo’

I’m not sure it makes a difference at all to refactoring, since you can name a default export anything and only the file path matters.

Like what you read? Give Evan Scott a round of applause.

From a quick cheer to a standing ovation, clap to show how much you enjoyed this story.