You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[ ] Regression
[*] 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
If I write a module which uses @nestjs/common sometimes there is a complaint about the multer module not being found
Expected behavior
There is no complaint about multer.
Minimal reproduction of the problem with instructions
What is the motivation / use case for changing the behavior?
Being able to write modules which use @nestjs/common without needing any further setup.
Environment
Nest version: 4.6.5
The package of @nestjs/common uses multer but there is no mention of it in the package.json.
multer is a dependency of @nestjs/core though, it is however not using the module.
So it seems like there is perhaps a dependency mix-up.
The text was updated successfully, but these errors were encountered:
Current behavior
If I write a module which uses
@nestjs/common
sometimes there is a complaint about themulter
module not being foundExpected behavior
There is no complaint about
multer
.Minimal reproduction of the problem with instructions
What is the motivation / use case for changing the behavior?
Being able to write modules which use
@nestjs/common
without needing any further setup.Environment
The package of
@nestjs/common
usesmulter
but there is no mention of it in the package.json.multer
is a dependency of@nestjs/core
though, it is however not using the module.So it seems like there is perhaps a dependency mix-up.
The text was updated successfully, but these errors were encountered: