Type checking is a breaking change

[arthot]

Hi!

The latest release (1.4.0) introduced a new functionality "added type checks to localizers". And it's definitely a breaking change, because it breaks code like

const total = 6;
i18n`Up to ${total} integrations`

So at least it should be a major version change. But in my opinion the project shouldn't have this functionality at all, because what is wrong with this code? It's pretty straightforward, you can always use .toString() implicitly, and after all it's a JavaScript, a language where you don't care about types and can spit on OOP 😄

[skolmer]

sorry, this was not intended. It should only check if you use type formatters for date and number formats.
It was intended to give a better debugging experience if you accidentally format a null/undefined or some other object as date or number like i18n`Current Date: ${null}:t(D)`

[skolmer]

sorry for the huge delay, I have so much work on my desk right now. happy to receive a pull request on this topic but also willing to work on this as soon as I find some free time.

[skolmer]

Fixed in 1.4.1