How do you handle HATEOAS hypermedia links in NestJS REST responses?

Q: How do you handle HATEOAS hypermedia links in NestJS REST responses?

// Link type export interface HateoasLink { rel: string; href: string; method: 'GET' | 'POST' | 'PUT' | 'PATCH' | 'DELETE'; } // Resource wrapper export class HateoasResource { constructor( public readonly data: T, public readonly links: HateoasLink[], ) {} } // Link builder service @Injectable() export class LinkBuilderService { constructor(private configService: ConfigService) {} userLinks(userId: number): HateoasLink[] { const base = this.configService.get('API_URL'); return [ { rel: 'self', href: `${base}/users/${userId}`, method: 'GET' }, { rel: 'update', href: `${base}/users/${userId}`, method: 'PATCH' }, { rel: 'delete', href: `${base}/users/${userId}`, method: 'DELETE' }, { rel: 'posts', href: `${base}/users/${userId}/posts`, method: 'GET' }, ]; } } // Controller @Get(':id') async findOne(@Param('id', ParseIntPipe) id: number) { const user = await this.usersService.findOne(id); return new HateoasResource(user, this.linkBuilder.userLinks(id)); } HateoasResource is a generic wrapper — reuse it for every resource type. LinkBuilderService reads API_URL from config so link hrefs are environment-aware. Include self, update, delete, and key related-resource links at minimum. Use rel names from IANA link relation types for standardized semantics. HATEOAS adds response payload size — only implement it if your clients actually consume the links.

Difficulty: 6/10

link generation, interceptors, API contract

NestJS has no built-in HATEOAS support. Implement it by creating a HateoasResource<T> wrapper class and a LinkBuilderService that generates self, update, delete, and related-resource links. Controllers wrap the returned resource in the envelope before returning.

HATEOAS resource wrapper and link builder

HATEOAS implementation guidelines:

1
HateoasResource<T> is a generic wrapper — reuse it for every resource type.
2

How do you handle HATEOAS hypermedia links in NestJS REST responses?

Difficulty: 6/10

link generation, interceptors, API contract

NestJS has no built-in HATEOAS support. Implement it by creating a HateoasResource<T> wrapper class and a LinkBuilderService that generates self, update, delete, and related-resource links. Controllers wrap the returned resource in the envelope before returning.

HATEOAS resource wrapper and link builder

HATEOAS implementation guidelines:

1
HateoasResource<T> is a generic wrapper — reuse it for every resource type.
2

How do you handle HATEOAS hypermedia links in NestJS REST responses?

NestJS has no built-in HATEOAS support. Implement it by creating a HateoasResource<T> wrapper class and a LinkBuilderService that generates self, update, delete, and related-resource links. Controllers wrap the returned resource in the envelope before returning.

How do you handle HATEOAS hypermedia links in NestJS REST responses?

NestJS has no built-in HATEOAS support. Implement it by creating a HateoasResource<T> wrapper class and a LinkBuilderService that generates self, update, delete, and related-resource links. Controllers wrap the returned resource in the envelope before returning.

Scenario Questions

Follow-up Questions