[ahmadjoya]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/nestjs/docs.nestjs.com/blob/master/CONTRIBUTING.md

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• Docs
• Other... Please describe:

What is the current behavior?

Issue Number: N/A

Three samples import an Express/Fastify type with a plain import { ... } and then use it in a decorated signature:

• fundamentals/provider-scopes.md: constructor(@Inject(REQUEST) private request: Request) in an @Injectable() class
• http/mvc.md (Express): root(@Res() res: Response) on a @Get() handler
• http/mvc.md (Fastify): root(@Res() res: FastifyReply) on a @Get() handler

The tsconfig that nest new generates sets both isolatedModules and emitDecoratorMetadata. With those options, copying any of these samples into a new project fails to compile:

error TS1272: A type referenced in a decorated signature must be imported with 'import type' or a namespace import when 'isolatedModules' and 'emitDecoratorMetadata' are enabled.

Checked with TypeScript 5.9.3, @nestjs/common 12.3.2, @types/express and fastify 5.12.7, using the compiler options from the schematics tsconfig.json.

What is the new behavior?

The three imports use import type, which is what controllers.md, faq/raw-body.md and http/file-upload.md already do for the same types. All three samples compile with those options.

The other plain express/fastify type imports in the docs (middlewares.md, exception-filters.md, http/performance.md and the ContextIdStrategy sample in provider-scopes.md) don't use the type in a decorated signature, so they compile as they are and I left them alone.

Does this PR introduce a breaking change?

• Yes
• No

Other information