Randy Topliffe

This will be supported in version 3 of the library.

@ardelato I submitted a PR for this #259 . Please verify that the contents of the PR would fix the issue. Thanks!

I've publish version 3.0.0-beta.5 to npm which includes this fix. Closing this issue.

Sorry that I didn't reply sooner. Glad you were able to find a solution that worked. However, I believe it's possible to avoid using `as AllMeasuresUnits` for each conversion by...

Using `exclude: ["nMi"]` is the correct way to handle this situation. The other solution is creating a custom measure that only contains the units needed.

So the issue isn't `toBest` but rather that there is an unexpected unit in the `imperial` system? If that's the case, could we close this issue and open a different...

Thanks for the question! I'm not sure I'm completely following the question. For your first code snippet, if `toBest()` is called without any arguments, it'll return `kl` with a value...

I'm open to cleaning up the systems/measures so that the sets are smaller. What approach do you think would work?

I'm in favour of creating a new system rather than modifying the existing system(s). Would you be willing to submit a PR for this?

The beta version supports [creating custom systems and units](https://github.com/convert-units/convert-units#custom-measures) as well as [extending existing measures](https://github.com/convert-units/convert-units#extending-existing-measures). However, if you're using the latest production version `2.3.4`, then this is not possible. >...