Nathan Bubna

Oooh, that is a fascinating idea. Of course, i can guarantee i'd take the PR without seeing it, but i'm definitely open to it. It's a case situation i've run...

A PR for this would be great!

I'm not very familiar with Rollup, but if it seems simple enough, i'm willing to try it out.

And yes, changing the source to ESM makes sense, as long as we still produce UMD for compatibility.

I will! Have patience and get some sleep. ;)

I'm pondering making this a major version bump. Then i can remove squish, Component support, possibly even trim some fat by using ES6 features, and maybe drop Grunt for Rollup...

I'm also thinking of getting rid of toCase, as i don't believe it gets much use (i don't use) and don't like modifying String.prototype. Since you are more experienced with...

Moving to jest is an excellent idea. As for the dynamic case creation, the idea is that people would export\import the ```Case``` object if they wish to add their own...

It should export Case as the default exports and the functions as named exports. That should be fine for tree-shaking. I'm off to bed and have a busy weekend. I...

Well, that's not a very helpful UMD impl. Since we're talking about bumping major version anyway, i think we may have to give up the Case[customType] part of the API...