This plugin is now compatible with Fastify 5, where request.routeConfig has been removed.
ref: https://fastify.dev/docs/latest/Guides/Migration-Guide-V5/#streamlined-access-to-route-definition

And does it throw an error if it does an access on that attribute? Or why do you state that this PR ensures compatility with fastify v5?

That fallback is no longer reached. If remove /* c8 ignore next */, test coverage will not be 100%. because that property has been removed and use request.routeOptions.config instead

So the answer to my question regarding "compatibiity" to fastify v5 is no and currently the plugins works without issues in v5.

@fastify/plugins
I think we can accept this PR. Currently the plugin is maybe working with fastify v4. We documented already, that v8 is only supporting fastify v5. So even if it breaks in userland, we can refer to the fact, that we already documented that we drop the support of fasstify v4.

I think we'd just need to do a major if dropping support for Fastify v4, and then updating the compatibility table accordingly.

It looks like this plugin now requires Fastify v5

It looks like this plugin now requires Fastify v5

fastify-static/index.js

Lines 542 to 545 in c4185a5

	module.exports = fp(fastifyStatic, {
	fastify: '5.x',
	name: '@fastify/static'
	})

Ah, good spot, thanks @inyourtime! Was looking at the compatibility table which was wrong. In that case, happy with this PR!

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.