Why NestJS exists - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why was NestJS created?

NestJS was created to solve which main problem in Node.js backend development?

A To provide a structured and scalable architecture for building server-side applications

B To replace JavaScript with a new programming language

C To simplify database management by removing the need for ORMs

D To create a frontend framework for building user interfaces

💡 Hint

Think about what developers struggle with when building large backend apps in Node.js.

NestJS was designed to bring a clear structure and modularity to Node.js backend apps, making them easier to build and maintain.

❓ component_behavior

intermediate

What does NestJS provide out of the box?

Which feature is a core part of NestJS that helps developers write clean backend code?

A Dependency injection system to manage class dependencies automatically

B Built-in frontend templating engine for UI rendering

C Automatic CSS styling for web pages

D Real-time chat server without any configuration

💡 Hint

Think about how NestJS helps manage how classes get their needed parts.

Dependency injection is a key feature in NestJS that allows classes to receive their dependencies automatically, improving code modularity and testing.

📝 Syntax

advanced

Which code snippet correctly defines a NestJS controller?

Choose the option that shows a valid NestJS controller class with a GET route.

A

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

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

B

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

@Controller('cats')
export function CatsController() {
  @Get()
  function findAll() {
    return 'Cats list';
  }
}

C

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

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

D

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

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

💡 Hint

Look for correct use of decorators and class syntax.

Option C correctly uses the @Controller and @Get decorators on a class and method, following NestJS syntax.

❓ lifecycle

advanced

When is the NestJS module lifecycle hook 'onModuleInit' called?

At what point in the NestJS application lifecycle does the 'onModuleInit' method run?

A Only when the application shuts down

B Right after the module's providers have been instantiated but before the app starts listening

C Before any modules or providers are created

D After every HTTP request is handled

💡 Hint

Think about when initialization logic for a module should run.

'onModuleInit' runs after the module's dependencies are ready but before the app starts accepting requests, allowing setup tasks.

🔧 Debug

expert

Why does this NestJS service fail to inject the dependency?

Given this service code, why will NestJS throw a runtime error about missing dependency? ```typescript import { Injectable } from '@nestjs/common'; import { CatsRepository } from './cats.repository'; @Injectable() export class CatsService { constructor(private catsRepo: CatsRepository) {} } ``` Options:

A The constructor parameter should be public, not private

B CatsService is missing the @Controller decorator

C CatsRepository must be imported from '@nestjs/common' to work

D CatsRepository is not marked with @Injectable(), so NestJS cannot inject it

💡 Hint

Check if the dependency class is properly decorated for injection.

For NestJS to inject a class, it must be decorated with @Injectable(). Without it, NestJS does not recognize it as a provider.