To confirm that I wasn't requiring the class elsewhere and it somehow being in scope, I went to the other module or two that were requiring esri/config and removed the reference. Surely, esriConfig would be undefined now, right? Nope, the default properties exist.
I'm using 3.14 and AMDs. So, it would seem that I would have to require it.
Should esriConfig be required before setting/getting properties in a custom module?
How is esriConfig global?
Is esriConfig supposed to be global?
Should it be global?
Am I doing it wrong?
Why does the documentation imply that only legacy code requires requiring of esri/config?
Are there any other global classes?