<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"><channel>
<title>Learn NestJS</title>
<link>https://learn-nestjs.com/</link>
<description>Free NestJS tutorials, plus how NestJS conventions make agent-generated backend code reviewable.</description>
<lastBuildDate>Sun, 06 Sep 2026 03:07:12 GMT</lastBuildDate>
<item><title>Hello, World!</title><link>https://learn-nestjs.com/hello-world/</link><guid>https://learn-nestjs.com/hello-world/</guid><description>A running NestJS application in three commands, and what each generated file is actually for.</description></item>
<item><title>Nest conventions make agent-written code reviewable</title><link>https://learn-nestjs.com/ai/conventions-for-agents/</link><guid>https://learn-nestjs.com/ai/conventions-for-agents/</guid><description>The framework's opinionated structure turns out to be exactly what makes generated back-end code fast to review. Here is how to lean on it.</description></item>
<item><title>The NestJS mistakes language models actually make</title><link>https://learn-nestjs.com/review/failure-modes/</link><guid>https://learn-nestjs.com/review/failure-modes/</guid><description>TypeScript catches the type errors. What gets through is authorisation, validation configuration, and logic drifting out of services — and those are the ones that matter.</description></item>
<item><title>Dependency hygiene for NestJS projects</title><link>https://learn-nestjs.com/review/dependencies/</link><guid>https://learn-nestjs.com/review/dependencies/</guid><description>npm's problems, plus a framework whose packages must all be on the same major version, plus a decorator ecosystem where a version mismatch produces a runtime error with no useful message.</description></item>
<item><title>Modules</title><link>https://learn-nestjs.com/modules/</link><guid>https://learn-nestjs.com/modules/</guid><description>The unit of organisation in Nest, and the thing that decides what can see what.</description></item>
<item><title>Writing an AGENTS.md for NestJS</title><link>https://learn-nestjs.com/ai/agents-md/</link><guid>https://learn-nestjs.com/ai/agents-md/</guid><description>Nest already decides where things go, so this file has one real job: the security configuration the framework will happily let you get wrong.</description></item>
<item><title>Controllers and routing</title><link>https://learn-nestjs.com/controllers/</link><guid>https://learn-nestjs.com/controllers/</guid><description>Parse the request, call a service, return a value. Everything else in a controller is a mistake.</description></item>
<item><title>Per-tenant token budgets in NestJS</title><link>https://learn-nestjs.com/ai/tokenomics/</link><guid>https://learn-nestjs.com/ai/tokenomics/</guid><description>Nest's interceptors and guards are exactly the right shape for cost control: measure in one place, enforce before the handler runs, and no feature can be added without both.</description></item>
<item><title>Security review checklist for NestJS applications</title><link>https://learn-nestjs.com/review/security/</link><guid>https://learn-nestjs.com/review/security/</guid><description>The framework gives you the right places to put security controls. What it will not do is tell you when one is missing — and a missing global is invisible until someone finds it.</description></item>
<item><title>Providers and dependency injection</title><link>https://learn-nestjs.com/providers-and-di/</link><guid>https://learn-nestjs.com/providers-and-di/</guid><description>How Nest constructs your objects, and the injection patterns worth knowing beyond the constructor.</description></item>
<item><title>The performance traps in generated NestJS code</title><link>https://learn-nestjs.com/review/performance/</link><guid>https://learn-nestjs.com/review/performance/</guid><description>Two Nest-specific problems dominate: N+1 queries through the ORM, and request-scoped providers that quietly make your entire dependency graph rebuild on every request.</description></item>
<item><title>DTOs and validation</title><link>https://learn-nestjs.com/dto-and-validation/</link><guid>https://learn-nestjs.com/dto-and-validation/</guid><description>The boundary where untrusted input becomes a typed object. Get this right and most of your input-handling bugs disappear.</description></item>
<item><title>Guards, authentication and authorisation</title><link>https://learn-nestjs.com/guards-and-auth/</link><guid>https://learn-nestjs.com/guards-and-auth/</guid><description>Guards answer one question: may this request proceed? Getting the difference between authentication and authorisation right is where most back-end vulnerabilities live.</description></item>
<item><title>Database access and testing</title><link>https://learn-nestjs.com/database-and-testing/</link><guid>https://learn-nestjs.com/database-and-testing/</guid><description>Wiring a database into a Nest module, and building the test setup that lets an agent iterate without a container.</description></item>
<item><title>Interceptors</title><link>https://learn-nestjs.com/interceptors/</link><guid>https://learn-nestjs.com/interceptors/</guid><description>Code that wraps a handler — before and after. Logging, response shaping, caching, timeouts and cleanup all live here.</description></item>
<item><title>Exception Filters</title><link>https://learn-nestjs.com/exception-filters/</link><guid>https://learn-nestjs.com/exception-filters/</guid><description>Turning thrown errors into HTTP responses — in one place, with full detail in the log and none of it leaking to the client.</description></item>
<item><title>Middleware and Lifecycle</title><link>https://learn-nestjs.com/middleware-and-lifecycle/</link><guid>https://learn-nestjs.com/middleware-and-lifecycle/</guid><description>The layer beneath Nest's abstractions, and the module hooks that decide whether your redeploys leak database connections.</description></item>
<item><title>Configuration and Environment</title><link>https://learn-nestjs.com/configuration/</link><guid>https://learn-nestjs.com/configuration/</guid><description>An application that refuses to start on a missing secret is far better than one that starts and fails on the first request that needs it.</description></item>
</channel></rss>