NestJs Questions

The @Get() decorator is specifically designed to handle HTTP GET requests. The other decorators are used for different HTTP methods or route configuration.

Controllers are always defined within a specific module in NestJS. This association determines their scope and how they are managed within the application's structure.

The main.ts file is the entry point of your NestJS application. It bootstraps the NestJS application, often setting up the listening port and other core configurations.

Providers are fundamental to NestJS's dependency injection system. They can be classes annotated with @Injectable(), and their instances can be injected into constructors of other components, promoting code reusability and testability.

Dependency Injection promotes loose coupling, not increased coupling. It allows components to depend on abstractions (interfaces) rather than concrete implementations.

NestJS is built on top of Node.js, which uses JavaScript as its primary programming language. While TypeScript is often preferred, you can write NestJS applications directly in JavaScript.

The @Inject() decorator expects the injection token of the dependency as its argument. This token can be a class, a string, a symbol, or any other value that uniquely identifies the dependency.

The getStatus() method allows the filter to access the appropriate HTTP status code from the caught exception, enabling it to set the correct status code for the error response.

NestJS allows defining multiple route paths for a single method by providing an array of strings as the first argument to the route decorator (@Get(), @Post(), etc.).

In NestJS, a Controller can access a Service's methods by injecting an instance of the Service through the Controller's constructor. This is facilitated by NestJS's Dependency Injection mechanism.