菜单
Maps internal AppError hierarchy to HTTP responses through a single global exception filter and a Result-to-HttpException helper. Use when adding new error types, fixing inconsistent error responses, or removing scattered try/catch in controllers.
| name | handling-nestjs-exceptions |
| description | Maps internal AppError hierarchy to HTTP responses through a single global exception filter and a Result-to-HttpException helper. Use when adding new error types, fixing inconsistent error responses, or removing scattered try/catch in controllers. |
| license | MIT |
AppError subclassesResult<T,E> mapped to HTTP via helper, not scattered try/catchAppError with statusCodetry/catch in controllers; let exceptions bubble to filter@Catch(AppError)
export class AppExceptionFilter implements ExceptionFilter {
catch(exception: AppError, host: ArgumentsHost) {
const ctx = host.switchToHttp();
const res = ctx.getResponse<Response>();
res.status(exception.statusCode || 400).json({
success: false,
error: { code: exception.code, message: exception.message },
});
}
}
export function resultToHttp<T>(result: Result<T, AppError>): T {
if (!result.success) throw result.error; // Let filter handle
return result.value;
}
// Controller: no try/catch, use helper
@Get(':id')
async findOne(@Param('id') id: string): Promise<ApiResponse<User>> {
const result = await this.useCase.execute(id);
return toApiResponse(result); // Helper handles mapping
}
// ❌ Scattered try/catch in controllers
try { ... } catch (e) { return res.status(400).json({ error: e.message }); }
AppErrorResult<T,E> mapped via helperstatusCodeSee reference/exception-patterns.md for full patterns.
Defines the rule base every skill in this pack obeys: file layout, frontmatter, vocabulary, OOP/typing/decoupling axioms, and anti-patterns. Load FIRST before authoring or applying any other skill in this pack.
Designs NestJS feature modules with clean dependency boundaries, provider scopes, and dynamic modules. Use when adding a new feature module, splitting a monolithic AppModule, or fixing tangled imports between modules.
Builds thin NestJS controllers that parse input, invoke a single use case, and map the Result to ApiResponse<T>. Use when adding HTTP endpoints, refactoring fat controllers, or applying API versioning.
Prepares a NestJS service for production: graceful shutdown, health/readiness, structured logs, config, Dockerfile, CI gates, and rollout safety. Use when promoting a service to staging/production or auditing readiness.
Designs NestJS application services as use-case classes that orchestrate domain logic and ports without leaking the framework. Use when creating new use cases, refactoring services that mix HTTP/DB/domain, or moving from anemic services to OOP.
Implements the Repository pattern with TypeORM in NestJS so domain entities stay framework-free, ORM models live in infrastructure, and transactions are explicit. Use when adding persistence, refactoring leaky ORM usage, or handling transactions across aggregates.