This is unpleasant, as correcting it might break the API. However, it should be addressed, as your module is very useful and will be used in the future.
You might do a deprecation warning in first and announce breaking changes once you bump to 1.0 remove the old name.
If you are interested, I could try to address this.
This is unpleasant, as correcting it might break the API. However, it should be addressed, as your module is very useful and will be used in the future.
You might do a deprecation warning in first and announce breaking changes once you bump to 1.0 remove the old name.
If you are interested, I could try to address this.