Lifting a comment from #165

This is really hurting downstream compatibility leading to the usual wac-a-mole of getting dependencies to work together (this being one of the dependencies that's used almost everywhere in our little ecosystem). Since it was a breaking change this would have been a good reason to /v3. In lieu of that, can we have these back please as aliases marked as deprecated?

We have a hard enough time with compatibility as these things move forward and break, can we not make our lives any harder for simple things that have no good reason to break?