Hard dependency on fastify

I’m submitting a…

[ ] Regression 
[x] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.

Current behavior

Error: Module not found: Error: Can't resolve 'fastify-swagger' in '...\node_modules\@nestjs\swagger\dist'

Expected behavior

Should just work, when following the getting started guide 😃

Minimal reproduction of the problem with instructions

Set up nest using @nestjs/ng-universal with express and follow this guide https://docs.nestjs.com/openapi/introduction

What is the motivation / use case for changing the behavior?

I want to add openpi to my project. But when I follow the guide from docs i face the error above. I am not using fastify.

Environment

"@nestjs/common": "^7.0.0",
"@nestjs/swagger": "^4.8.2",
"@nguniversal/express-engine": "^12.1.0",
"express": "^4.15.2",
 "@angular/core": "~12.1.0",

For Tooling issues:
- Node version: v14.17.0
- Platform:  Windows

Others:

[mbeckenbach]

Yes it uses webpack for sure. I will push you something to GitHub tomorrow. Thank you in advance

[kamilmysliwiec]

https://github.com/nestjs/swagger/issues/1334#issuecomment-836488125

Long story short: webpack tries to bundle all deps referenced in your code (and libraries you use), even if you’re not actually using them (static analysis). Therefore, you must explicitly exclude these that you don’t use if you want to bundle your application. For this, you’ll have to provide a custom webpack configuration (setting the fastify-swagger as an external package using externals: []). You can find somewhat more complex example here https://github.com/nestjs/ng-universal/issues/115