Configuration des passerelles
Configurez les passerelles WebSocket dans NestJS et gérez les événements de connexion, les messages et les salles.
Configuration des passerelles est une leçon Node.js Backend Development Bootcamp gratuite sur CoddyKit. Ceci est la leçon 4 sur 6. Tu peux lire la leçon complète ci-dessous gratuitement — puis la pratiquer en direct dans le navigateur avec un éditeur de code intégré et un tuteur IA 24/7. Elle fait partie du parcours d'apprentissage Node.js Backend Development Bootcamp, et ta progression se synchronise sur le web et l'application CoddyKit. Le cours Node.js Backend Development Bootcamp comprend 6 leçons au total.
Certaines parties de cette leçon n'ont pas encore été traduites et s'affichent en anglais.
Unlocking Real-time with Gateways
Welcome back! In the previous lesson, we learned about WebSockets. Now, let's dive into how NestJS makes real-time communication easy with Gateways.
Think of a Gateway as a special controller for WebSocket connections. It listens for messages from clients and sends responses back, enabling dynamic, two-way communication.
Creating Your First Gateway
To create a Gateway, we use the @WebSocketGateway() decorator. This decorator marks a class as a WebSocket gateway.
By default, NestJS uses Socket.IO. You can specify a port, namespace, or other options. Let's start with a basic gateway:
import { WebSocketGateway,
WebSocketServer } from '@nestjs/websockets';
import { Server } from 'socket.io';
// src/events.gateway.ts
@WebSocketGateway(3001) // Listens on port 3001 for WS
export class EventsGateway {
@WebSocketServer() server: Server;
}
// src/app.module.ts (minimal)
import { Module } from '@nestjs/common';
import { EventsGateway } from './events.gateway';
@Module({
providers: [EventsGateway],
})
export class AppModule {}
// src/main.ts (minimal)
import { NestFactory } from '@nestjs/core';
import { AppModule } from './app.module';
async function bootstrap() {
const app = await NestFactory.create(AppModule);
await app.listen(3000); // HTTP app, WS runs alongside
}
bootstrap();Gateway Configuration Options
The @WebSocketGateway() decorator accepts an optional configuration object. This lets you customize how your WebSocket server behaves:
port: The port the WebSocket server listens on (e.g.,3001).namespace: Group connections under a specific path (e.g.,'/chat').cors: Configure Cross-Origin Resource Sharing for browser clients.adapter: Specify a custom WebSocket adapter (e.g., for `ws` instead of `socket.io`).
Handling Connections & Disconnections
Gateways can react to client connections and disconnections using lifecycle hooks. These are interfaces your gateway can implement:
OnGatewayInit: Called once the gateway is initialized.OnGatewayConnection: Called when a client connects.OnGatewayDisconnect: Called when a client disconnects.
Use these to perform setup or cleanup tasks.
import { WebSocketGateway,
OnGatewayConnection,
OnGatewayDisconnect,
WebSocketServer } from '@nestjs/websockets';
import { Server, Socket } from 'socket.io';
// src/events.gateway.ts
@WebSocketGateway(3001)
export class EventsGateway
implements OnGatewayConnection, OnGatewayDisconnect {
@WebSocketServer() server: Server;
handleConnection(client: Socket, ...args: any[]) {
console.log(`Client connected: ${client.id}`);
}
handleDisconnect(client: Socket) {
console.log(`Client disconnected: ${client.id}`);
}
}
// src/app.module.ts (minimal)
import { Module } from '@nestjs/common';
import { EventsGateway } from './events.gateway';
@Module({
providers: [EventsGateway],
})
export class AppModule {}
// src/main.ts (minimal)
import { NestFactory } from '@nestjs/core';
import { AppModule } from './app.module';
async function bootstrap() {
const app = await NestFactory.create(AppModule);
await app.listen(3000);
}
bootstrap();Subscribing to Client Messages
Clients send messages with an 'event name'. Your gateway listens for these specific events using the @SubscribeMessage() decorator.
The decorated method receives the client (Socket instance) and the payload (data sent by the client).
import { WebSocketGateway,
SubscribeMessage,
WebSocketServer } from '@nestjs/websockets';
import { Server, Socket } from 'socket.io';
// src/events.gateway.ts
@WebSocketGateway(3001)
export class EventsGateway {
@WebSocketServer() server: Server;
@SubscribeMessage('sendMessage')
handleMessage(client: Socket, payload: string): void {
console.log(`Message from ${client.id}: ${payload}`);
// Process payload, then send response
}
}
// src/app.module.ts (minimal)
import { Module } from '@nestjs/common';
import { EventsGateway } from './events.gateway';
@Module({
providers: [EventsGateway],
})
export class AppModule {}
// src/main.ts (minimal)
import { NestFactory } from '@nestjs/core';
import { AppModule } from './app.module';
async function bootstrap() {
const app = await NestFactory.create(AppModule);
await app.listen(3000);
}
bootstrap();Sending Messages Back to Clients
Once your gateway receives a message, you'll often want to send a response. You can inject the WebSocketServer instance using @WebSocketServer().
To send a message to a specific client, use client.emit('eventName', data). To broadcast to all clients, use this.server.emit('eventName', data).
import { WebSocketGateway,
SubscribeMessage,
WebSocketServer } from '@nestjs/websockets';
import { Server, Socket } from 'socket.io';
// src/events.gateway.ts
@WebSocketGateway(3001)
export class EventsGateway {
@WebSocketServer() server: Server;
@SubscribeMessage('echo')
handleEcho(client: Socket, payload: string): void {
console.log(`Received: ${payload} from ${client.id}`);
client.emit('echoResponse', `You said: ${payload}`);
}
@SubscribeMessage('broadcast')
handleBroadcast(client: Socket, payload: string): void {
this.server.emit(
'broadcastMessage',
`${client.id} broadcasted: ${payload}`
);
}
}
// src/app.module.ts (minimal)
import { Module } from '@nestjs/common';
import { EventsGateway } from './events.gateway';
@Module({
providers: [EventsGateway],
})
export class AppModule {}
// src/main.ts (minimal)
import { NestFactory } from '@nestjs/core';
import { AppModule } from './app.module';
async function bootstrap() {
const app = await NestFactory.create(AppModule);
await app.listen(3000);
}
bootstrap();Organizing Clients with Rooms
For more complex applications, you might not want to broadcast every message to every client. This is where rooms come in handy!
Rooms allow you to group specific clients together. Messages can then be sent only to clients within a particular room. This is perfect for chat channels, game lobbies, or specific user notifications.
Joining and Leaving Rooms
Socket.IO clients can join or leave rooms dynamically. You can manage this from your gateway methods using the client instance:
client.join(roomName): Adds the client to the specified room.client.leave(roomName): Removes the client from the specified room.
A client can be in multiple rooms simultaneously.
import { WebSocketGateway,
SubscribeMessage,
WebSocketServer } from '@nestjs/websockets';
import { Server, Socket } from 'socket.io';
// src/events.gateway.ts
@WebSocketGateway(3001)
export class EventsGateway {
@WebSocketServer() server: Server;
@SubscribeMessage('joinRoom')
handleJoinRoom(client: Socket, room: string): void {
client.join(room);
client.emit('joinedRoom', `You joined ${room}`);
console.log(`${client.id} joined room: ${room}`);
}
@SubscribeMessage('leaveRoom')
handleLeaveRoom(client: Socket, room: string): void {
client.leave(room);
client.emit('leftRoom', `You left ${room}`);
console.log(`${client.id} left room: ${room}`);
}
}
// src/app.module.ts (minimal)
import { Module } from '@nestjs/common';
import { EventsGateway } from './events.gateway';
@Module({
providers: [EventsGateway],
})
export class AppModule {}
// src/main.ts (minimal)
import { NestFactory } from '@nestjs/core';
import { AppModule } from './app.module';
async function bootstrap() {
const app = await NestFactory.create(AppModule);
await app.listen(3000);
}
bootstrap();Sending Messages to Specific Rooms
Once clients are in rooms, you can send targeted messages. Use the server.to(roomName).emit('eventName', data) method.
This ensures only clients subscribed to that particular room receive the message, making your real-time updates efficient and relevant.
import { WebSocketGateway,
SubscribeMessage,
WebSocketServer } from '@nestjs/websockets';
import { Server, Socket } from 'socket.io';
// src/events.gateway.ts
@WebSocketGateway(3001)
export class EventsGateway {
@WebSocketServer() server: Server;
@SubscribeMessage('roomMessage')
handleRoomMessage(
client: Socket,
payload: { room: string; message: string },
): void {
const { room, message } = payload;
this.server
.to(room)
.emit('roomUpdate',
`[${room}] ${client.id}: ${message}`);
console.log(
`Message in ${room} from ${client.id}: ${message}`
);
}
}
// src/app.module.ts (minimal)
import { Module } from '@nestjs/common';
import { EventsGateway } from './events.gateway';
@Module({
providers: [EventsGateway],
})
export class AppModule {}
// src/main.ts (minimal)
import { NestFactory } from '@nestjs/core';
import { AppModule } from './app.module';
async function bootstrap() {
const app = await NestFactory.create(AppModule);
await app.listen(3000);
}
bootstrap();Gateway Configuration Quiz
Which of the following statements about NestJS WebSocket Gateways and rooms are TRUE?
Recap: Master Your Gateway
Great job! You've learned how to configure NestJS Gateways for powerful real-time communication.
- We defined gateways using
@WebSocketGateway(). - We explored configuration options like port and namespace.
- We implemented lifecycle hooks for connections and disconnections.
- We handled client messages with
@SubscribeMessage(). - We used
@WebSocketServer()to broadcast and send targeted messages. - Finally, we mastered rooms for efficient client grouping and targeted messaging.
Next, we'll build a full real-time chat application!
Questions Fréquemment Posées
La leçon « Configuration des passerelles » est-elle gratuite ?
Oui — le texte complet de « Configuration des passerelles » est gratuit à lire ici sur le web. Pour la pratiquer de manière interactive (un éditeur de code intégré et un tuteur IA 24/7) et déverrouiller le reste du cours Node.js Backend Development Bootcamp, passe à CoddyKit PRO. Le cours Node.js Backend Development Bootcamp comprend 6 leçons au total.
Qu'est-ce que j'apprendrai dans « Configuration des passerelles » ?
Configurez les passerelles WebSocket dans NestJS et gérez les événements de connexion, les messages et les salles. Tu pratiques Node.js Backend Development Bootcamp avec du code pratique que tu exécutes directement dans le navigateur, et un tuteur IA 24/7 répond à tes questions au fur et à mesure que tu avances dans la leçon.
Dois-je avoir de l'expérience pour commencer Node.js Backend Development Bootcamp ?
Aucune expérience préalable n'est requise. Node.js Backend Development Bootcamp sur CoddyKit est structuré pour les débutants jusqu'aux apprenants avancés, donc tu peux commencer ici ou depuis le début et avancer à ton rythme. Ceci est la leçon 4 sur 6.
Combien de temps prend la leçon « Configuration des passerelles » ?
La plupart des leçons CoddyKit prennent environ 5–10 minutes. Chacune est courte et interactive, tu progresses régulièrement et tu repiques exactement où tu t'es arrêté sur le web et l'app.
Peux-tu écrire et exécuter du code dans cette leçon Node.js Backend Development Bootcamp ?
Oui. Chaque leçon Node.js Backend Development Bootcamp inclut un éditeur de code intégré, tu écris et exécutes du vrai code directement dans ton navigateur et tu reçois des retours IA instantanés — aucune configuration locale requise.
Toutes les leçons de ce cours
- Introduction aux WebSockets
- WebSockets avec NestJS
- Implémenter Socket.IO dans Node.js
- Configuration des passerelles
- Créer une application de discussion en temps réel
- Application de discussion en temps réel