The session begins by initializing a new NestJS application using the command line interface. The instructor navigates the project structure, reviews basic file configurations, and starts the development server. Finally, they install necessary networking dependencies, including axios, axios-retry, http-terminator, and opossum for production-ready implementations.
Length 4:54
Captions English (Generated), Spanish (Auto-translated), French (Auto-translated), Korean (Auto-translated), Portuguese (Auto-translated), Vietnamese (Auto-translated) #nestjs #nodejs #backend #axios #programming #tutorial #software-development #networking #typescript #terminal
0:00 All right, so let's go ahead and start off with initializing our NestJS 0:03 project, 0:04 which is what I'm gonna use to go over our production 0:08 networking concepts. Now, it's not important to use 0:11 NestJS specifically. Any Node.js backend will work 0:15 for this particular lecture. However, I prefer NestJS because it helps us to 0:19 encapsulate our dependencies really nicely, and we'll see some nice 0:23 design patterns, including a factory pattern, 0:26 to implement our 0:26 production networking best practices. 0:29 So to use NestJS, if you don't already have the CLI 0:33 available, you can add this globally with npm 0:37 @nestjs/cli 0:40 @latest to go ahead and grab that CLI. 0:43 And then once you have it, you should be able to run nest 0:47 new and call this project whatever you want. 0:50 I'll call mine production-networking, and I'll go ahead and choose 0:54 pnpm as my package manager. So go ahead and let the 0:58 project finish initializing. 1:01 So after it initializes, we should be able to CD into the project, 1:05 and we can open it up inside a code editor. 1:09 And so here we're gonna see the basic starting project for 1:13 a new NestJS application. Now, I'm not gonna go over all of 1:16 this in detail. You can refer back to my previous lectures 1:20 for this. 1:21 However, let's just review. We have our starting package JSON with the 1:25 ability to build our backend server and start up the 1:28 development server to watch for changes using this startdev 1:32 command. 1:34 We have our basic NestJS dependencies, 1:37 and inside of source, we have our main TS file 1:41 where we bootstrap our underlying application by using the 1:45 nestFactory.create to create the application 1:49 and then bootstrap the HTTP server to listen on port 1:53 3000 for incoming requests. And so what this will do is it'll 1:57 bring in our root app module here, which currently
The rest of the transcript is for members.
Sign in 