@tank/design-patterns

For extensible API request processing, the middleware pattern is often the best JavaScript design pattern, allowing you to chain handlers flexibly. Alternatively, a command pipeline or repository-backed architecture might suit your needs depending on coupling and data access requirements.

To choose the right TypeScript design pattern for object creation, compare creational patterns like Factory against your object complexity. Use Factory for variable object types, but avoid the Builder pattern for trivial objects to prevent overengineering.

You should not use the Singleton pattern for dependency sharing in TypeScript when it creates hidden coupling and complicates testing. Recognizing this as an anti-pattern helps reduce coupling and structure code more clearly without unnecessary global state.

To implement the Observer pattern in TypeScript, define a notification interface for subscribers and let subjects broadcast changes. This Skill provides practical TypeScript examples and real-world implementation guidance for behavioral coordination scenarios like this.

Choosing between middleware and repository patterns in JS depends on your architecture: middleware handles sequential request transformations, while the repository pattern abstracts data persistence. Compare structural and modern JS/TS patterns to find the best fit.