mixin-pattern

To add reusable behavior to JavaScript classes without inheritance, use the mixin pattern to compose features across multiple types. You apply a mixin object containing the desired methods directly to a class prototype using Object.assign, injecting shared functionality without altering the existing hierarchy.

A mixin in TypeScript is a pattern that adds reusable behavior to objects or classes without inheritance. You should use it to inject cross-cutting capabilities like logging or validation into multiple types, promoting code reuse across diverse modules without introducing rigid class hierarchies.

The best way to compose behavior from multiple sources in JavaScript is using the mixin pattern. By applying mixin objects to class prototypes via Object.assign, you can augment objects with common functionality from various sources, avoiding duplication and bypassing traditional inheritance constraints.

Yes, a key limitation of using Object.assign for mixins in TypeScript is the risk of prototype pollution. When applying mixins to prototypes, you must take precautions to avoid polluting the base object, and the pattern advises evaluating when to prefer alternative composition patterns instead.

You should avoid mixins and use alternative composition patterns when your codebase requires strict type safety or when applying mixins via Object.assign introduces prototype pollution risks. If cross-cutting capabilities demand rigid structural contracts, alternative composition approaches are preferred over mixins.