fastify 5.1.0 → 5.2.0

package/README.md

@@ -9,7 +9,7 @@
 
 <div align="center">
 
-[![CI](https://github.com/fastify/fastify/actions/workflows/ci.yml/badge.svg)](https://github.com/fastify/fastify/actions/workflows/ci.yml)
+[![CI](https://github.com/fastify/fastify/actions/workflows/ci.yml/badge.svg?branch=main)](https://github.com/fastify/fastify/actions/workflows/ci.yml)
 [![Package Manager
 CI](https://github.com/fastify/fastify/workflows/package-manager-ci/badge.svg?branch=main)](https://github.com/fastify/fastify/actions/workflows/package-manager-ci.yml)
 [![Web
@@ -29,7 +29,7 @@ downloads](https://img.shields.io/npm/dm/fastify.svg?style=flat)](https://www.np
 Disclosure](https://img.shields.io/badge/Security-Responsible%20Disclosure-yellow.svg)](https://github.com/fastify/fastify/blob/main/SECURITY.md)
 [![Discord](https://img.shields.io/discord/725613461949906985)](https://discord.gg/fastify)
 [![Contribute with Gitpod](https://img.shields.io/badge/Contribute%20with-Gitpod-908a85?logo=gitpod&color=blue)](https://gitpod.io/#https://github.com/fastify/fastify)
-![Open Collective backers and sponsors](https://img.shields.io/opencollective/all/fastify)
+[![Open Collective backers and sponsors](https://img.shields.io/opencollective/all/fastify)](https://github.com/sponsors/fastify#sponsors)
 
 </div>
 
@@ -106,14 +106,9 @@ generate functionality of [Fastify CLI](https://github.com/fastify/fastify-cli).
 
 To install Fastify in an existing project as a dependency:
 
-Install with npm:
 ```sh
 npm i fastify
 ```
-Install with yarn:
-```sh
-yarn add fastify
-```
 
 ### Example
 
@@ -266,6 +261,13 @@ application, you should __always__ benchmark if performance matters to you.
 Please visit [Fastify help](https://github.com/fastify/help) to view prior
 support issues and to ask new support questions.
 
+Version 3 of Fastify and lower are EOL and will not receive any security or bug fixes.
+
+Fastify's partner, HeroDevs, provides commercial security fixes for all
+unsupported versions at [https://herodevs.com/support/fastify-nes][hd-link].
+Fastify's supported version matrix is available in the
+[Long Term Support][lts-link] documentation.
+
 ## Contributing
 
 Whether reporting bugs, discussing improvements and new ideas or writing code,
@@ -414,3 +416,6 @@ dependencies:
 - ISC
 - BSD-3-Clause
 - BSD-2-Clause
+
+[hd-link]: https://www.herodevs.com/support/fastify-nes?utm_source=fastify&utm_medium=link&utm_campaign=github_readme
+[lts-link]: https://fastify.dev/docs/latest/Reference/LTS/

package/docs/Guides/Database.md

@@ -2,17 +2,17 @@
 
 ## Database
 
-Fastify's ecosystem provides a handful of 
-plugins for connecting to various database engines. 
-This guide covers engines that have Fastify 
+Fastify's ecosystem provides a handful of
+plugins for connecting to various database engines.
+This guide covers engines that have Fastify
 plugins maintained within the Fastify organization.
 
-> If a plugin for your database of choice does not exist 
-> you can still use the database as Fastify is database agnostic. 
-> By following the examples of the database plugins listed in this guide, 
-> a plugin can be written for the missing database engine. 
+> If a plugin for your database of choice does not exist
+> you can still use the database as Fastify is database agnostic.
+> By following the examples of the database plugins listed in this guide,
+> a plugin can be written for the missing database engine.
 
-> If you would like to write your own Fastify plugin 
+> If you would like to write your own Fastify plugin
 > please take a look at the [plugins guide](./Plugins-Guide.md)
 
 ### [MySQL](https://github.com/fastify/fastify-mysql)
@@ -104,8 +104,8 @@ fastify.listen({ port: 3000 }, err => {
 })
 ```
 
-By default `@fastify/redis` doesn't close 
-the client connection when Fastify server shuts down. 
+By default `@fastify/redis` doesn't close
+the client connection when Fastify server shuts down.
 To opt-in to this behavior, register the client like so:
 
 ```javascript
@@ -126,7 +126,7 @@ fastify.register(require('@fastify/mongodb'), {
   // force to close the mongodb connection when app stopped
   // the default value is false
   forceClose: true,
-  
+
   url: 'mongodb://mongo/mydb'
 })
 
@@ -178,8 +178,8 @@ fastify.listen({ port: 3000 }, err => {
 ```
 
 ### Writing plugin for a database library
-We could write a plugin for a database 
-library too (e.g. Knex, Prisma, or TypeORM). 
+We could write a plugin for a database
+library too (e.g. Knex, Prisma, or TypeORM).
 We will use [Knex](https://knexjs.org/) in our example.
 
 ```javascript
@@ -281,7 +281,7 @@ async function migrate() {
   const client = new pg.Client({
     host: 'localhost',
     port: 5432,
-    database: 'example', 
+    database: 'example',
     user: 'example',
     password: 'example',
   });
@@ -313,7 +313,7 @@ async function migrate() {
     console.error(err)
     process.exitCode = 1
   }
-  
+
   await client.end()
 }
 

package/docs/Guides/Detecting-When-Clients-Abort.md

@@ -4,30 +4,30 @@
 
 ## Introduction
 
-Fastify provides request events to trigger at certain points in a request's 
-lifecycle. However, there isn't a built-in mechanism to 
-detect unintentional client disconnection scenarios such as when the client's 
+Fastify provides request events to trigger at certain points in a request's
+lifecycle. However, there isn't a built-in mechanism to
+detect unintentional client disconnection scenarios such as when the client's
 internet connection is interrupted. This guide covers methods to detect if
 and when a client intentionally aborts a request.
 
-Keep in mind, Fastify's `clientErrorHandler` is not designed to detect when a 
-client aborts a request. This works in the same way as the standard Node HTTP 
-module, which triggers the `clientError` event when there is a bad request or 
-exceedingly large header data. When a client aborts a request, there is no 
+Keep in mind, Fastify's `clientErrorHandler` is not designed to detect when a
+client aborts a request. This works in the same way as the standard Node HTTP
+module, which triggers the `clientError` event when there is a bad request or
+exceedingly large header data. When a client aborts a request, there is no
 error on the socket and the `clientErrorHandler` will not be triggered.
 
 ## Solution
 
 ### Overview
 
-The proposed solution is a possible way of detecting when a client 
-intentionally aborts a request, such as when a browser is closed or the HTTP 
-request is aborted from your client application. If there is an error in your 
-application code that results in the server crashing, you may require 
+The proposed solution is a possible way of detecting when a client
+intentionally aborts a request, such as when a browser is closed or the HTTP
+request is aborted from your client application. If there is an error in your
+application code that results in the server crashing, you may require
 additional logic to avoid a false abort detection.
 
-The goal here is to detect when a client intentionally aborts a connection 
-so your application logic can proceed accordingly. This can be useful for 
+The goal here is to detect when a client intentionally aborts a connection
+so your application logic can proceed accordingly. This can be useful for
 logging purposes or halting business logic.
 
 ### Hands-on
@@ -78,10 +78,10 @@ const start = async () => {
 start()
 ```
 
-Our code is setting up a Fastify server which includes the following 
+Our code is setting up a Fastify server which includes the following
 functionality:
 
-- Accepting requests at http://localhost:3000, with a 3 second delayed response 
+- Accepting requests at http://localhost:3000, with a 3 second delayed response
 of `{ ok: true }`.
 - An onRequest hook that triggers when every request is received.
 - Logic that triggers in the hook when the request is closed.
@@ -108,7 +108,7 @@ app.get('/', async (request, reply) => {
 })
 ```
 
-At any point in your business logic, you can check if the request has been 
+At any point in your business logic, you can check if the request has been
 aborted and perform alternative actions.
 
 ```js
@@ -122,14 +122,14 @@ app.get('/', async (request, reply) => {
 })
 ```
 
-A benefit to adding this in your application code is that you can log Fastify 
-details such as the reqId, which may be unavailable in lower-level code that 
+A benefit to adding this in your application code is that you can log Fastify
+details such as the reqId, which may be unavailable in lower-level code that
 only has access to the raw request information.
 
 ### Testing
 
-To test this functionality you can use an app like Postman and cancel your 
-request within 3 seconds. Alternatively, you can use Node to send an HTTP 
+To test this functionality you can use an app like Postman and cancel your
+request within 3 seconds. Alternatively, you can use Node to send an HTTP
 request with logic to abort the request before 3 seconds. Example:
 
 ```js
@@ -151,7 +151,7 @@ setTimeout(() => {
 }, 1000);
 ```
 
-With either approach, you should see the Fastify log appear at the moment the 
+With either approach, you should see the Fastify log appear at the moment the
 request is aborted.
 
 ## Conclusion
@@ -160,13 +160,13 @@ Specifics of the implementation will vary from one problem to another, but the
 main goal of this guide was to show a very specific use case of an issue that
 could be solved within Fastify's ecosystem.
 
-You can listen to the request close event and determine if the request was 
-aborted or if it was successfully delivered. You can implement this solution 
+You can listen to the request close event and determine if the request was
+aborted or if it was successfully delivered. You can implement this solution
 in an onRequest hook or directly in an individual route.
 
-This approach will not trigger in the event of internet disruption, and such 
-detection would require additional business logic. If you have flawed backend 
-application logic that results in a server crash, then you could trigger a 
-false detection. The `clientErrorHandler`, either by default or with custom 
-logic, is not intended to handle this scenario and will not trigger when the 
+This approach will not trigger in the event of internet disruption, and such
+detection would require additional business logic. If you have flawed backend
+application logic that results in a server crash, then you could trigger a
+false detection. The `clientErrorHandler`, either by default or with custom
+logic, is not intended to handle this scenario and will not trigger when the
 client aborts a request.

package/docs/Guides/Ecosystem.md

@@ -175,6 +175,10 @@ section.
 - [`@ethicdevs/fastify-git-server`](https://github.com/EthicDevs/fastify-git-server)
   A plugin to easily create git server and make one/many Git repositories available
   for clone/fetch/push through the standard `git` (over http) commands.
+- [`@exortek/fastify-mongo-sanitize`](https://github.com/ExorTek/fastify-mongo-sanitize)
+  A Fastify plugin that protects against No(n)SQL injection by sanitizing data.
+- [`@exortek/remix-fastify`](https://github.com/ExorTek/remix-fastify)
+  Fastify plugin for Remix.
 - [`@fastify-userland/request-id`](https://github.com/fastify-userland/request-id)
   Fastify Request ID Plugin
 - [`@fastify-userland/typeorm-query-runner`](https://github.com/fastify-userland/typeorm-query-runner)
@@ -214,9 +218,9 @@ section.
   Beautiful OpenAPI/Swagger API references for Fastify
 - [`@trubavuong/fastify-seaweedfs`](https://github.com/trubavuong/fastify-seaweedfs)
   SeaweedFS for Fastify
-- [`apitally`](https://github.com/apitally/nodejs-client) Fastify plugin to
-  integrate with [Apitally](https://apitally.io), a simple API monitoring &
-  API key management solution.
+- [`apitally`](https://github.com/apitally/apitally-js) Fastify plugin to
+  integrate with [Apitally](https://apitally.io/fastify), an API analytics,
+  logging and monitoring tool.
 - [`arecibo`](https://github.com/nucleode/arecibo) Fastify ping responder for
   Kubernetes Liveness and Readiness Probes.
 - [`aws-xray-sdk-fastify`](https://github.com/aws/aws-xray-sdk-node/tree/master/sdk_contrib/fastify)
@@ -249,7 +253,7 @@ section.
   plugin to authenticate HTTP requests based on API key and signature
 - [`fastify-appwrite`](https://github.com/Dev-Manny/fastify-appwrite) Fastify
   Plugin for interacting with Appwrite server.
-- [`fastify-asyncforge`](https://github.com/mcollina/fastify-asyncforge) Plugin 
+- [`fastify-asyncforge`](https://github.com/mcollina/fastify-asyncforge) Plugin
   to access Fastify instance, logger, request and reply from Node.js [Async
   Local Storage](https://nodejs.org/api/async_context.html#class-asynclocalstorage).
 - [`fastify-at-mysql`](https://github.com/mateonunez/fastify-at-mysql) Fastify
@@ -277,7 +281,7 @@ section.
   development servers that require Babel transformations of JavaScript sources.
 - [`fastify-bcrypt`](https://github.com/beliven-it/fastify-bcrypt) A Bcrypt hash
   generator & checker.
-- [`fastify-better-sqlite3`](https://github.com/punkish/fastify-better-sqlite3) 
+- [`fastify-better-sqlite3`](https://github.com/punkish/fastify-better-sqlite3)
   Plugin for better-sqlite3.
 - [`fastify-blipp`](https://github.com/PavelPolyakov/fastify-blipp) Prints your
   routes to the console, so you definitely know which endpoints are available.
@@ -289,7 +293,7 @@ section.
   to add [bree](https://github.com/breejs/bree) support.
 - [`fastify-bugsnag`](https://github.com/ZigaStrgar/fastify-bugsnag) Fastify plugin
   to add support for [Bugsnag](https://www.bugsnag.com/) error reporting.
-- [`fastify-cacheman`](https://gitlab.com/aalfiann/fastify-cacheman) 
+- [`fastify-cacheman`](https://gitlab.com/aalfiann/fastify-cacheman)
   Small and efficient cache provider for Node.js with In-memory, File, Redis
    and MongoDB engines for Fastify
 - [`fastify-casbin`](https://github.com/nearform/fastify-casbin) Casbin support
@@ -344,7 +348,7 @@ section.
 - [`fastify-event-bus`](https://github.com/Shiva127/fastify-event-bus) Event bus
   support for Fastify. Built upon [js-event-bus](https://github.com/bcerati/js-event-bus).
 - [`fastify-evervault`](https://github.com/Briscoooe/fastify-evervault/) Fastify
-  plugin for instantiating and encapsulating the 
+  plugin for instantiating and encapsulating the
   [Evervault](https://evervault.com/) client.
 - [`fastify-explorer`](https://github.com/Eomm/fastify-explorer) Get control of
   your decorators across all the encapsulated contexts.
@@ -538,6 +542,8 @@ middlewares into Fastify plugins
   OSM plugin to run overpass queries by OpenStreetMap.
 - [`fastify-override`](https://github.com/matthyk/fastify-override)
   Fastify plugin to override decorators, plugins and hooks for testing purposes
+- [`fastify-passkit-webservice`](https://github.com/alexandercerutti/fastify-passkit-webservice)
+  A set of Fastify plugins to integrate Apple Wallet Web Service specification
 - [`fastify-peekaboo`](https://github.com/simone-sanfratello/fastify-peekaboo)
   Fastify plugin for memoize responses by expressive settings.
 - [`fastify-piscina`](https://github.com/piscinajs/fastify-piscina) A worker

package/docs/Guides/Index.md

@@ -15,7 +15,7 @@ This table of contents is in alphabetical order.
   met in your application. This guide focuses on solving the problem using
   [`Hooks`](../Reference/Hooks.md), [`Decorators`](../Reference/Decorators.md),
   and [`Plugins`](../Reference/Plugins.md).
-+ [Detecting When Clients Abort](./Detecting-When-Clients-Abort.md): A 
++ [Detecting When Clients Abort](./Detecting-When-Clients-Abort.md): A
   practical guide on detecting if and when a client aborts a request.
 + [Ecosystem](./Ecosystem.md): Lists all core plugins and many known community
   plugins.

package/docs/Guides/Migration-Guide-V4.md

@@ -9,13 +9,13 @@ work after upgrading.
 ## Codemods
 ### Fastify v4 Codemods
 
-To help with the upgrade, we’ve worked with the team at 
+To help with the upgrade, we’ve worked with the team at
 [Codemod](https://github.com/codemod-com/codemod) to
-publish codemods that will automatically update your code to many of 
+publish codemods that will automatically update your code to many of
 the new APIs and patterns in Fastify v4.
 
-Run the following 
-[migration recipe](https://go.codemod.com/fastify-4-migration-recipe) to 
+Run the following
+[migration recipe](https://go.codemod.com/fastify-4-migration-recipe) to
 automatically update your code to Fastify v4:
 
 ```
@@ -30,7 +30,7 @@ This will run the following codemods:
 - [`fastify/4/await-register-calls`](https://go.codemod.com/fastify-4-await-register-calls)
 
 Each of these codemods automates the changes listed in the v4 migration guide.
-For a complete list of available Fastify codemods and further details, 
+For a complete list of available Fastify codemods and further details,
 see [Codemod Registry](https://go.codemod.com/fastify).
 
 
@@ -52,14 +52,14 @@ fastify.register(async fastify => {
     console.log(err.message) // 'kaboom'
     throw new Error('caught')
   })
-  
+
   fastify.get('/encapsulated', async () => {
     throw new Error('kaboom')
   })
 })
 
 fastify.setErrorHandler(async err => {
-  console.log(err.message) // 'caught' 
+  console.log(err.message) // 'caught'
   throw new Error('wrapped')
 })
 
@@ -67,10 +67,10 @@ const res = await fastify.inject('/encapsulated')
 console.log(res.json().message) // 'wrapped'
 ```
 
->The root error handler is Fastify’s generic error handler. 
->This error handler will use the headers and status code in the Error object, 
+>The root error handler is Fastify’s generic error handler.
+>This error handler will use the headers and status code in the Error object,
 >if they exist. **The headers and status code will not be automatically set if
->a custom error handler is provided**. 
+>a custom error handler is provided**.
 
 ### Removed `app.use()` ([#3506](https://github.com/fastify/fastify/pull/3506))
 
@@ -242,7 +242,7 @@ As such, schemas like below will need to be changed from:
   properties: {
     api_key: { type: 'string' },
     image: { type: ['object', 'array'] }
-  } 
+  }
 }
 ```
 

package/docs/Guides/Migration-Guide-V5.md

@@ -159,7 +159,7 @@ the following:
 +++ b/index.ts
 @@ -11,7 +11,8 @@ import {
  import { FromSchema, FromSchemaDefaultOptions, FromSchemaOptions, JSONSchema } from 'json-schema-to-ts'
- 
+
  export interface JsonSchemaToTsProvider<
    Options extends FromSchemaOptions = FromSchemaDefaultOptions
  > extends FastifyTypeProvider {
@@ -298,7 +298,7 @@ use the `constraints` option instead.
 We have a more strict requirement for custom `HEAD` route when
 `exposeHeadRoutes: true`.
 
-When you provides a custom `HEAD` route, you must either explicitly 
+When you provides a custom `HEAD` route, you must either explicitly
 set `exposeHeadRoutes` to `false`
 
 ```js
@@ -403,7 +403,7 @@ and requires the route definition to be passed as it is defined in the route.
 fastify.get('/example/:file(^\\d+).png', function (request, reply) { })
 
 console.log(fastify.hasRoute({
-  method: 'GET', 
+  method: 'GET',
   url: '/example/12345.png'
 )); // true
 ```
@@ -414,7 +414,7 @@ console.log(fastify.hasRoute({
 fastify.get('/example/:file(^\\d+).png', function (request, reply) { })
 
 console.log(fastify.hasRoute({
-  method: 'GET', 
+  method: 'GET',
   url: '/example/:file(^\\d+).png'
 )); // true
 ```
@@ -480,7 +480,7 @@ or as a getter
 ```js
 // v5
 fastify.decorateRequest('myObject', {
-  getter () { 
+  getter () {
     return { hello: 'world' }
   }
 });

package/docs/Guides/Plugins-Guide.md

@@ -316,7 +316,7 @@ based on a [route config option](../Reference/Routes.md#routes-options):
 ```js
 fastify.register((instance, opts, done) => {
   instance.decorate('util', (request, key, value) => { request[key] = value })
-  
+
   function handler(request, reply, done) {
     instance.util(request, 'timestamp', new Date())
     done()

package/docs/Guides/Prototype-Poisoning.md

@@ -8,7 +8,7 @@
 <a id="pp"></a>
 
 Based on the article by Eran Hammer,the issue is created by a web security bug.
-It is also a perfect illustration of the efforts required to maintain 
+It is also a perfect illustration of the efforts required to maintain
 open-source software and the limitations of existing communication channels.
 
 But first, if we use a JavaScript framework to process incoming JSON data, take
@@ -16,7 +16,7 @@ a moment to read up on [Prototype Poisoning](https://medium.com/intrinsic/javasc
 in general, and the specific
 [technical details](https://github.com/hapijs/hapi/issues/3916) of this issue.
 This could be a critical issue so, we might need to verify your own code first.
-It focuses on specific framework however, any solution that uses `JSON.parse()` 
+It focuses on specific framework however, any solution that uses `JSON.parse()`
 to process external data is potentially at risk.
 
 ### BOOM
@@ -42,7 +42,7 @@ defect a validation library can have.
 
 To understand this, we need to understand how JavaScript works a bit.
 Every object in JavaScript can have a prototype. It is a set of methods and
-properties it "inherits" from another object. I have put inherits in quotes 
+properties it "inherits" from another object. I have put inherits in quotes
 because JavaScript isn't really an object-oriented language. It is a prototype-
 based object-oriented language.
 

package/docs/Guides/Recommendations.md

@@ -307,22 +307,22 @@ readinessProbe:
 ## Capacity Planning For Production
 <a id="capacity"></a>
 
-In order to rightsize the production environment for your Fastify application, 
-it is highly recommended that you perform your own measurements against 
+In order to rightsize the production environment for your Fastify application,
+it is highly recommended that you perform your own measurements against
 different configurations of the environment, which may
 use real CPU cores, virtual CPU cores (vCPU), or even fractional
 vCPU cores. We will use the term vCPU throughout this
 recommendation to represent any CPU type.
 
-Tools such as [k6](https://github.com/grafana/k6) 
+Tools such as [k6](https://github.com/grafana/k6)
 or [autocannon](https://github.com/mcollina/autocannon) can be used for
 conducting the necessary performance tests.
 
 That said, you may also consider the following as a rule of thumb:
 
-* To have the lowest possible latency, 2 vCPU are recommended per app 
-instance (e.g., a k8s pod). The second vCPU will mostly be used by the 
-garbage collector (GC) and libuv threadpool. This will minimize the latency 
+* To have the lowest possible latency, 2 vCPU are recommended per app
+instance (e.g., a k8s pod). The second vCPU will mostly be used by the
+garbage collector (GC) and libuv threadpool. This will minimize the latency
 for your users, as well as the memory usage, as the GC will be run more
 frequently. Also, the main thread won't have to stop to let the GC run.
 
@@ -330,7 +330,7 @@ frequently. Also, the main thread won't have to stop to let the GC run.
 requests per second per vCPU available), consider using a smaller amount of vCPUs
 per app instance. It is totally fine to run Node.js applications with 1 vCPU.
 
-* You may experiment with an even smaller amount of vCPU, which may provide 
+* You may experiment with an even smaller amount of vCPU, which may provide
 even better throughput in certain use-cases. There are reports of API gateway
 solutions working well with 100m-200m vCPU in Kubernetes.
 
@@ -347,7 +347,7 @@ would be exposing metrics endpoints on a separate port,
 to prevent public access, when using a reverse proxy or an ingress
 firewall is not an option.
 
-It is perfectly fine to spin up several Fastify instances within the same 
-Node.js process and run them concurrently, even in high load systems. 
+It is perfectly fine to spin up several Fastify instances within the same
+Node.js process and run them concurrently, even in high load systems.
 Each Fastify instance only generates as much load as the traffic it receives,
 plus the memory used for that Fastify instance.

package/docs/Guides/Serverless.md

@@ -36,10 +36,10 @@ snippet of code.
 
 To integrate with AWS, you have two choices of library:
 
-- Using [@fastify/aws-lambda](https://github.com/fastify/aws-lambda-fastify) 
+- Using [@fastify/aws-lambda](https://github.com/fastify/aws-lambda-fastify)
   which only adds API Gateway support but has heavy optimizations for fastify.
-- Using [@h4ad/serverless-adapter](https://github.com/H4ad/serverless-adapter) 
-  which is a little slower as it creates an HTTP request for each AWS event but 
+- Using [@h4ad/serverless-adapter](https://github.com/H4ad/serverless-adapter)
+  which is a little slower as it creates an HTTP request for each AWS event but
   has support for more AWS services such as: AWS SQS, AWS SNS and others.
 
 So you can decide which option is best for you, but you can test both libraries.
@@ -263,7 +263,7 @@ curl -X POST https://$GOOGLE_REGION-$GOOGLE_PROJECT.cloudfunctions.net/me \
 
 ## Google Firebase Functions
 
-Follow this guide if you want to use Fastify as the HTTP framework for 
+Follow this guide if you want to use Fastify as the HTTP framework for
 Firebase Functions instead of the vanilla JavaScript router provided with
 `onRequest(async (req, res) => {}`.
 
@@ -280,7 +280,7 @@ const { onRequest } = require("firebase-functions/v2/https")
 ### Creation of Fastify instance
 
 Create the Fastify instance and encapsulate the returned application instance
-in a function which will register routes, await the server's processing of 
+in a function which will register routes, await the server's processing of
 plugins, hooks and other settings. As follows:
 
 ```js

package/docs/Guides/Testing.md

@@ -264,7 +264,7 @@ test('should work with undici', async t => {
     'http://localhost:' + fastify.server.address().port, {
       keepAliveTimeout: 10,
       keepAliveMaxTimeout: 10
-    } 
+    }
   )
 
   t.after(() => {
@@ -279,8 +279,8 @@ test('should work with undici', async t => {
 })
 ```
 
-Alternatively, starting with Node.js 18, 
-[`fetch`](https://nodejs.org/docs/latest-v18.x/api/globals.html#fetch) 
+Alternatively, starting with Node.js 18,
+[`fetch`](https://nodejs.org/docs/latest-v18.x/api/globals.html#fetch)
 may be used without requiring any extra dependencies:
 
 **test-listen.js**
@@ -296,7 +296,7 @@ test('should work with fetch', async t => {
   t.after(() => fastify.close())
 
   await fastify.listen()
-  
+
   const response = await fetch(
     'http://localhost:' + fastify.server.address().port
   )
@@ -386,7 +386,7 @@ test("Test the Plugin Route", async t => {
 
     fastify.register(myPlugin)
 
-    // Add an endpoint of your choice 
+    // Add an endpoint of your choice
     fastify.get("/", async (request, reply) => {
         return ({ message: request.helloRequest })
     })
@@ -396,7 +396,7 @@ test("Test the Plugin Route", async t => {
         method: "GET",
         url: "/"
     })
-    
+
   console.log('status code: ', fastifyResponse.statusCode)
   console.log('body: ', fastifyResponse.body)
 })
@@ -440,7 +440,7 @@ test("Test the Plugin Route", async t => {
         method: "GET",
         url: "/"
     })
-    
+
     t.assert.strictEqual(fastifyResponse.statusCode, 200)
     t.assert.deepStrictEqual(JSON.parse(fastifyResponse.body), { message: "Hello World" })
 })
@@ -465,7 +465,7 @@ test("Test the Plugin Route", async t => {
 
     fastify.get("/", async (request, reply) => {
         // Testing the fastify decorators
-        t.assert.ifError(request.helloRequest) 
+        t.assert.ifError(request.helloRequest)
         t.assert.ok(request.helloRequest, "Hello World")
         t.assert.ok(fastify.helloInstance, "Hello Fastify Instance")
         return ({ message: request.helloRequest })

package/docs/Guides/Write-Plugin.md

@@ -63,7 +63,7 @@ among different versions of its dependencies.
 We do not enforce any testing library. We use [`node:test`](https://nodejs.org/api/test.html)
 since it offers out-of-the-box parallel testing and code coverage, but it is up
 to you to choose your library of preference.
-We highly recommend you read the [Plugin Testing](./Testing.md#plugins) to 
+We highly recommend you read the [Plugin Testing](./Testing.md#plugins) to
 learn about how to test your plugins.
 
 ## Code Linter

package/docs/Guides/Write-Type-Provider.md

@@ -10,9 +10,9 @@ Whereas exhaustive type narrowing checks normally rely on `never` to represent
 an unreachable state, reduction in type provider interfaces should only be done
 up to `unknown`.
 
-The reasoning is that certain methods of `FastifyInstance` are 
-contravariant on `TypeProvider`, which can lead to TypeScript surfacing 
-assignability issues unless the custom type provider interface is 
+The reasoning is that certain methods of `FastifyInstance` are
+contravariant on `TypeProvider`, which can lead to TypeScript surfacing
+assignability issues unless the custom type provider interface is
 substitutable with `FastifyTypeProviderDefault`.
 
 For example, `FastifyTypeProviderDefault` will not be assignable to the following:

package/docs/Reference/Decorators.md

@@ -59,7 +59,7 @@ close as possible to the value intended to be set dynamically in the future.
 Initialize a decorator as a `''` if the intended value is a string, and as
 `null` if it will be an object or a function.
 
-Remember this example works only with value types as reference types will 
+Remember this example works only with value types as reference types will
 thrown and error during the fastify startup. See [decorateRequest](#decorate-request).
 
 See [JavaScript engine fundamentals: Shapes and Inline
@@ -109,7 +109,7 @@ fastify.decorate('db', new DbConnection())
 fastify.get('/', async function (request, reply) {
   // using return
   return { hello: await this.db.query('world') }
-  
+
   // or
   // using reply.send()
   reply.send({ hello: await this.db.query('world') })