Coding standards address various levels of questions. At a high level, you can choose to use a module pattern or a commenting style. At the lowest level, you can choose between using spaces and tabs or single and double quotes. While it is definitely important to address the high level issues to ensure consistency, setting standards for the low level and what may seem to be insignificant issues will save many headaches down the road.
Tools such as Github and Gitlab allow other users to leave comments and approve or reject commits and pull requests. During these meetings, you can review the code by walking through each pull request or commit. Or you can focus on what each developer has been working on since the last meeting. Code reviews are a great checkpoint. Many times, simply having other people review your code will allow a developer to catch potential issues before they are pushed out to users.
- CommonJS and RequireJS are other common module systems. CommonJS modules are used primarily in Node.JS applications. But they can also be used in browser applications through build tools such as Browserify. RequireJS is an early module system that is supported by some of the newest browsers. It uses the Asynchronous Module Definition (AMD) pattern to load dependencies..
The module pattern you choose for your application may be influenced by other choices. These include server languages and frameworks. If you are developing a Node application or a UI with a Node backend, it may be helpful to use CommonJS to maintain consistency between back and front ends. But if you are developing a TypeScript or Angular2 application, SystemJS may make more sense as that is the default module loader for both. Regardless of the module loader chosen, it is important to divide a large application into smaller modules of functionality as you follow the single responsibility design pattern.