It's early days. Thanks for pointing this out. Has now been fixed.

Haha I can't believe how spiteful this place is. I don't understand why it's so impossible for you guys to just ignore something you think should be ignored. Or do you have to make sure that everyone who wants to make up their own mind should ignore it too.

Just incase you haven't got it already... I had a need for an ECMA5 targeted toolkit for my Node.JS development that provided all the useful goodness Ruby, Python and PHP had been given over the years which JS had never really had a need for (living mainly in the cave of the browser). A simple comparison:

Underscore.JS:
_.map([1,2,3], function(a, b) { return a * b });

JS Toolkit:
[1,2,3].map(function(a, b) { return a * b });

I didn't care about intruding the object namespace because ECMA5 introduced property descriptors which allowed me to make any extension methods non-enumerable and essentially no different to how other native methods were implemented. So with that in mind I created something that made more sense to me than underscore.js, as why should I have to use an underscore at all? Trust me if there were something that suited my needs I would have used and contributed to that instead.

I'm surprised it managed to find it's way here so quickly. It is still an immature project but perfectly useable with a few small bugs i'm working my hardest to iron out. It wasn't published by me so clearly there was someone who thought it worth showing to the world. I'm grateful to that person's support and I will do my best to see it through.