Best VS Code Extensions for NestJS in 2026: 13 That Earn Their Place

This is the .vscode/extensions.json I drop into every NestJS project. Thirteen extensions, five of them NestJS-specific, the rest for the stack that always sits around Nest: Prisma, Jest, .env files, HTTP requests, Docker.

{
  "recommendations": [
    "imgildev.vscode-nestjs-snippets-extension",
    "imgildev.vscode-nestjs-generator",
    "devxmursalin.nestor",
    "archsense.architecture-view-nestjs",
    "imgildev.vscode-nestjs-swagger-snippets",
    "Prisma.prisma",
    "humao.rest-client",
    "Orta.vscode-jest",
    "mikestead.dotenv",
    "ms-azuretools.vscode-containers",
    "dbaeumer.vscode-eslint",
    "esbenp.prettier-vscode",
    "usernamehw.errorlens"
  ]
}

The rest of this post is why each one is on the list, which popular alternatives I left off and why, and what the NestJS Essential Extension Pack actually installs before you click it. Install counts are from the Marketplace on 17 September 2026. One disclosure up front: I built Nestor, number three on the list. I say what it does and does not do like everything else here.

How I picked

Three filters, applied in order:

1. Maintained. If the last update is more than three years old, it is off the list no matter the install count. NestJS 11 and TypeScript 5 have moved; snippets written for Nest 4 have not.

2. One job, no overlap. Two extensions that both generate controllers is one too many.

3. Earns its slot on a NestJS project specifically. GitLens and Code Spell Checker are fine extensions. They are not NestJS extensions, so they are not here.

NestJS-specific extensions

1. NestJS Snippets (imgildev)

imgildev.vscode-nestjs-snippets-extension, ~50K installs, updated August 2025, MIT.

The snippet set I recommend, and the reason is the update date. Its prefixes are namespaced ns_: ns_class_controller, ns_class_service, ns_class_dynamic_module, ns_deco_use_guards, ns_class_interceptor, ns_test. It covers GraphQL resolvers and operations (scoped to .graphql files), JwtModule.register, @WebSocketGateway(), @Sse(), and a ValidationPipe snippet that defaults to { whitelist: true, transform: true }, which is the config you want anyway.

What it does not do: anything the Nest CLI does. nest g resource users still generates a full CRUD module faster than any snippet. Snippets are for the file you are already in.

2. NestJS File Generator (imgildev)

imgildev.vscode-nestjs-generator, ~32K installs, updated May 2026, MIT.

Right-click a folder in the Explorer, pick controller, service, module, DTO, guard, interceptor, gateway, JWT guard, filter, or exception, name it, done. It auto-imports the new provider into the nearest module, adds a sidebar with tree views for methods, entities, DTOs and modules, and wraps the Nest CLI in an integrated terminal so you can run nest g without leaving the editor. Configurable per project through .vscode/settings.json (nestjs.files.include, nestjs.files.exclude, nestjs.files.watch).

This depends on NestJS Snippets above, so installing it pulls in both.

3. Nestor

devxmursalin.nestor, published 17 September 2026, MIT. Mine.

Snippets and generators produce code. Nestor explains it. It bundles 136 pages of docs.nestjs.com and an index of about 800 @nestjs/* symbols, so hovering ThrottlerModule, @SkipThrottle or ValidationPipe shows the relevant docs paragraph, a link that opens the full page in a side panel, and the other sections that cover it. Ctrl+Alt+N searches every page and heading. Everything is offline; it makes no network requests.

The second half is the design pattern hover: hover one of your own classes and it reports which Gang of Four pattern the class follows, the role it plays (ConcreteDecorator, say), review notes where the implementation misses part of the pattern's checklist, and the NestJS angle: interceptors as decorators, Passport strategies, CQRS commands and events, DI singletons. Detection is static and local. If you add a Groq API key it also asks an LLM, with a two-second hover timeout and per-workspace caching.

Limits, stated plainly: pattern detection is syntactic, so an interface declared in another file is matched by naming convention only; the side panel renders code blocks without syntax highlighting; the docs are a snapshot refreshed each release. Full write-up in the Nestor launch post.

4. Architecture View NestJS

archsense.architecture-view-nestjs, ~11K installs, updated October 2025, MIT.

One command, Show architecture, and it renders a diagram of your NestJS application built from static analysis of the source (the same team's Scout analyser and Orakul UI). That is the whole extension, and it is the right size. On a project past ten modules it is the fastest way to see the real module layout instead of the one in your head, and to question a module that has quietly become a hub. Six ratings, all five stars, which for a tool this narrow is the right signal.

5. NestJS Swagger Snippets (imgildev)

imgildev.vscode-nestjs-swagger-snippets, ~14K installs, updated August 2025, MIT.

Only if you use @nestjs/swagger. It adds ns_swagger_ snippets for @ApiProperty, @ApiTags and the other @nestjs/swagger decorators, plus the DocumentBuilder chain in main.ts (setTitle, setDescription, setVersion, setContact). If you decorate DTOs by hand for OpenAPI, this saves the most typing per day of anything on the list. If you generate OpenAPI from Zod or a CLI plugin, skip it.

The stack around NestJS

6. Prisma

Prisma.prisma, ~3.5M installs, updated September 2026.

Syntax highlighting, formatting, autocomplete, jump-to-definition and linting for schema.prisma. If your NestJS project uses Prisma this is not optional; without it the schema file is plain text. TypeORM and Mongoose users do not need an equivalent because their entities are TypeScript already.

7. REST Client

humao.rest-client, ~7.6M installs, 4.9 stars from 388 ratings.

Write requests in a .http file, click "Send Request" above each one, see the response in a split pane. Files live in the repo next to the controller they exercise, so they get code review and version history. Variables, environments and chained requests are supported.

Thunder Client (rangav.vscode-thunder-client) is the GUI alternative with a similar install count and a 2.4-star rating from 752 reviews. The install count says people want a GUI client in the editor; the rating says the current one is not it. Text files in git have never disappointed me, so REST Client.

8. Jest

Orta.vscode-jest, ~3.9M installs.

Runs the NestJS default test runner in watch mode, decorates each it() with pass/fail, and puts inline failure messages under the assertion. Pair it with Jest / Vitest Runner (firsttris.vscode-jest-runner, ~2.3M installs) if you want "Run" and "Debug" CodeLens above individual tests; I find the main Jest extension enough.

9. DotENV

mikestead.dotenv, ~8.4M installs.

Syntax highlighting for .env files. Last updated 2018, which is fine, because .env syntax has not changed either. It is the one exception I make to the maintenance rule: the job is done.

10. Container Tools

ms-azuretools.vscode-containers, ~17.9M installs, updated September 2026.

Microsoft's current home for Dockerfile and Compose editing, image and container management, and attaching to a running container. It is where the features of the older Docker extension (ms-azuretools.vscode-docker) live now. Every NestJS project I ship has a docker-compose.yml for Postgres and Redis, so this stays.

TypeScript hygiene

These three are not NestJS extensions, but a NestJS project without them is not set up.

11. ESLint

dbaeumer.vscode-eslint, ~52.8M installs. nest new scaffolds an ESLint config; this extension is what makes it show up in the editor rather than only in CI.

12. Prettier

esbenp.prettier-vscode, ~71.6M installs. Same story; nest new ships a .prettierrc. Turn on editor.formatOnSave and stop thinking about it.

13. Error Lens

usernamehw.errorlens, ~9.9M installs, 4.9 stars. Prints diagnostics inline at the end of the line instead of a squiggle you have to hover. On a DI error like "Nest can't resolve dependencies of the UsersService", seeing the TypeScript side of the problem without a mouse movement matters more than it sounds. Pretty TypeScript Errors (yoavbls.pretty-ts-errors, ~2.3M installs, 5.0 stars) is a good companion for the generic-heavy errors decorators produce.

Should you install the NestJS Essential Extension Pack?

imgildev.vscode-nestjs-pack (~11K installs) is the pack most people find first. It installs 27 extensions. The NestJS-specific ones are the same three from the top of this list: NestJS File Generator, NestJS Snippets, NestJS Swagger Snippets. The other 24 are general tooling: ESLint, Prettier, Error Lens, Jest, Jest Runner, DotENV, Path Intellisense, GitLens, Pretty TypeScript Errors, Better Comments, EditorConfig, gitignore, Auto Import, Auto Barrel, JSON Flow, Draw Folder Structure, Highlight Matching Tag, Trailing Spaces, Indent Rainbow, Markdown All in One, markdownlint, and a few more.

My take: install the pack if you are setting up a fresh machine and want a reasonable baseline in one click. Do not install it into a team's recommended extensions, because you are recommending Indent Rainbow and Auto Rename Tag to a backend project. Pick the three NestJS ones plus what your stack needs, and write the list into .vscode/extensions.json so new team members get a prompt instead of a scavenger hunt.

Nestor, Architecture View and Prisma are not in the pack, so you would add those anyway.

Popular ones I left off, and why

Settings that make the list work

Four lines in .vscode/settings.json cover most of the friction:

{
  "editor.formatOnSave": true,
  "editor.defaultFormatter": "esbenp.prettier-vscode",
  "editor.codeActionsOnSave": { "source.fixAll.eslint": "explicit" },
  "[prisma]": { "editor.defaultFormatter": "Prisma.prisma" }
}

Commit both files. The whole point of .vscode/extensions.json is that the next developer on the repo gets a "this workspace has extension recommendations" prompt on first open.

FAQ

Is there an official NestJS VS Code extension?

No. The NestJS team ships the @nestjs/cli and the docs site, not an editor extension. Everything on the Marketplace is community-built, including the extensions in this post.

Do I need snippets if I use the Nest CLI?

Not for whole files; nest g is faster for those. Snippets earn their keep inside a file: adding a guard decorator, a createParamDecorator, a test scaffold, a JwtModule.register block.

Which extension shows NestJS documentation inside VS Code?

Nestor. It bundles the docs and shows them on hover and in a searchable side panel, offline. None of the snippet or generator extensions include documentation.

Is the NestJS Essential Extension Pack worth it?

For a fresh machine, yes. For a team repo, no; it recommends 24 general-purpose extensions alongside the three NestJS ones. Pick individually and commit .vscode/extensions.json.

What VS Code extensions do I need for NestJS with Prisma?

The Prisma extension for schema.prisma, plus the NestJS list above. If you want Prisma-flavoured snippets, imgildev also publishes NestJS Prisma Snippets (imgildev.vscode-nestjs-prisma-snippets, ~6K installs).

Work with me

I ship NestJS backends for SaaS products, usually with Next.js in front and Prisma underneath. If you need one built or an existing one reviewed, book a call or start a professional-tier build. Scope is on the web and SaaS platforms professional page; how I work remotely from Bangladesh is on the remote developer page.