[fadiroot]

PR Checklist

• The commit message follows our guidelines: https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

• Bugfix

What is the current behavior?

Issue Number: N/A

In watch mode with --type-check, the swc compiler forks forked-type-checker with the root compilerOptions.plugins only:

JSON.stringify(configuration.compilerOptions.plugins ?? []),

In a monorepo an application can declare its own plugins under projects.<app>.compilerOptions.plugins, and the non-watch path already loads them per application through loadPlugins() (which resolves compilerOptions.plugins with getValueOrDefault(..., appName)). So with

{ "projects": { "api": { "compilerOptions": { "plugins": ["@nestjs/swagger"] } } } }

and no root plugins, nest build api --builder swc --type-check generates the swagger metadata, while nest start api --builder swc --type-check --watch prints "Found 0 issues" and generates none. The forked checker places whatever it receives under projects[app], so the application's own plugins are lost for good.

#3589 fixed the same class of problem for sourceRoot in these same fork arguments; the plugins argument one line below was missed.

What is the new behavior?

The plugins are resolved through getValueOrDefault(configuration, 'compilerOptions.plugins', appName), matching the non-watch path and the sourceRoot argument.

The existing "should fork the type checker with the built application source root" spec now declares per-application plugins and asserts they reach the forked checker. It fails on master and passes with this change.

Does this PR introduce a breaking change?

• No