Multer options neglected when using MulterModule like on the docs.

I’m submitting a…

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

Current behavior

I followed the File Upload async configuration documentation

Expected behavior

Multer options should work, uploading a file exceeding the limit should not work, and I should see the log from fileFilter function each time I do an upload.

Minimal reproduction of the problem with instructions

The app module app.module.ts:

@Module({
  imports: [
    MulterModule.registerAsync({
      imports: [ConfigModule],
      useFactory: async (config: ConfigService) => ({
        fileFilter: (req, file, cb) => {
          console.log('********************', config.get('FILE_SIZE_LIMIT'));
          cb(null, true);
        },
        limits: {
          fileSize: config.get('FILE_SIZE_LIMIT'),
        },
      }),
      inject: [ConfigService],
    }),
  ]
})

The controller controller.ts

@Controller('upload')
export class FilesController {
  constructor(private readonly config: ConfigService) {}
  @Post()
  @UseInterceptors(FileInterceptor('file'))
  upload(@UploadedFile() file) {
    console.log(file);
    return 'Okay';
  }
}

When having multer options as the second argument of FileInterceptor everything works fine, but when using MulterModule just like on the docs, the options are neglected.

Environment

Nest version: 6.1.1
 
For Tooling issues:
- Node version: 10.15.3
- Platform:  Linux

[ExpDev07]

I ran into a similar issue. I was trying to register multer in AppModule, but expected the settings there to be used in a feature module. The multer options get consumed while the feature module is being created, so anything set in the AppModule is ignored. Not sure if this is by design or a bug, but moving the multer module import to the feature module fixed it for me.

Can we get an update on this? I just ran into it as an issue. Seems like this is something that you’d only want to define at the AppModule like with database and not need to copy into every module where you’ll use multer?

[brianmcd]

I ran into a similar issue. I was trying to register multer in AppModule, but expected the settings there to be used in a feature module. The multer options get consumed while the feature module is being created, so anything set in the AppModule is ignored. Not sure if this is by design or a bug, but moving the multer module import to the feature module fixed it for me.