Module Pattern

Table of Contents

• When to Use
• When NOT to Use
• Instructions
• Details
• Source

As your application and codebase grow, it becomes increasingly important to keep your code maintainable and separated. The module pattern allows you to split up your code into smaller, reusable pieces.

Besides being able to split your code into smaller reusable pieces, modules allow you to keep certain values within your file private. Declarations within a module are scoped (encapsulated) to that module, by default. If we don't explicitly export a certain value, that value is not available outside that module. This reduces the risk of name collisions for values declared in other parts of your codebase, since the values are not available on the global scope.

When to Use

• Use this when you need to organize code into maintainable, encapsulated units
• This is helpful when you want to keep certain values private to a module and avoid global scope pollution
• Use this to enable tree-shaking and reduce bundle sizes