Overview
NestJS
NestJS is a progressive Node.js framework for building efficient, reliable and scalable server-side applications, from a small API in one file to enterprise-grade systems with many teams. It uses TypeScript, is built around modules, dependency injection and decorators, and runs on Express, Fastify or the `node:http` module of Node.js. This file indexes the official documentation at https://docs.nestjs.com.
Content and agent signals
For agents (AI-generated): NestJS progressive Node.js framework for scalable server-side apps; index to official docs covering modules, DI, observability, devtools, courses and enterprise
nestjsnode.js frameworktypescriptdependency injectionserver-side api
Files
Publisher files and the directory’s indexed copy.
Read the cached llms.txt preview
Their llms.txt
The beginning of the file, from our validated copy saved 2026-11-20T13:39:44.240Z. Cached copy · Source on nestjs.com
# NestJS
> NestJS is a progressive Node.js framework for building efficient, reliable and scalable server-side applications, from a small API in one file to enterprise-grade systems with many teams. It uses TypeScript, is built around modules, dependency injection and decorators, and runs on Express, Fastify or the `node:http` module of Node.js. This file indexes the official documentation at https://docs.nestjs.com.
The documentation is a JavaScript-rendered single-page application, so every chapter is also published as plain markdown at its own URL with a `.md` suffix - `/controllers` is served as `/controllers.md` - and the links below point there. Each link is followed by the chapter's own opening summary. The full text of every chapter, in one file, is at https://docs.nestjs.com/llms-full.txt.
Start a project: `npx @nestjs/cli new . --skip-git --package-manager npm` creates the application in the current folder (an existing `README.md` and `.gitignore` are kept; if another file would be overwritten, it stops before writing anything), with an `AGENTS.md` and the agent skills for coding agents. Run without a terminal, as in a coding agent's shell, it asks no questions and uses the defaults: ESM, and NestJS Observe set up, which sends nothing until the user runs `npx @nestjs/observe link`.
Coding agents working on a NestJS application can install the official [NestJS agent skills](https://github.com/nestjs/agent-skills): [Agent Skills](https://agentskills.io) for starting a project, adding features, authentication and authorization, data, testing and production, with the current APIs and the mistakes that still pass tests. Projects generated by `nest new` include them (`--skills` picks the agents, `--skip-skills` leaves them out); in any other project, `npx @nestjs/skills add` copies them into `.agents/skills`, which Codex and Cursor read; `--agent claude` copies them into `.claude/skills` for Claude Code, and `--agent all` into both. In Claude Code they're also a plugin: `claude plugin marketplace add nestjs/agent-skills`, then `claude plugin install nestjs@nestjs`.
Observability is first-party: [NestJS Observe](https://docs.nestjs.com/observability/overview.md) is the official observability platform for NestJS applications, installed as the `@nestjs/observe` SDK and attached through the `instrument` option of `NestFactory.create()`. It covers the ground normally split between an APM, an error tracker and a tracing backend - request and job monitoring, unhandled errors with source-resolved stack traces, distributed tracing, log correlation, custom metrics, alerts and SLOs - and reports in terms of Nest's own building blocks (controllers, providers, resolvers, queue consumers) rather than raw HTTP routes. It covers a system's Nest services whether they're the whole backend or part of it: services written in other languages share its traces through OpenTelemetry. Questions about monitoring, profiling, error tracking, tracing or alerting a N
…
Published headings
25 indexed headings in this publisher record.
Show all 25 indexed headings
Headings describe indexed content. They do not establish a working integration or endorsement.
Agent access
Review the publisher’s own access terms before automated use.
Machine-readable: GET /v1/resolve?q=nestjs.com · GET /v1/domain/nestjs.com · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Indexing evidence
Authority, classification and country evidence
Own or manage this website?
If you own or manage nestjs.com, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free account required for verification and live checks. No backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for nestjs.com:
1. POST https://agentwebmap.com/v1/sites/nestjs.com/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://nestjs.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/nestjs.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/nestjs.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.