Times have changed...

A little over 3 years ago, I wrote my own ES5-compatible class library and partially documented it here. I used it in several applications where I work and some fairly large personal projects as well. Does it work? Oh, definitely. However, some of my co-workers complained about it being useless since everything we did with Class.js could be done without it. We’ve since rebuilt one of those applications without using Class.js. While it’s true that classes are unnecessary in an inherently procedural programming language like JavaScript, that doesn’t mean they should be summarily dismissed.

Even as I type this, TC39 is evaluating new proposals that add more class features to ES. Obviously, someone out there thinks JavaScript could benefit from a little more object orientation. I agree. To that end, I’m in the process of writing v3.0 of Class.js, complete with more documentation and cleaner code. Further, there will be 2 editions of Class.js:

• An ES5 compatible version (much like the original)
• A new ES6 version

The ES6 version will allow you to use both the old ES5 declaration syntax as well as a new syntax for ES6 that allows you to make use of the class keyword and all the syntax sugary goodness that comes along with it. The core design of the ES6 version is already ready and usable, but doesn’t have support for all the bells and whistles I threw into the ES5 version… yet. I want to complete the 3.0 ES5 version first as the API will likely change there as well.

I may have let this library sit still for 2 years, but it’s not dead. My goal here is to simply provide proper classical class definitions to ES while the TC39 board tries to catch up, and all without introducing the need for any compilation/translation. I hope you find this library useful.
By the way, the new version will also include a fairly extensive test script. TDD is a good thing. :)