Code Organization with Classes and Modules

Key Insight

JavaScript employs classes and modules as primary patterns for organizing code by grouping related data and behaviors into logical units, facilitating cooperation among them. Classes define custom data structures, encapsulating data (e.g., 'this.text' in 'Page') and methods (e.g., 'print()'). These definitions are not concrete values but serve as blueprints, requiring instantiation with the 'new' keyword to create usable instances, such as 'var mathNotes = new Notebook();'. Class inheritance allows child classes, like 'Book' and 'BlogPost' extending 'Publication', to reuse and specialize parent behaviors through 'super()' calls and method overriding, demonstrating polymorphism where inherited and overridden methods with the same name coexist.

Classic modules, a pattern used widely before native JS module syntax, organize code using outer factory functions that return an 'instance' with a public API. Crucially, this pattern enables explicit control over public and private members: methods and data not explicitly returned remain hidden within the module's scope. Unlike classes, methods and data are accessed as scoped identifier variables without a 'this.' prefix, and modules are instantiated by simply calling their factory function without 'new'. Variations like AMD, UMD, and CommonJS adhere to these core principles, all aimed at creating encapsulated, reusable code units.

ES Modules (ESM), introduced in ES6, offer native file-based modularity, treating each file as a distinct module. Public interfaces are explicitly defined using the 'export' keyword, while unexported elements remain private. A key difference is that ESMs are singletons; importing a module ('import { create as createPub } from "publication.js";') simply accesses its single, program-wide instance rather than creating new ones. If multiple instances are required, an ESM can export a classic module-style factory function. ESMs support flexible integration, allowing for renaming imports (e.g., 'create as newBlogPost') and combining with classic module patterns to address diverse architectural needs.