clean-architecture-ts

What problem does it solve?

Remix apps can accumulate complex logic inside loaders and actions, creating bloated routes that are hard to test and maintain. This guide promotes a layered architecture to separate concerns across Web Layer, Service Layer, and Repository Layer.

Core Features & Use Cases

• Separation of concerns across the Web Layer (loaders/actions), the Service Layer (business rules), and the Repository Layer (data access).
• Encourages dependency injection, testability, and clearer boundaries.
• Use case: refactor a route to move business logic into a Service and data access into a Repository.

Quick Start

Refactor a Remix route by extracting business rules into a Service and data access into a Repository, then wire the Service from loaders and actions.