`5.2.0` introduces a breaking change

The 5.2.0 release accidentally introduced a breaking change when using CommonJS require().

5.1.1:

> require('memoize-one')
[Function: memoizeOne]

5.2.0:

> require('memoize-one')
{ default: [Function: memoizeOne], memoizeOne: [Function: memoizeOne] }

[alexreardon]

Okay, based on feedback I think I have acted correctly and followed SemVer. I will close this issue for now.

This whole issue was super stressful! The last thing I want to do is cause anybody friction in their consumption.

Thanks everybody for your input

[Andarist]

Yep, my stance on this is very similar to @jesstelford and @ehmicky . Stuff like this happens from time to time - we need to be pragmatic here, the current versions are OK - and whoever has adjusted their code already with the named export in mind… can just revert their changes (there shouldn’t be that many of such people anyway). Semver is just a human-based guideline anyway - somebody’s bug fix is always somebody’s breaking chance if we consider software at scale so it’s not worth stressing things like this too much.