v2: Make a decision on casing for the default export

TinyColor vs tinycolor:

The lowercase variation is the v1 API, so keeping that would make migration easier. The camel cased variation is more typical for class naming.

This mostly just affects UMD users and how we write it in documentation if we go with something like https://github.com/bgrins/TinyColor/pull/181 where we do a default export for node.

[bgrins]

Yeah, I’ve gone back and forth. I’m also leaning lowercase for now since that’ll make migration from v1 to v2 seamless for most cases. I actually wish it was camel case to match the project name, but I think there’s value in uncoupling that potential name change from getting v2 shipped.

[scttcper]

i think we should keep it showing new because it is still a class.

I do think some of the readme examples no longer work?

import { fromRatio } from 'tinycolor2';

might not be working anymore.