refactor(fastify): update fastify static options interface

[Tony133]

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?

Issue Number: N/A

What is the new behavior?

Proposal:

• Refactor fastify-static-options.interface.ts, see here for other info: https://github.com/fastify/fastify-static/blob/master/types/index.d.ts

Does this PR introduce a breaking change?

• Yes
• No

Other information

[coveralls]

Pull Request Test Coverage Report for Build dc6e204c-b705-4972-a5da-ae32f0647ea0

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 6 unchanged lines in 3 files lost coverage.
• Overall coverage decreased (-0.03%) to 92.213%

---

Files with Coverage Reduction	New Missed Lines	%
packages/common/pipes/validation.pipe.ts	1	94.34%
packages/core/inspector/initialize-on-preview.allowlist.ts	1	75.0%
packages/core/injector/internal-core-module/internal-core-module-factory.ts	4	80.0%

Totals
Change from base Build 72f148bc-4145-44b3-a3c4-06a616307114:	-0.03%
Covered Lines:	6750
Relevant Lines:	7320

---

💛 - Coveralls

[kamilmysliwiec]

Was it added in the latest version (that is not yet compatible with Nest)?

[Tony133]

Was it added in the latest version (that is not yet compatible with Nest)?

With the new version of Fastify 5.x, a small change has been made to the interface, see here : fastify/fastify-static@426f3be#diff-093ad82a25aee498b11febf1cdcb6546e4d223ffcb49ed69cc275ac27ce0ccceL80
The version of the @fastify/static package released for Fastify 5.x and v8.0.0, is now v8.0.2

[kamilmysliwiec]

So if that's the case, shouldn't we target the 11.0.0 branch instead of master?

[Tony133]

So if that's the case, shouldn't we target the 11.0.0 branch instead of master?

I think we can also merge it into v10.x only that that small change was made in the new version of the @fastify/static v8.0.0 package which is only compatible with fastify v5.x, at best I can remove it and make a separate PR with that small change.