How do you implement a standard paginated response envelope across all list endpoints in NestJS?

Q: How do you implement a standard paginated response envelope across all list endpoints in NestJS?

// Reusable paginated response wrapper export class PaginatedResponseDto { data: T[]; meta: { total: number; page: number; limit: number; totalPages: number; hasNextPage: boolean; hasPreviousPage: boolean; }; constructor(data: T[], total: number, page: number, limit: number) { this.data = data; this.meta = { total, page, limit, totalPages: Math.ceil(total / limit), hasNextPage: page * limit 1, }; } } // Service returns raw data + count async findAll(query: PaginationDto): Promise { return this.repo.findAndCount({ skip: query.skip, take: query.limit, }); } // Controller wraps in envelope @Get() async findAll(@Query() query: PaginationDto) { const [users, total] = await this.usersService.findAll(query); return new PaginatedResponseDto(users, total, query.page, query.limit); } Use a generic class PaginatedResponseDto so it works for any entity type. Include hasNextPage and hasPreviousPage so clients can render navigation without computing them. Services should return [items, total] tuple — let the controller build the envelope. totalPages = Math.ceil(total / limit) — always use ceiling division to include the last partial page. Consistent envelope shape across all list endpoints makes client SDK generation much simpler.

Difficulty: 5/10

pagination, response DTO, interceptors

Create a generic PaginatedResponseDto<T> class with a data array and a meta object containing total, page, limit, totalPages, hasNextPage, and hasPreviousPage. Services return a tuple of [items, total] using findAndCount. Controllers wrap the result in the envelope before returning.

Generic paginated response wrapper

Paginated envelope design guidelines:

1
Use a generic class PaginatedResponseDto<T> so it works for any entity type.
2

How do you implement a standard paginated response envelope across all list endpoints in NestJS?

Difficulty: 5/10

pagination, response DTO, interceptors

Create a generic PaginatedResponseDto<T> class with a data array and a meta object containing total, page, limit, totalPages, hasNextPage, and hasPreviousPage. Services return a tuple of [items, total] using findAndCount. Controllers wrap the result in the envelope before returning.

Generic paginated response wrapper

Paginated envelope design guidelines:

1
Use a generic class PaginatedResponseDto<T> so it works for any entity type.
2

How do you implement a standard paginated response envelope across all list endpoints in NestJS?

Create a generic PaginatedResponseDto<T> class with a data array and a meta object containing total, page, limit, totalPages, hasNextPage, and hasPreviousPage. Services return a tuple of [items, total] using findAndCount. Controllers wrap the result in the envelope before returning.

How do you implement a standard paginated response envelope across all list endpoints in NestJS?

Create a generic PaginatedResponseDto<T> class with a data array and a meta object containing total, page, limit, totalPages, hasNextPage, and hasPreviousPage. Services return a tuple of [items, total] using findAndCount. Controllers wrap the result in the envelope before returning.

Scenario Questions

Follow-up Questions