Tag: nestjs Basic
This content is a draft and will not be included in production builds.
27 articles tagged nestjs:
- AsyncLocalStorage: per-request context, when context gets lost, and when not to use it
- Common API mistakes: injection, authorization, secrets, retries
- Common mistakes in Node.js, NestJS and PostgreSQL backend code
- Cross-service transactions in NestJS: keeping one connection across services with CLS
- Custom decorators and Reflector in NestJS: why @Public() on a controller has no effect
- Decorator pattern: adding cache, metrics and retry around a client, and why the order changes the numbers
- DTO validation in NestJS: why role "admin" and a mistyped address still get through
- Dynamic modules in NestJS: forRoot, forRootAsync and why importing twice yields two instances
- Error handling, comments, duplication and dependency direction
- Exception filters in NestJS: one error format, no leaked SQL, and knowing which errors never reach a filter
- Functions and side effects: guard clauses, no flags, a pure core
- Hexagonal and clean architecture: switch payment providers without touching the place-order use case
- Integration tests with Testcontainers: a real Postgres, Redis and Kafka per run, without slowing CI to a crawl
- Naming in backend systems: code, database, API and events
- NestJS architecture: modules, providers and controllers
- NestJS Dependency Injection: tokens, providers, useClass vs useExisting
- OAuth 2.0, OIDC and PKCE: signing in through an identity provider without leaking the code or the token
- Observer and domain events: what OrderPaid guarantees when it fires in-process, and when you need an outbox
- Parse and validate env at startup: report every error, then exit
- Pragmatic clean code: write code the next person can change safely
- Provider scopes in NestJS: singleton, request and transient
- Request lifecycle in NestJS: who runs first, who blocks the request, and where errors land
- Safe refactoring: characterization tests and commits that separate behavior changes
- Scenario: a Node.js Pod gets OOMKilled every 6 hours
- Secure coding for backends: the vulnerabilities live in the code you write
- Six naming rules and how to apply them in TypeScript and NestJS
- Strategy pattern: changing rules without stuffing more branches into checkout