fix(testing): add fallback option to file type validator

[Yasir-Rafique]

PR Checklist

Please check if your PR fulfills the following requirements:

• 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

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Other... Please describe:

What is the current behavior?

Currently, the FileTypeValidator fails when file-type is unable to determine the MIME type — particularly for file formats with undetectable signatures. This can cause valid uploads to fail unexpectedly.

Additionally, the related unit test did not cover scenarios involving fallback logic or validator option validation.

Issue Number: #15055

What is the new behavior?

• Added mimeTypeFallback support to the FileTypeValidator to allow more resilient handling when file-type cannot detect MIME.
• Improved the test case in parse-file-pipe.builder.spec.ts to assert that validator options (including mimeTypeFallback) are properly passed and used.
• Updated package.json:
• Downgraded redis from v5 (ESM-only) to ^4.7.1 for compatibility.
• Moved redis from devDependencies to dependencies.
• Ensured backwards compatibility with existing file validation logic.

Does this PR introduce a breaking change?

• Yes
• No

Other information

This PR resolves compatibility issues related to MIME type detection and improves developer experience by making file validation more fault-tolerant in real-world uploads. It also keeps dependencies aligned with current CommonJS-based usage patterns.

[coveralls]

Pull Request Test Coverage Report for Build 789e8c93-ab4a-4bca-86db-21c38176ac58

Details

• 2 of 2 (100.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.001%) to 88.919%

---

Totals
Change from base Build 2a845090-0b42-4092-81ff-64987c934f5c:	0.001%
Covered Lines:	7198
Relevant Lines:	8095

---

💛 - Coveralls

[Yasir-Rafique]

All conflicts have been resolved, and checks are passing. Ready for review

[itrethan]

It seems it's approved but conflict remains, can you please resolve the merge?

[itrethan]

why there is a redis dependency?

[Yasir-Rafique]

Thank you @itrethan for pointing that out. The redis dependency was added unintentionally during local development and should not have been included in this PR. It is unrelated to the scope of this fix.

I'll remove it immediately to keep the PR focused and clean.

[Yasir-Rafique]

I’ve just resolved the merge conflict and pulled the latest changes. After doing so, I encountered some new issues during the integration tests:

• ESLint errors surfaced in a few files (e.g., formatting issues in the snapshot test).
• Additionally, the code benchmark check failed, though that seems unrelated to the changes in this PR.

The failing integration test is related to the snapshot comparison, although I haven’t modified any relevant logic or snapshots directly. Do you have any suggestions on how to proceed with this?