My fix was...

The plugin filters the files it looks up based on a suffix rule.

• If you use a different naming convention than Angular's, you need to pass custom plugin options to fix it;
• If your controller or Dto is not inside a file with the name suffix, it wont be upgraded.

I had exactly the same issue.

I solved it with this:

1. Make sure you have nestcli installed: npm i -g @nestjs/cli
2. Update nestcli on deployment before you make npm install: nest update
3. If this not helps, try another Swagger-Version. I had the problem with version 4.5.9, I upgraded to @nestjs/swagger": "^4.5.11 and it helped.

Hope this works for you.

do you know that the plugin won't touch source files, right? you can compare the .dto.js with and without the plugin enabled

NRWL doesn't use Nest CLI, however you can still achieve the same results by adding the Swagger Plugin to the webpack transformation pipeline that NX uses.

1. Open the project.json in the specific app where you want the NestJS Swagger Plugin to be active.
2. Locate the configuration for the @nrwl/webpack:webpack executor
3. Add @nestjs/swagger/plugin to the list of transformers.
4. (Optional) configure the plugin's settings like introspectComments

Below an example:

{
    "name": "project-with-swagger-plugin",
    "targets": {
        "build": {
            "executor": "@nrwl/webpack:webpack",
            "options": {
                // other options 
                "transformers": [
                    // register plugins here
                    {
                        "name": "@nestjs/swagger/plugin",
                        "options": {
                            "introspectComments": true
                        }
                    }
                ]
            },
        }
   }
}