fastify 5.2.1 → 5.3.0

package/LICENSE

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2016-2024 The Fastify Team
+Copyright (c) 2016-2025 The Fastify Team
 
 The Fastify team members are listed at https://github.com/fastify/fastify#team
 and in the README file.

package/PROJECT_CHARTER.md

@@ -1,6 +1,6 @@
 # Fastify Charter
 
-The Fastify project aims to build a fast and low overhead web framework for
+The Fastify project aims to build a fast and low-overhead web framework for
 Node.js.
 
 
@@ -20,7 +20,7 @@ experience with the least overhead and a plugin architecture.
 ### 1.1: In-scope
 
 + Develop a web framework for Node.js with a focus on developer experience,
-  performance and extensibility.
+  performance, and extensibility.
 + Plugin Architecture
 + Support web protocols
 + Official plugins for common user requirements
@@ -43,7 +43,7 @@ experience with the least overhead and a plugin architecture.
 
 + Support versions of Node.js at EOL (end of life) stage
 + Support serverless architecture
-+ Contributions that violates the [Code of Conduct](CODE_OF_CONDUCT.md)
++ Contributions that violate the [Code of Conduct](CODE_OF_CONDUCT.md)
 
 
 ## Section 2: Relationship with OpenJS Foundation CPC.
@@ -58,10 +58,10 @@ the Board of Directors (the "Board").
 This Fastify Charter reflects a carefully constructed balanced role for the
 Collaborators and the CPC in the governance of the OpenJS Foundation. The
 charter amendment process is for the Fastify Collaborators to propose change
-using simple majority of the full Fastify Organization, the proposed changes
+using a majority of the full Fastify Organization, the proposed changes
 being subject to review and approval by the CPC. The CPC may additionally make
 amendments to the Collaborators charter at any time, though the CPC will not
-interfere with day-to-day discussions, votes or meetings of the Fastify
+interfere with day-to-day discussions, votes, or meetings of the Fastify
 Organization.
 
 
@@ -92,7 +92,7 @@ Section Intentionally Left Blank
 Fastify's features can be discussed in GitHub issues and/or projects. Consensus
 on a discussion is reached when there is no objection by any collaborators.
 
-Whenever there is not consensus, Lead Maintainers will have final say on the
+When there is no consensus, Lead Maintainers will have the final say on the
 topic.
 
 **Voting, and/or Elections**
@@ -112,7 +112,7 @@ Section Intentionally Left Blank
   Foundation Board.
 
 + *Collaborators*: contribute code and other artifacts, have the right to commit
-  to the code base and release plugins projects. Collaborators follow the
+  to the code base, and release plugin projects. Collaborators follow the
   [CONTRIBUTING](CONTRIBUTING.md) guidelines to manage the project. A
   Collaborator could be encumbered by other Fastify Collaborators and never by
   the CPC or OpenJS Foundation Board.

package/README.md

@@ -11,9 +11,9 @@
 
 [![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)
+CI](https://github.com/fastify/fastify/actions/workflows/package-manager-ci.yml/badge.svg?branch=main)](https://github.com/fastify/fastify/actions/workflows/package-manager-ci.yml)
 [![Web
-SIte](https://github.com/fastify/fastify/workflows/website/badge.svg?branch=main)](https://github.com/fastify/fastify/actions/workflows/website.yml)
+site](https://github.com/fastify/fastify/actions/workflows/website.yml/badge.svg?branch=main)](https://github.com/fastify/fastify/actions/workflows/website.yml)
 [![neostandard javascript style](https://img.shields.io/badge/code_style-neostandard-brightgreen?style=flat)](https://github.com/neostandard/neostandard)
 [![CII Best Practices](https://bestpractices.coreinfrastructure.org/projects/7585/badge)](https://bestpractices.coreinfrastructure.org/projects/7585)
 
@@ -35,10 +35,10 @@ Disclosure](https://img.shields.io/badge/Security-Responsible%20Disclosure-yello
 
 <br />
 
-An efficient server implies a lower cost of the infrastructure, a better
-responsiveness under load and happy users. How can you efficiently handle the
+An efficient server implies a lower cost of the infrastructure, better
+responsiveness under load, and happy users. How can you efficiently handle the
 resources of your server, knowing that you are serving the highest number of
-requests as possible, without sacrificing security validations and handy
+requests possible, without sacrificing security validations and handy
 development?
 
 Enter Fastify. Fastify is a web framework highly focused on providing the best
@@ -46,7 +46,7 @@ developer experience with the least overhead and a powerful plugin architecture.
 It is inspired by Hapi and Express and as far as we know, it is one of the
 fastest web frameworks in town.
 
-The `main` branch refers to the Fastify `v5` release, which is not released/LTS yet.
+The `main` branch refers to the Fastify `v5` release.
 Check out the [`4.x` branch](https://github.com/fastify/fastify/tree/4.x) for `v4`.
 
 ### Table of Contents
@@ -138,7 +138,7 @@ fastify.listen({ port: 3000 }, (err, address) => {
 })
 ```
 
-with async-await:
+With async-await:
 
 ```js
 // ESM
@@ -165,13 +165,14 @@ fastify.listen({ port: 3000 }, (err, address) => {
 
 Do you want to know more? Head to the <a
 href="./docs/Guides/Getting-Started.md"><code><b>Getting Started</b></code></a>.
+If you learn best by reading code, explore the official [demo](https://github.com/fastify/demo).
 
 > ## Note
 > `.listen` binds to the local host, `localhost`, interface by default
 > (`127.0.0.1` or `::1`, depending on the operating system configuration). If
 > you are running Fastify in a container (Docker,
 > [GCP](https://cloud.google.com/), etc.), you may need to bind to `0.0.0.0`. Be
-> careful when deciding to listen on all interfaces; it comes with inherent
+> careful when listening on all interfaces; it comes with inherent
 > [security
 > risks](https://web.archive.org/web/20170711105010/https://snyk.io/blog/mongodb-hack-and-secure-defaults/).
 > See [the documentation](./docs/Reference/Server.md#listen) for more
@@ -182,16 +183,16 @@ href="./docs/Guides/Getting-Started.md"><code><b>Getting Started</b></code></a>.
 - **Highly performant:** as far as we know, Fastify is one of the fastest web
   frameworks in town, depending on the code complexity we can serve up to 76+
   thousand requests per second.
-- **Extensible:** Fastify is fully extensible via its hooks, plugins and
+- **Extensible:** Fastify is fully extensible via its hooks, plugins, and
   decorators.
-- **Schema based:** even if it is not mandatory we recommend to use [JSON
+- **Schema-based:** even if it is not mandatory we recommend using [JSON
   Schema](https://json-schema.org/) to validate your routes and serialize your
-  outputs, internally Fastify compiles the schema in a highly performant
+  outputs. Internally Fastify compiles the schema in a highly performant
   function.
 - **Logging:** logs are extremely important but are costly; we chose the best
   logger to almost remove this cost, [Pino](https://github.com/pinojs/pino)!
 - **Developer friendly:** the framework is built to be very expressive and help
-  the developer in their daily use, without sacrificing performance and
+  developers in their daily use without sacrificing performance and
   security.
 
 ### Benchmarks
@@ -211,10 +212,10 @@ second average
 | -                  |                            |              |               |
 | `http.Server`      | 16.14.2	                  | &#10007;     | 74,513        |
 
-Benchmarks taken using https://github.com/fastify/benchmarks. This is a
-synthetic, "hello world" benchmark that aims to evaluate the framework overhead.
+These benchmarks taken using https://github.com/fastify/benchmarks. This is a
+synthetic "hello world" benchmark that aims to evaluate the framework overhead.
 The overhead that each framework has on your application depends on your
-application, you should __always__ benchmark if performance matters to you.
+application. You should __always__ benchmark if performance matters to you.
 
 ## Documentation
 * [__`Getting Started`__](./docs/Guides/Getting-Started.md)
@@ -244,13 +245,11 @@ application, you should __always__ benchmark if performance matters to you.
 * [__`Serverless`__](./docs/Guides/Serverless.md)
 * [__`Recommendations`__](./docs/Guides/Recommendations.md)
 
-中文文档[地址](https://github.com/fastify/docs-chinese/blob/HEAD/README.md)
-
 ## Ecosystem
 
 - [Core](./docs/Guides/Ecosystem.md#core) - Core plugins maintained by the
   _Fastify_ [team](#team).
-- [Community](./docs/Guides/Ecosystem.md#community) - Community supported
+- [Community](./docs/Guides/Ecosystem.md#community) - Community-supported
   plugins.
 - [Live Examples](https://github.com/fastify/example) - Multirepo with a broad
   set of real working examples.
@@ -270,7 +269,7 @@ Fastify's supported version matrix is available in the
 
 ## Contributing
 
-Whether reporting bugs, discussing improvements and new ideas or writing code,
+Whether reporting bugs, discussing improvements and new ideas, or writing code,
 we welcome contributions from anyone and everyone. Please read the [CONTRIBUTING](./CONTRIBUTING.md)
 guidelines before submitting pull requests.
 
@@ -345,9 +344,9 @@ listed in alphabetical order.
   <https://twitter.com/manueomm>, <https://www.npmjs.com/~eomm>
 
 ### Emeritus Contributors
-Great contributors on a specific area in the Fastify ecosystem will be invited
+Great contributors to a specific area of the Fastify ecosystem will be invited
 to join this group by Lead Maintainers when they decide to step down from the
-active contributors group.
+active contributor's group.
 
 * [__Tommaso Allevi__](https://github.com/allevo),
   <https://twitter.com/allevitommaso>, <https://www.npmjs.com/~allevo>
@@ -383,7 +382,7 @@ active contributors group.
 src="https://github.com/openjs-foundation/artwork/blob/main/openjs_foundation/openjs_foundation-logo-horizontal-color.png?raw=true"
 width="250px;"/>](https://openjsf.org/projects)
 
-We are a [At-Large
+We are an [At-Large
 Project](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/PROJECT_PROGRESSION.md#at-large-projects)
 in the [OpenJS Foundation](https://openjsf.org/).
 
@@ -393,7 +392,7 @@ Support this project by becoming a [SPONSOR](./SPONSORS.md)!
 Fastify has an [Open Collective](https://opencollective.com/fastify)
 page where we accept and manage financial contributions.
 
-## Acknowledgements
+## Acknowledgments
 
 This project is kindly sponsored by:
 - [NearForm](https://nearform.com)
@@ -402,8 +401,8 @@ This project is kindly sponsored by:
 Past Sponsors:
 - [LetzDoIt](https://www.letzdoitapp.com/)
 
-This list includes all companies that support one or more of the team members
-in the maintenance of this project.
+This list includes all companies that support one or more team members
+in maintaining this project.
 
 ## License
 

package/SPONSORS.md

@@ -16,6 +16,7 @@ _Be the first!_
 - [Mercedes-Benz Group](https://github.com/mercedes-benz)
 - [Val Town, Inc.](https://opencollective.com/valtown)
 - [Handsontable - JavaScript Data Grid](https://handsontable.com/docs/react-data-grid/?utm_source=Fastify_GH&utm_medium=sponsorship&utm_campaign=library_sponsorship_2024)
+- [Lokalise - A Localization and Translation Software Tool](https://lokalise.com/?utm_source=Fastify_GH&utm_medium=sponsorship)
 
 ## Tier 2
 

package/docs/Guides/Benchmarking.md

@@ -1,17 +1,17 @@
 <h1 align="center">Fastify</h1>
 
 ## Benchmarking
-Benchmarking is important if you want to measure how a change can affect the
-performance of your application. We provide a simple way to benchmark your
+Benchmarking is important if you want to measure how a change can affect your
+application's performance. We provide a simple way to benchmark your
 application from the point of view of a user and contributor. The setup allows
 you to automate benchmarks in different branches and on different Node.js
 versions.
 
 The modules we will use:
-- [Autocannon](https://github.com/mcollina/autocannon): A HTTP/1.1 benchmarking
+- [Autocannon](https://github.com/mcollina/autocannon): An HTTP/1.1 benchmarking
   tool written in node.
 - [Branch-comparer](https://github.com/StarpTech/branch-comparer): Checkout
-  multiple git branches, execute scripts and log the results.
+  multiple git branches, execute scripts, and log the results.
 - [Concurrently](https://github.com/kimmobrunfeldt/concurrently): Run commands
   concurrently.
 - [Npx](https://github.com/npm/npx): NPM package runner used to run scripts

package/docs/Guides/Database.md

@@ -245,7 +245,7 @@ for Postgres, MySQL, SQL Server and SQLite. For MongoDB migrations, please check
 #### [Postgrator](https://www.npmjs.com/package/postgrator)
 
 Postgrator is Node.js SQL migration tool that uses a directory of SQL scripts to
-alter the database schema. Each file in a migrations folder need to follow the
+alter the database schema. Each file in a migrations folder needs to follow the
 pattern: ` [version].[action].[optional-description].sql`.
 
 **version:** must be an incrementing number (e.g. `001` or a timestamp).

package/docs/Guides/Delay-Accepting-Requests.md

@@ -77,8 +77,8 @@ server.get('/ping', function (request, reply) {
 })
 
 server.post('/webhook', function (request, reply) {
-  // It's good practice to validate webhook requests really come from
-  // whoever you expect. This is skipped in this sample for the sake
+  // It's good practice to validate webhook requests come from
+  // who you expect. This is skipped in this sample for the sake
   // of simplicity
 
   const { magicKey } = request.body
@@ -448,10 +448,10 @@ have the possibility of giving the customer meaningful information, like how
 long they should wait before retrying the request. Going even further, by
 issuing a [`503` status
 code](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/503) we're
-signaling to our infrastructure components (namely load balancers) we're still
-not ready to take incoming requests and they should redirect traffic to other
-instances, if available, besides in how long we estimate that will be solved.
-All of that in a few simple lines!
+signaling to our infrastructure components (namely load balancers) that we're
+still not ready to take incoming requests and they should redirect traffic to
+other instances, if available. Additionally, we are providing a `Retry-After`
+header with the time in milliseconds the client should wait before retrying.
 
 It's noteworthy that we didn't use the `fastify-plugin` wrapper in the `delay`
 factory. That's because we wanted the `onRequest` hook to only be set within
@@ -524,14 +524,14 @@ Retry-After: 5000
 }
 ```
 
-Then we attempt a new request (`req-2`), which was a `GET /ping`. As expected,
+Then we attempted a new request (`req-2`), which was a `GET /ping`. As expected,
 since that was not one of the requests we asked our plugin to filter, it
-succeeded. That could also be used as means of informing an interested party
+succeeded. That could also be used as a means of informing an interested party
 whether or not we were ready to serve requests (although `/ping` is more
 commonly associated with *liveness* checks and that would be the responsibility
 of a *readiness* check -- the curious reader can get more info on these terms
 [here](https://cloud.google.com/blog/products/containers-kubernetes/kubernetes-best-practices-setting-up-health-checks-with-readiness-and-liveness-probes))
-with the `ready` field. Below is the response for that request:
+with the `ready` field. Below is the response to that request:
 
 ```sh
 HTTP/1.1 200 OK
@@ -547,7 +547,7 @@ Keep-Alive: timeout=5
 }
 ```
 
-After that there were more interesting log messages:
+After that, there were more interesting log messages:
 
 <!-- markdownlint-disable -->
 ```sh

package/docs/Guides/Ecosystem.md

@@ -86,6 +86,8 @@ section.
   [`simple-oauth2`](https://github.com/lelylan/simple-oauth2).
 - [`@fastify/one-line-logger`](https://github.com/fastify/one-line-logger) Formats
   Fastify's logs into a nice one-line message.
+- [`@fastify/otel`](https://github.com/fastify/otel) OpenTelemetry
+  instrumentation library.
 - [`@fastify/passport`](https://github.com/fastify/fastify-passport) Use Passport
   strategies to authenticate requests and protect route.
 - [`@fastify/postgres`](https://github.com/fastify/fastify-postgres) Fastify
@@ -198,6 +200,8 @@ section.
   to go!
   A plugin to implement [Lyra](https://github.com/nearform/lyra) search engine
   on Fastify
+- [`@jerome1337/fastify-enforce-routes-pattern`](https://github.com/Jerome1337/fastify-enforce-routes-pattern)
+  A Fastify plugin that enforces naming pattern for routes path.
 - [`@joggr/fastify-prisma`](https://github.com/joggrdocs/fastify-prisma)
   A plugin for accessing an instantiated PrismaClient on your server.
 - [`@mgcrea/fastify-graceful-exit`](https://github.com/mgcrea/fastify-graceful-exit)
@@ -214,7 +218,7 @@ section.
   A custom compact pino-base prettifier
 - [`@pybot/fastify-autoload`](https://github.com/kunal097/fastify-autoload)
   Plugin to generate routes automatically with valid json content
-- [`@scalar/fastify-api-reference`](https://github.com/scalar/scalar/tree/main/packages/fastify-api-reference)
+- [`@scalar/fastify-api-reference`](https://github.com/scalar/scalar/tree/main/integrations/fastify)
   Beautiful OpenAPI/Swagger API references for Fastify
 - [`@trubavuong/fastify-seaweedfs`](https://github.com/trubavuong/fastify-seaweedfs)
   SeaweedFS for Fastify
@@ -456,6 +460,8 @@ middlewares into Fastify plugins
   Lightweight cache plugin
 - [`fastify-list-routes`](https://github.com/chuongtrh/fastify-list-routes)
   A simple plugin for Fastify to list all available routes.
+- [`fastify-lm`](https://github.com/galiprandi/fastify-lm#readme)
+  Use OpenAI, Claude, Google, Deepseek, and others LMs with one Fastify plugin.
 - [`fastify-loader`](https://github.com/TheNoim/fastify-loader) Load routes from
   a directory and inject the Fastify instance in each file.
 - [`fastify-log-controller`](https://github.com/Eomm/fastify-log-controller/)

package/docs/Guides/Fluent-Schema.md

@@ -55,7 +55,7 @@ fastify.post('/the/url', { schema }, handler)
 
 ### Reuse
 
-With `fluent-json-schema` you can manipulate your schemas more easily and
+With `fluent-json-schema`, you can manipulate your schemas more easily and
 programmatically and then reuse them thanks to the `addSchema()` method. You can
 refer to the schema in two different manners that are detailed in the
 [Validation and

package/docs/Guides/Getting-Started.md

@@ -106,7 +106,7 @@ of your code.
 Fastify offers an easy platform that helps to solve all of the problems outlined
 above, and more!
 
-> ## Note
+> **Note**
 > The above examples, and subsequent examples in this document, default to
 > listening *only* on the localhost `127.0.0.1` interface. To listen on all
 > available IPv4 interfaces the example should be modified to listen on
@@ -128,6 +128,9 @@ above, and more!
 >
 > When deploying to a Docker (or another type of) container using `0.0.0.0` or
 > `::` would be the easiest method for exposing the application.
+>
+> Note that when using `0.0.0.0`, the address provided in the callback argument
+> above will be the first address the wildcard refers to.
 
 ### Your first plugin
 <a id="first-plugin"></a>
@@ -417,7 +420,7 @@ In this way, you will always have access to all of the properties declared in
 the current scope.
 
 As discussed previously, Fastify offers a solid encapsulation model, to help you
-build your application as single and independent services. If you want to
+build your application as independent services. If you want to
 register a plugin only for a subset of routes, you just have to replicate the
 above structure.
 ```
@@ -552,15 +555,16 @@ an amazing [ecosystem](./Ecosystem.md)!
 <a id="test-server"></a>
 
 Fastify does not offer a testing framework, but we do recommend a way to write
-your tests that use the features and architecture of Fastify.
+your tests that uses the features and architecture of Fastify.
 
 Read the [testing](./Testing.md) documentation to learn more!
 
 ### Run your server from CLI
 <a id="cli"></a>
 
-Fastify also has CLI integration thanks to
-[fastify-cli](https://github.com/fastify/fastify-cli).
+Fastify also has CLI integration via
+[fastify-cli](https://github.com/fastify/fastify-cli),
+a separate tool for scaffolding and managing Fastify projects.
 
 First, install `fastify-cli`:
 

package/docs/Guides/Index.md

@@ -19,7 +19,7 @@ This table of contents is in alphabetical order.
   practical guide on detecting if and when a client aborts a request.
 + [Ecosystem](./Ecosystem.md): Lists all core plugins and many known community
   plugins.
-+ [Fluent Schema](./Fluent-Schema.md): Shows how writing JSON Schema can be
++ [Fluent Schema](./Fluent-Schema.md): Shows how JSON Schema can be
   written with a fluent API and used in Fastify.
 + [Getting Started](./Getting-Started.md): Introduction tutorial for Fastify.
   This is where beginners should start.

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

@@ -210,7 +210,7 @@ fastify.get('/posts/:id?', (request, reply) => {
 The [variadic signature](https://en.wikipedia.org/wiki/Variadic_function) of the
 `fastify.listen()` method is now deprecated.
 
-Prior to this release, the following invocations of this method were valid:
+Before this release, the following invocations of this method were valid:
 
   - `fastify.listen(8000)`
   - `fastify.listen(8000, ‘127.0.0.1’)`

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

@@ -472,7 +472,7 @@ or turn it into a function
 
 ```js
 // v5
-fastify.decorateRequest('myObject', () => { hello: 'world' });
+fastify.decorateRequest('myObject', () => ({ hello: 'world' }));
 ```
 
 or as a getter
@@ -524,6 +524,17 @@ fastify.register(function (instance, opts, done) {
 });
 ```
 
+### Requests now have `host`, `hostname`, and `port`, and `hostname` no longer includes the port number
+
+In Fastify v4, `req.hostname` would include both the hostname and the
+server’s port, so locally it might have the value `localhost:1234`.
+With v5, we aligned to the Node.js URL object and now include `host`, `hostname`,
+and `port` properties. `req.host` has the same value as `req.hostname` did in v4,
+while `req.hostname` includes the hostname _without_ a port if a port is present,
+and `req.port` contains just the port number.
+See [#4766](https://github.com/fastify/fastify/pull/4766)
+and [#4682](https://github.com/fastify/fastify/issues/4682) for more information.
+
 ### Removes `getDefaultRoute` and `setDefaultRoute` methods
 
 The `getDefaultRoute` and `setDefaultRoute` methods have been removed in v5.
@@ -709,4 +720,3 @@ contributing to those that are capable of accepting sponsorships.
 | voxpelli | [❤️ sponsor](https://github.com/sponsors/voxpelli) | fastify |
 | weixinwu |  | fastify-cli |
 | zetaraku |  | fastify-cli |
-

package/docs/Guides/Plugins-Guide.md

@@ -71,8 +71,8 @@ order of plugins. *How?* Glad you asked, check out
 [`avvio`](https://github.com/mcollina/avvio)! Fastify starts loading the plugin
 __after__ `.listen()`, `.inject()` or `.ready()` are called.
 
-Inside a plugin you can do whatever you want, register routes, utilities (we
-will see this in a moment) and do nested registers, just remember to call `done`
+Inside a plugin you can do whatever you want, register routes and utilities (we
+will see this in a moment), and do nested registers, just remember to call `done`
 when everything is set up!
 ```js
 module.exports = function (fastify, options, done) {
@@ -117,7 +117,7 @@ Now you can access your utility just by calling `fastify.util` whenever you need
 it - even inside your test.
 
 And here starts the magic; do you remember how just now we were talking about
-encapsulation? Well, using `register` and `decorate` in conjunction enable
+encapsulation? Well, using `register` and `decorate` in conjunction enables
 exactly that, let me show you an example to clarify this:
 ```js
 fastify.register((instance, opts, done) => {
@@ -137,7 +137,7 @@ Inside the second register call `instance.util` will throw an error because
 `util` exists only inside the first register context.
 
 Let's step back for a moment and dig deeper into this: every time you use the
-`register` API, a new context is created which avoids the negative situations
+`register` API, a new context is created that avoids the negative situations
 mentioned above.
 
 Do note that encapsulation applies to the ancestors and siblings, but not the
@@ -202,7 +202,7 @@ a utility that also needs access to the `request` and `reply` instance,
 a function that is defined using the `function` keyword is needed instead
 of an *arrow function expression*.
 
-In the same way you can do this for the `request` object:
+You can do the same for the `request` object:
 ```js
 fastify.decorate('getHeader', (req, header) => {
   return req.headers[header]
@@ -395,7 +395,7 @@ As we mentioned earlier, Fastify starts loading its plugins __after__
 have been declared. This means that, even though the plugin may inject variables
 to the external Fastify instance via [`decorate`](../Reference/Decorators.md),
 the decorated variables will not be accessible before calling `.listen()`,
-`.inject()` or `.ready()`.
+`.inject()`, or `.ready()`.
 
 In case you rely on a variable injected by a preceding plugin and want to pass
 that in the `options` argument of `register`, you can do so by using a function

package/docs/Guides/Serverless.md

@@ -25,11 +25,11 @@ snippet of code.
 ### Contents
 
 - [AWS](#aws)
+- [Genezio](#genezio)
 - [Google Cloud Functions](#google-cloud-functions)
 - [Google Firebase Functions](#google-firebase-functions)
 - [Google Cloud Run](#google-cloud-run)
 - [Netlify Lambda](#netlify-lambda)
-- [Platformatic Cloud](#platformatic-cloud)
 - [Vercel](#vercel)
 
 ## AWS
@@ -129,6 +129,14 @@ If you need to integrate with more AWS services, take a look at
 [@h4ad/serverless-adapter](https://viniciusl.com.br/serverless-adapter/docs/main/frameworks/fastify)
 on Fastify to find out how to integrate.
 
+## Genezio
+
+[Genezio](https://genezio.com/) is a platform designed to simplify the deployment
+of serverless applications to the cloud.
+
+[Genezio has a dedicated guide for deploying a Fastify application.](https://genezio.com/docs/frameworks/fastify/)
+
+
 ## Google Cloud Functions
 
 ### Creation of Fastify instance
@@ -280,8 +288,8 @@ 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
-plugins, hooks and other settings. As follows:
+in a function that will register routes, await the server's processing of
+plugins, hooks, and other settings. As follows:
 
 ```js
 const fastify = require("fastify")({
@@ -299,7 +307,7 @@ const fastifyApp = async (request, reply) => {
 
 Firebase Function's HTTP layer already parses the request
 and makes a JSON payload available. It also provides access
-to the raw body, unparsed, which is useful in order to calculate
+to the raw body, unparsed, which is useful for calculating
 request signatures to validate HTTP webhooks.
 
 Add as follows to the `registerRoutes()` function:
@@ -384,7 +392,7 @@ familiar with gcloud or just follow their
 
 ### Adjust Fastify server
 
-In order for Fastify to properly listen for requests within the container, be
+For Fastify to properly listen for requests within the container, be
 sure to set the correct port and address:
 
 ```js
@@ -562,49 +570,7 @@ Add this command to your `package.json` *scripts*
 }
 ```
 
-Then it should work fine
-
-## Platformatic Cloud
-
-[Platformatic](https://platformatic.dev) provides zero-configuration deployment
-for Node.js applications.
-To use it now, you should wrap your existing Fastify application inside a
-[Platformatic Service](https://oss.platformatic.dev/docs/reference/service/introduction),
-by running the following:
-
-
-```bash
-npm create platformatic@latest -- service
-```
-
-The wizard would ask you to fill in a few answers:
-
-```
-? Where would you like to create your project? .
-? Do you want to run npm install? yes
-? Do you want to use TypeScript? no
-? What port do you want to use? 3042
-[13:04:14] INFO: Configuration file platformatic.service.json successfully created.
-[13:04:14] INFO: Environment file .env successfully created.
-[13:04:14] INFO: Plugins folder "plugins" successfully created.
-[13:04:14] INFO: Routes folder "routes" successfully created.
-? Do you want to create the github action to deploy this application to Platformatic Cloud dynamic workspace? no
-? Do you want to create the github action to deploy this application to Platformatic Cloud static workspace? no
-```
-
-Then, head to [Platformatic Cloud](https://platformatic.cloud) and sign in
-with your GitHub account.
-Create your first application and a static workspace: be careful to download the
-API key as an env file, e.g. `yourworkspace.txt`.
-
-Then, you can easily deploy your application with the following command:
-
-```bash
-platformatic deploy --keys `yourworkspace.txt`
-```
-
-Check out the [Full Guide](https://blog.platformatic.dev/how-to-migrate-a-fastify-app-to-platformatic-service)
-on how to wrap Fastify application in Platformatic.
+Then it should work fine.
 
 ## Vercel
 

package/docs/Guides/Style-Guide.md

@@ -83,7 +83,7 @@ Result:
 
 Make sure you avoid copying other people's work. Keep it as original as
 possible. You can learn from what they have done and reference where it is from
-if you used a particular quote from their work.
+if you use a particular quote from their work.
 
 
 ## Word Choice
@@ -217,7 +217,7 @@ Styles](https://medium.com/better-programming/string-case-styles-camel-pascal-sn
 
 ### Hyperlinks
 
-Hyperlinks should have a clear title of what it references. Here is how your
+Hyperlinks should have a clear title of what they reference. Here is how your
 hyperlink should look:
 
 ```MD

package/docs/Guides/Testing.md

@@ -340,10 +340,10 @@ test('should ...', {only: true}, t => ...)
 ```
 2. Run `node --test`
 ```bash
-> node --test --test-only --node-arg=--inspect-brk test/<test-file.test.js>
+> node --test --test-only --inspect-brk test/<test-file.test.js>
 ```
 - `--test-only` specifies to run tests with the `only` option enabled
-- `--node-arg=--inspect-brk` will launch the node debugger
+- `--inspect-brk` will launch the node debugger
 3. In VS Code, create and launch a `Node.js: Attach` debug configuration. No
    modification should be necessary.