First NestJS application - Step-by-Step Execution

Concept Flow - First NestJS application

Start NestJS CLI

↓

Generate new project

↓

Create main.ts (entry)

↓

Define AppModule

↓

Define AppController

↓

Define AppService

↓

Bootstrap application

↓

Listen on port

↓

App ready to accept requests

This flow shows how NestJS starts from CLI project creation, sets up modules, controllers, and services, then boots the app to listen for requests.

Execution Sample

NestJS

import { NestFactory } from '@nestjs/core';
import { AppModule } from './app.module';

async function bootstrap() {
  const app = await NestFactory.create(AppModule);
  await app.listen(3000);
}
bootstrap();

This code boots the NestJS app by creating it from AppModule and starts listening on port 3000.

Execution Table

Step	Action	Evaluation	Result
1	Call bootstrap()	Function starts	bootstrap function invoked
2	NestFactory.create(AppModule)	Creates app instance	App instance created with AppModule
3	app.listen(3000)	Start server on port 3000	Server listening on port 3000
4	bootstrap() completes	App running	App ready to accept requests

💡 bootstrap function completes after app starts listening on port 3000

Variable Tracker

Variable	Start	After Step 2	After Step 3	Final
app	undefined	App instance created	Server listening	Server running

Key Moments - 2 Insights

Why do we use async/await in bootstrap()?

Because NestFactory.create() and app.listen() return promises, we await them to ensure the app is fully created and listening before continuing, as shown in execution_table steps 2 and 3.

What is AppModule's role in this process?

AppModule defines the root module of the app, telling NestJS what controllers and providers to load. It's passed to NestFactory.create() at step 2 to build the app structure.

Visual Quiz - 3 Questions

Look at the execution table, what is the state of 'app' after step 2?

A Server listening

B App instance created

C Undefined

D App stopped

💡 Hint

Check the variable_tracker row for 'app' after Step 2

At which step does the server start listening on port 3000?

A Step 3

B Step 2

C Step 1

D Step 4

💡 Hint

Look at the 'Action' and 'Result' columns in execution_table

If we remove 'await' before app.listen(3000), what happens?

A App will not start listening

B AppModule won't load

C bootstrap() may complete before server is ready

D NestFactory.create() fails

💡 Hint

Consider the async nature of app.listen() in execution_table steps 3 and 4

Concept Snapshot

NestJS app starts by creating an app instance from AppModule using NestFactory.
Use async/await in bootstrap() to wait for app creation and server listening.
App listens on a port to accept requests.
AppModule defines app structure with controllers and providers.
Bootstrap function runs once to start the app.

Full Transcript

This visual execution traces the first NestJS application startup. It begins with the bootstrap function call, which uses NestFactory to create an app instance from AppModule. The app then listens on port 3000. Variables like 'app' change from undefined to an app instance, then to a running server. Key points include the use of async/await to handle promises and the role of AppModule as the root module. The app is ready to accept requests after listening starts.