Search icon
Subscription
0
Cart icon
Close icon
You have no products in your basket yet
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Nest.js: A Progressive Node.js Framework

You're reading from  Nest.js: A Progressive Node.js Framework

Product type Book
Published in Nov 2019
Publisher Packt
ISBN-13 9781800204737
Pages 317 pages
Edition 1st Edition
Languages
Authors (5):
Greg Magolan Greg Magolan
Profile icon Greg Magolan
Patrick Housley Patrick Housley
Profile icon Patrick Housley
Adrien de Peretti Adrien de Peretti
Profile icon Adrien de Peretti
Jay Bell Jay Bell
Profile icon Jay Bell
David Guijarro David Guijarro
Profile icon David Guijarro
View More author details

Table of Contents (16) Chapters

Preface
1. Introduction 2. Overview 3. Nest.js authentication 4. Dependency Injection system of Nest.js 5. TypeORM 6. Sequelize 7. Mongoose 8. Web sockets 9. Microservices 10. Routing and request handling in Nest.js 11. OpenAPI (Swagger) Specification 12. Command Query Responsibility Separation (CQRS) 13. Architecture 14. Testing 15. Server-side Rendering with Angular Universal

WebSocketGateway

To implement your first module using the Nest.js web socket, you will have to use the @WebSocketGateway decorator. This decorator can take an argument as an object to provide a way to configure how to use the adapter.

The implementation of the arguments respect the interface GatewayMetadata, allowing you to provide:

  • port, which must be use by the adapter
  • namespace, which belongs to the handlers
  • middlewares that have to be applied on the gateway before accessing the handlers

All the parameters are optional.

To use it, you have to create you first gateway class, so imagine a UserGateway:

@WebSocketGateway({
    middlewares: [AuthenticationGatewayMiddleware]
})  
export class UserGateway { /*....*/ }

By default, without any parameters, the socket will use the same port as your express server (generally 3000). As you can see, in the previous example we used a @WebSocketGateway, which uses the default port 3000 without namespace and with one middleware that we will see...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at €14.99/month. Cancel anytime}