Why NestJS exists

Introduction

NestJS exists to help developers build server-side applications easily and in an organized way. It makes writing backend code simpler and more maintainable.

When you want to build a backend API for a web or mobile app.

When you need a structured way to organize your server code.

When you want to use modern JavaScript or TypeScript features on the server.

When you want to build scalable and testable applications.

When you prefer a framework that supports dependency injection and modular design.

Syntax

NestJS

No specific syntax applies here as this is a conceptual explanation.

NestJS uses TypeScript and follows a modular architecture.

It is built on top of Express (or optionally Fastify) to handle HTTP requests.

Examples

This topic explains the purpose of NestJS rather than code syntax.

NestJS

No code example needed for this concept.

Sample Program

This simple NestJS app shows how NestJS organizes code with controllers and modules. It starts a server that responds with a greeting message.

NestJS

import { Controller, Get } from '@nestjs/common';
import { Module } from '@nestjs/common';
import { NestFactory } from '@nestjs/core';

@Controller()
class AppController {
  @Get()
  getHello(): string {
    return 'Hello from NestJS!';
  }
}

@Module({
  controllers: [AppController],
})
class AppModule {}

async function bootstrap() {
  const app = await NestFactory.create(AppModule);
  await app.listen(3000);
  console.log('Server running on http://localhost:3000');
}

bootstrap();

Important Notes

NestJS helps keep backend code clean and easy to manage.

It supports TypeScript out of the box, which adds helpful features like type checking.

Using NestJS can speed up backend development by providing ready-to-use tools and patterns.

Summary

NestJS exists to simplify building backend applications.

It provides structure and modern features for server-side code.

It is great for scalable, maintainable, and testable backend projects.

Practice

1. Why was NestJS created as a framework for backend development?

easy

A. To replace frontend frameworks like React and Angular

B. To create mobile applications easily

C. To only support legacy JavaScript without TypeScript

D. To provide a clear and organized way to build scalable server-side apps

Solution

1. Step 1: Understand NestJS purpose

   NestJS is designed to help developers build backend applications that are easy to maintain and scale.

2. Step 2: Compare options with NestJS goals

   Options A, C, and D do not match NestJS's backend focus or modern language support.

3. Final Answer:

   To provide a clear and organized way to build scalable server-side apps -> Option D

4. Quick Check:

   Backend clarity and scalability = B [OK]

Hint: NestJS focuses on backend clarity and scalability [OK]

Common Mistakes:

• Confusing NestJS with frontend frameworks
• Thinking NestJS only supports old JavaScript
• Assuming NestJS is for mobile apps

2. Which of the following is the correct way to create a basic NestJS controller?

easy

A. import { Controller, Get } from '@nestjs/common';

@Controller('cats')
export class CatsController {
@Get()
findAll() {
return 'This action returns all cats';
}
}

B. import { Controller } from 'nestjs';

@Controller('/cats')
class Cats {
getAll() {
return 'Cats list';
}
}

C. const controller = require('nestjs').Controller;

controller('/cats', () => {
return 'Cats';
});

D. import { Controller, Post } from '@nestjs/common';

@Controller('cats')
export class CatsController {
findAll() {
return 'All cats';
}
}

Solution

1. Step 1: Check import and decorator usage

   import { Controller, Get } from '@nestjs/common'; @Controller('cats') export class CatsController { @Get() findAll() { return 'This action returns all cats'; } } correctly imports from '@nestjs/common' and uses @Controller and @Get decorators properly.

2. Step 2: Verify method and return value

   import { Controller, Get } from '@nestjs/common'; @Controller('cats') export class CatsController { @Get() findAll() { return 'This action returns all cats'; } }'s method findAll returns a string as expected for a GET route. Other options have wrong imports, missing decorators, or wrong HTTP method.

3. Final Answer:

   Option A code snippet -> Option A

4. Quick Check:

   Correct decorators and imports = A [OK]

Hint: Look for @Controller and @Get from '@nestjs/common' [OK]

Common Mistakes:

• Using wrong import paths
• Missing HTTP method decorators
• Using require instead of import

3. Consider this NestJS service code:

import { Injectable } from '@nestjs/common';

@Injectable()
export class MathService {
  double(value: number): number {
    return value * 2;
  }
}

const service = new MathService();
console.log(service.double(5));

What will be printed in the console?

medium

A. 10

B. 5

C. undefined

D. Error: Injectable decorator missing

Solution

1. Step 1: Understand the double method

   The method multiplies the input value by 2, so double(5) returns 10.

2. Step 2: Check usage of Injectable decorator

   The @Injectable decorator marks the class for NestJS dependency injection but does not affect direct instantiation or method output.

3. Final Answer:

   10 -> Option A

4. Quick Check:

   5 times 2 equals 10 [OK]

Hint: Method doubles input; decorator doesn't block direct use [OK]

Common Mistakes:

• Thinking @Injectable prevents direct instantiation
• Expecting undefined return
• Confusing decorator effects with runtime errors

4. This NestJS controller code has an error:

import { Controller, Get } from '@nestjs/common';

@Controller('dogs')
export class DogsController {
  @Get()
  getDogs() {
    return this.dogs;
  }
}

What is the main problem here?

medium

A. The import statement is wrong

B. The controller is missing a constructor to initialize 'dogs'

C. The @Get decorator is used incorrectly

D. The method getDogs should be async

Solution

1. Step 1: Identify usage of 'this.dogs'

   The method returns 'this.dogs' but the class does not define or initialize 'dogs'.

2. Step 2: Check for initialization

   Without a constructor or property assignment, 'this.dogs' is undefined, causing runtime errors.

3. Final Answer:

   The controller is missing a constructor to initialize 'dogs' -> Option B

4. Quick Check:

   Undefined property needs initialization [OK]

Hint: Check if all used properties are initialized [OK]

Common Mistakes:

• Assuming decorators fix property issues
• Thinking async is required without async code
• Ignoring missing property initialization

5. You want to build a scalable backend app using NestJS that handles many users and keeps code organized. Which feature of NestJS helps most with this goal?

hard

A. Its use of global variables for shared state

B. Its built-in support for frontend UI components

C. Its modular architecture allowing separation of features into modules

D. Its automatic generation of mobile app code

Solution

1. Step 1: Identify scalability needs

   Scalable apps need clear separation of concerns and organized code structure.

2. Step 2: Match NestJS features to needs

   NestJS modules let you group related code, making it easier to maintain and scale. Other options do not support backend scalability.

3. Final Answer:

   Its modular architecture allowing separation of features into modules -> Option C

4. Quick Check:

   Modular design = scalable backend [OK]

Hint: Modular design is key for scalable backend apps [OK]

Common Mistakes:

• Confusing backend with frontend features
• Thinking NestJS generates mobile code
• Using global variables instead of modules