fastify 5.3.2 → 5.4.0

package/README.md

@@ -306,6 +306,8 @@ listed in alphabetical order.
 * [__Vincent Le Goff__](https://github.com/zekth)
 * [__Luciano Mammino__](https://github.com/lmammino),
   <https://twitter.com/loige>, <https://www.npmjs.com/~lmammino>
+* [__Jean Michelet__](https://github.com/jean-michelet),
+  <https://www.npmjs.com/~jean-michelet>
 * [__KaKa Ng__](https://github.com/climba03003),
   <https://www.npmjs.com/~climba03003>
 * [__Luis Orbaiceta__](https://github.com/luisorbaiceta),

package/build/build-validation.js

@@ -42,7 +42,8 @@ const defaultInitOptions = {
   requestIdLogLabel: 'reqId',
   http2SessionTimeout: 72000, // 72 seconds
   exposeHeadRoutes: true,
-  useSemicolonDelimiter: false
+  useSemicolonDelimiter: false,
+  allowErrorHandlerOverride: true // TODO: set to false in v6
 }
 
 const schema = {

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

@@ -529,9 +529,9 @@ since that was not one of the requests we asked our plugin to filter, it
 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 to that request:
+of a *readiness* check -- the curious reader can get more info on these
+[terms](https://cloud.google.com/blog/products/containers-kubernetes/kubernetes-best-practices-setting-up-health-checks-with-readiness-and-liveness-probes))
+here with the `ready` field. Below is the response to that request:
 
 ```sh
 HTTP/1.1 200 OK

package/docs/Guides/Ecosystem.md

@@ -40,8 +40,6 @@ section.
   plugin for adding
   [CSRF](https://en.wikipedia.org/wiki/Cross-site_request_forgery) protection to
   Fastify.
-- [`@fastify/diagnostics-channel`](https://github.com/fastify/fastify-diagnostics-channel)
-  Plugin to deal with `diagnostics_channel` on Fastify.
 - [`@fastify/elasticsearch`](https://github.com/fastify/fastify-elasticsearch)
   Plugin to share the same ES client.
 - [`@fastify/env`](https://github.com/fastify/fastify-env) Load and check
@@ -154,6 +152,15 @@ section.
 
 #### [Community](#community)
 
+> ℹ️ Note:
+> Fastify community plugins are part of the broader community efforts,
+> and we are thankful for these contributions. However, they are not
+> maintained by the Fastify team.
+> Use them at your own discretion.
+> If you find malicious code, please
+> [open an issue](https://github.com/fastify/fastify/issues/new/choose) or
+> submit a PR to remove the plugin from the list.
+
 - [`@aaroncadillac/crudify-mongo`](https://github.com/aaroncadillac/crudify-mongo)
   A simple way to add a crud in your fastify project.
 - [`@applicazza/fastify-nextjs`](https://github.com/applicazza/fastify-nextjs)
@@ -195,11 +202,9 @@ section.
 - [`@immobiliarelabs/fastify-metrics`](https://github.com/immobiliare/fastify-metrics)
   Minimalistic and opinionated plugin that collects usage/process metrics and
   dispatches to [statsd](https://github.com/statsd/statsd).
-- [`@immobiliarelabs/fastify-sentry`](https://github.com/immobiliare/fastify-sentry)
-  Sentry errors handler that just works! Install, add your DSN and you're good
-  to go!
-  A plugin to implement [Lyra](https://github.com/nearform/lyra) search engine
-  on Fastify
+- [`@inaiat/fastify-papr`](https://github.com/inaiat/fastify-papr)
+  A plugin to integrate [Papr](https://github.com/plexinc/papr), 
+  the MongoDB ORM for TypeScript & MongoDB, with 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)
@@ -737,9 +742,13 @@ middlewares into Fastify plugins
   generator by directory structure.
 - [`fastify-flux`](https://github.com/Jnig/fastify-flux) Tool for building
   Fastify APIs using decorators and convert Typescript interface to JSON Schema.
+- [`jeasx`](https://www.jeasx.dev)
+  A flexible server-rendering framework built on Fastify
+  that leverages asynchronous JSX to simplify web development.
 - [`simple-tjscli`](https://github.com/imjuni/simple-tjscli) CLI tool to
   generate JSON Schema from TypeScript interfaces.
 - [`vite-plugin-fastify`](https://github.com/Vanilla-IceCream/vite-plugin-fastify)
   Fastify plugin for Vite with Hot-module Replacement.
 - [`vite-plugin-fastify-routes`](https://github.com/Vanilla-IceCream/vite-plugin-fastify-routes)
   File-based routing for Fastify applications using Vite.
+  

package/docs/Guides/Serverless.md

@@ -1,20 +1,20 @@
 <h1 align="center">Serverless</h1>
 
 Run serverless applications and REST APIs using your existing Fastify
-application. By default, Fastify will not work on your serverless platform of
-choice, you will need to make some small changes to fix this. This document
-contains a small guide for the most popular serverless providers and how to use
+application. You may need to make code changes to work on your
+serverless platform of choice. This document contains a small guide
+for the most popular serverless providers and how to use
 Fastify with them.
 
 #### Should you use Fastify in a serverless platform?
 
-That is up to you! Keep in mind that functions as a service should always use
+That is up to you! Keep in mind, functions as a service should always use
 small and focused functions, but you can also run an entire web application with
 them. It is important to remember that the bigger the application the slower the
 initial boot will be. The best way to run Fastify applications in serverless
-environments is to use platforms like Google Cloud Run, AWS Fargate, and Azure
-Container Instances, where the server can handle multiple requests at the same
-time and make full use of Fastify's features.
+environments is to use platforms like Google Cloud Run, AWS Fargate, Azure
+Container Instances, and Vercel where the server can handle multiple requests
+at the same time and make full use of Fastify's features.
 
 One of the best features of using Fastify in serverless applications is the ease
 of development. In your local environment, you will always run the Fastify
@@ -136,7 +136,6 @@ 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
@@ -238,14 +237,13 @@ npx @google-cloud/functions-framework --target=fastifyFunction
 Or add this command to your `package.json` scripts:
 ```json
 "scripts": {
-...
-"dev": "npx @google-cloud/functions-framework --target=fastifyFunction"
-...
+  ...
+  "dev": "npx @google-cloud/functions-framework --target=fastifyFunction"
+  ...
 }
 ```
 and run it with `npm run dev`.
 
-
 ### Deploy
 ```bash
 gcloud functions deploy fastifyFunction \
@@ -326,7 +324,7 @@ async function registerRoutes (fastify) {
   })
 
   // define your endpoints here...
-  fastify.post("/some-route-here", async (request, reply) => {}
+  fastify.post("/some-route-here", async (request, reply) => {})
 
   fastify.get('/', async (request, reply) => {
     reply.send({message: 'Hello World!'})
@@ -377,7 +375,6 @@ firebase functions:log
 - [Fastify on Firebase Functions](https://github.com/lirantal/lemon-squeezy-firebase-webhook-fastify/blob/main/package.json)
 - [An article about HTTP webhooks on Firebase Functions and Fastify: A Practical Case Study with Lemon Squeezy](https://lirantal.com/blog/http-webhooks-firebase-functions-fastify-practical-case-study-lemon-squeezy)
 
-
 ## Google Cloud Run
 
 Unlike AWS Lambda or Google Cloud Functions, Google Cloud Run is a serverless
@@ -463,7 +460,7 @@ CMD [ "npm", "start" ]
 To keep build artifacts out of your container (which keeps it small and improves
 build times) add a `.dockerignore` file like the one below:
 
-```.dockerignore
+```dockerignore
 Dockerfile
 README.md
 node_modules
@@ -490,12 +487,11 @@ gcloud beta run deploy --image gcr.io/PROJECT-ID/APP-NAME --platform managed
 
 Your app will be accessible from the URL GCP provides.
 
-
 ## netlify-lambda
 
 First, please perform all preparation steps related to **AWS Lambda**.
 
-Create a folder called `functions`,  then create `server.js` (and your endpoint
+Create a folder called `functions`, then create `server.js` (and your endpoint
 path will be `server.js`) inside the `functions` folder.
 
 ### functions/server.js
@@ -564,9 +560,9 @@ Add this command to your `package.json` *scripts*
 
 ```json
 "scripts": {
-...
-"build:functions": "netlify-lambda build functions --config ./webpack.config.netlify.js"
-...
+  ...
+  "build:functions": "netlify-lambda build functions --config ./webpack.config.netlify.js"
+  ...
 }
 ```
 
@@ -574,54 +570,17 @@ Then it should work fine.
 
 ## Vercel
 
-[Vercel](https://vercel.com) provides zero-configuration deployment for Node.js
-applications. To use it now, it is as simple as configuring your `vercel.json`
-file like the following:
-
-```json
-{
-    "rewrites": [
-        {
-            "source": "/(.*)",
-            "destination": "/api/serverless.js"
-        }
-    ]
-}
-```
-
-Then, write `api/serverless.js` like so:
-
-```js
-"use strict";
-
-// Read the .env file.
-import * as dotenv from "dotenv";
-dotenv.config();
+[Vercel](https://vercel.com) fully supports deploying Fastify applications.
+Additionally, with Vercel's
+[Fluid compute](https://vercel.com/docs/functions/fluid-compute), you can combine
+server-like concurrency with the autoscaling properties of traditional
+serverless functions.
 
-// Require the framework
-import Fastify from "fastify";
+Get started with the
+[Fastify Node.js template on Vercel](
+https://vercel.com/templates/other/fastify-serverless-function).
 
-// Instantiate Fastify with some config
-const app = Fastify({
-  logger: true,
-});
-
-// Register your application as a normal plugin.
-app.register(import("../src/app.js"));
-
-export default async (req, res) => {
-    await app.ready();
-    app.server.emit('request', req, res);
-}
-```
-
-In `src/app.js` define the plugin.
-```js
-async function routes (fastify, options) {
-  fastify.get('/', async (request, reply) => {
-    return { hello: 'world' }
-  })
-}
-
-export default routes;
-```
+[Fluid compute](https://vercel.com/docs/functions/fluid-compute) currently
+requires an explicit opt-in. Learn more about enabling Fluid compute
+[here](
+https://vercel.com/docs/functions/fluid-compute#how-to-enable-fluid-compute).

package/docs/Reference/ContentTypeParser.md

@@ -152,7 +152,7 @@ fastify.addContentTypeParser('text/xml', function (request, payload, done) {
 })
 ```
 
-> 🛈 Note: `function(req, done)` and `async function(req)` are
+> ℹ️ Note: `function(req, done)` and `async function(req)` are
 > still supported but deprecated.
 
 #### Body Parser

package/docs/Reference/Errors.md

@@ -69,7 +69,6 @@
     - [FST_ERR_SCH_VALIDATION_BUILD](#fst_err_sch_validation_build)
     - [FST_ERR_SCH_SERIALIZATION_BUILD](#fst_err_sch_serialization_build)
     - [FST_ERR_SCH_RESPONSE_SCHEMA_NOT_NESTED_2XX](#fst_err_sch_response_schema_not_nested_2xx)
-    - [FST_ERR_HTTP2_INVALID_VERSION](#fst_err_http2_invalid_version)
     - [FST_ERR_INIT_OPTS_INVALID](#fst_err_init_opts_invalid)
     - [FST_ERR_FORCE_CLOSE_CONNECTIONS_IDLE_NOT_AVAILABLE](#fst_err_force_close_connections_idle_not_available)
     - [FST_ERR_DUPLICATED_ROUTE](#fst_err_duplicated_route)
@@ -98,6 +97,7 @@
     - [FST_ERR_VALIDATION](#fst_err_validation)
     - [FST_ERR_LISTEN_OPTIONS_INVALID](#fst_err_listen_options_invalid)
     - [FST_ERR_ERROR_HANDLER_NOT_FN](#fst_err_error_handler_not_fn)
+    - [FST_ERR_ERROR_HANDLER_ALREADY_SET](#fst_err_error_handler_already_set)
 
 ### Error Handling In Node.js
 <a id="error-handling"></a>
@@ -340,7 +340,6 @@ Below is a table with all the error codes used by Fastify.
 | <a id="fst_err_sch_validation_build">FST_ERR_SCH_VALIDATION_BUILD</a> | The JSON schema provided for validation to a route is not valid. | Fix the JSON schema. | [#2023](https://github.com/fastify/fastify/pull/2023) |
 | <a id="fst_err_sch_serialization_build">FST_ERR_SCH_SERIALIZATION_BUILD</a> | The JSON schema provided for serialization of a route response is not valid. | Fix the JSON schema. | [#2023](https://github.com/fastify/fastify/pull/2023) |
 | <a id="fst_err_sch_response_schema_not_nested_2xx">FST_ERR_SCH_RESPONSE_SCHEMA_NOT_NESTED_2XX</a> | Response schemas should be nested under a valid status code (2XX). | Use a valid status code. | [#4554](https://github.com/fastify/fastify/pull/4554) |
-| <a id="fst_err_http2_invalid_version">FST_ERR_HTTP2_INVALID_VERSION</a> | HTTP2 is available only from node >= 8.8.1. | Use a higher version of node. | [#1346](https://github.com/fastify/fastify/pull/1346) |
 | <a id="fst_err_init_opts_invalid">FST_ERR_INIT_OPTS_INVALID</a> | Invalid initialization options. | Use valid initialization options. | [#1471](https://github.com/fastify/fastify/pull/1471) |
 | <a id="fst_err_force_close_connections_idle_not_available">FST_ERR_FORCE_CLOSE_CONNECTIONS_IDLE_NOT_AVAILABLE</a> | Cannot set forceCloseConnections to `idle` as your HTTP server does not support `closeIdleConnections` method. | Use a different value for `forceCloseConnections`. | [#3925](https://github.com/fastify/fastify/pull/3925) |
 | <a id="fst_err_duplicated_route">FST_ERR_DUPLICATED_ROUTE</a> | The HTTP method already has a registered controller for that URL. | Use a different URL or register the controller for another HTTP method. | [#2954](https://github.com/fastify/fastify/pull/2954) |
@@ -368,5 +367,4 @@ Below is a table with all the error codes used by Fastify.
 | <a id="fst_err_plugin_invalid_async_handler">FST_ERR_PLUGIN_INVALID_ASYNC_HANDLER</a> | The plugin being registered mixes async and callback styles. | - | [#5141](https://github.com/fastify/fastify/pull/5141) |
 | <a id="fst_err_validation">FST_ERR_VALIDATION</a> | The Request failed the payload validation. | Check the request payload. | [#4824](https://github.com/fastify/fastify/pull/4824) |
 | <a id="fst_err_listen_options_invalid">FST_ERR_LISTEN_OPTIONS_INVALID</a> | Invalid listen options. | Check the listen options. | [#4886](https://github.com/fastify/fastify/pull/4886) |
-| <a id="fst_err_error_handler_not_fn">FST_ERR_ERROR_HANDLER_NOT_FN</a> | Error Handler must be a function | Provide a function to `setErrorHandler`. | [#5317](https://github.com/fastify/fastify/pull/5317) |
-
+| <a id="fst_err_error_handler_not_fn">FST_ERR_ERROR_HANDLER_NOT_FN</a> | Error Handler must be a function | Provide a function to `setErrorHandler`. | [#5317](https://github.com/fastify/fastify/pull/5317) | <a id="fst_err_error_handler_already_set">FST_ERR_ERROR_HANDLER_ALREADY_SET</a> | Error Handler already set in this scope. Set `allowErrorHandlerOverride: true` to allow overriding. | By default, `setErrorHandler` can only be called once per encapsulation context. | [#6097](https://github.com/fastify/fastify/pull/6098) |

package/docs/Reference/Hooks.md

@@ -34,7 +34,7 @@ are Request/Reply hooks and application hooks:
 - [Using Hooks to Inject Custom Properties](#using-hooks-to-inject-custom-properties)
 - [Diagnostics Channel Hooks](#diagnostics-channel-hooks)
 
-> 🛈 Note: The `done` callback is not available when using `async`/`await` or
+> ℹ️ Note: The `done` callback is not available when using `async`/`await` or
 > returning a `Promise`. If you do invoke a `done` callback in this situation
 > unexpected behavior may occur, e.g. duplicate invocation of handlers.
 
@@ -68,7 +68,7 @@ fastify.addHook('onRequest', async (request, reply) => {
 })
 ```
 
-> 🛈 Note: In the [onRequest](#onrequest) hook, `request.body` will always be
+> ℹ️ Note: In the [onRequest](#onrequest) hook, `request.body` will always be
 > `undefined`, because the body parsing happens before the
 > [preValidation](#prevalidation) hook.
 
@@ -98,16 +98,16 @@ fastify.addHook('preParsing', async (request, reply, payload) => {
 })
 ```
 
-> 🛈 Note: In the [preParsing](#preparsing) hook, `request.body` will always be
+> ℹ️ Note: In the [preParsing](#preparsing) hook, `request.body` will always be
 > `undefined`, because the body parsing happens before the
 > [preValidation](#prevalidation) hook.
 
-> 🛈 Note: You should also add a `receivedEncodedLength` property to the
+> ℹ️ Note: You should also add a `receivedEncodedLength` property to the
 > returned stream. This property is used to correctly match the request payload
 > with the `Content-Length` header value. Ideally, this property should be updated
 > on each received chunk.
 
-> 🛈 Note: The size of the returned stream is checked to not exceed the limit
+> ℹ️ Note: The size of the returned stream is checked to not exceed the limit
 > set in [`bodyLimit`](./Server.md#bodylimit) option.
 
 ### preValidation
@@ -166,7 +166,7 @@ fastify.addHook('preSerialization', async (request, reply, payload) => {
 })
 ```
 
-> 🛈 Note: The hook is NOT called if the payload is a `string`, a `Buffer`, a
+> ℹ️ Note: The hook is NOT called if the payload is a `string`, a `Buffer`, a
 > `stream`, or `null`.
 
 ### onError
@@ -196,7 +196,7 @@ user
 *(Note that the default error handler always sends the error back to the
 user)*.
 
-> 🛈 Note: Unlike the other hooks, passing an error to the `done` function is not
+> ℹ️ Note: Unlike the other hooks, passing an error to the `done` function is not
 > supported.
 
 ### onSend
@@ -233,7 +233,7 @@ fastify.addHook('onSend', (request, reply, payload, done) => {
 > to `0`, whereas the `Content-Length` header will not be set if the payload is
 > `null`.
 
-> 🛈 Note: If you change the payload, you may only change it to a `string`, a
+> ℹ️ Note: If you change the payload, you may only change it to a `string`, a
 > `Buffer`, a `stream`, a `ReadableStream`, a `Response`, or `null`.
 
 
@@ -256,7 +256,7 @@ The `onResponse` hook is executed when a response has been sent, so you will not
 be able to send more data to the client. It can however be useful for sending
 data to external services, for example, to gather statistics.
 
-> 🛈 Note: Setting `disableRequestLogging` to `true` will disable any error log
+> ℹ️ Note: Setting `disableRequestLogging` to `true` will disable any error log
 > inside the `onResponse` hook. In this case use `try - catch` to log errors.
 
 ### onTimeout
@@ -298,7 +298,7 @@ The `onRequestAbort` hook is executed when a client closes the connection before
 the entire request has been processed. Therefore, you will not be able to send
 data to the client.
 
-> 🛈 Note: Client abort detection is not completely reliable.
+> ℹ️ Note: Client abort detection is not completely reliable.
 > See: [`Detecting-When-Clients-Abort.md`](../Guides/Detecting-When-Clients-Abort.md)
 
 ### Manage Errors from a hook
@@ -452,7 +452,7 @@ fastify.addHook('onListen', async function () {
 })
 ```
 
-> 🛈 Note: This hook will not run when the server is started using
+> ℹ️ Note: This hook will not run when the server is started using
 > fastify.inject()` or `fastify.ready()`.
 
 ### onClose
@@ -576,7 +576,7 @@ This hook can be useful if you are developing a plugin that needs to know when a
 plugin context is formed, and you want to operate in that specific context, thus
 this hook is encapsulated.
 
-> 🛈 Note: This hook will not be called if a plugin is wrapped inside
+> ℹ️ Note: This hook will not be called if a plugin is wrapped inside
 > [`fastify-plugin`](https://github.com/fastify/fastify-plugin).
 ```js
 fastify.decorate('data', [])
@@ -774,7 +774,7 @@ fastify.route({
 })
 ```
 
-> 🛈 Note: Both options also accept an array of functions.
+> ℹ️ Note: Both options also accept an array of functions.
 
 ## Using Hooks to Inject Custom Properties
 <a id="using-hooks-to-inject-custom-properties"></a>
@@ -861,7 +861,7 @@ channel.subscribe(function ({ fastify }) {
 })
 ```
 
-> 🛈 Note: The TracingChannel class API is currently experimental and may undergo
+> ℹ️ Note: The TracingChannel class API is currently experimental and may undergo
 > breaking changes even in semver-patch releases of Node.js.
 
 Five other events are published on a per-request basis following the

package/docs/Reference/Logging.md

@@ -157,7 +157,7 @@ const fastify = require('fastify')({
 });
 ```
 
-> 🛈 Note: In some cases, the [`Reply`](./Reply.md) object passed to the `res`
+> ℹ️ Note: In some cases, the [`Reply`](./Reply.md) object passed to the `res`
 > serializer cannot be fully constructed. When writing a custom `res`
 > serializer, check for the existence of any properties on `reply` aside from
 > `statusCode`, which is always present. For example, verify the existence of
@@ -184,7 +184,7 @@ const fastify = require('fastify')({
 });
 ```
 
-> 🛈 Note: The body cannot be serialized inside a `req` method because the
+> ℹ️ Note: The body cannot be serialized inside a `req` method because the
 request is serialized when the child logger is created. At that time, the body
 is not yet parsed.
 
@@ -199,7 +199,7 @@ app.addHook('preHandler', function (req, reply, done) {
 })
 ```
 
-> 🛈 Note: Ensure serializers never throw errors, as this can cause the Node
+> ℹ️ Note: Ensure serializers never throw errors, as this can cause the Node
 > process to exit. See the
 > [Pino documentation](https://getpino.io/#/docs/api?id=opt-serializers) for more
 > information.

package/docs/Reference/Middleware.md

@@ -50,7 +50,7 @@ that already has the Fastify [Request](./Request.md#request) and
 To run middleware under certain paths, pass the path as the first parameter to
 `use`.
 
-> 🛈 Note: This does not support routes with parameters
+> ℹ️ Note: This does not support routes with parameters
 > (e.g. `/user/:id/comments`) and wildcards are not supported in multiple paths.
 
 ```js

package/docs/Reference/Reply.md

@@ -151,7 +151,7 @@ fastify.get('/', async function (req, rep) {
 Sets a response header. If the value is omitted or undefined, it is coerced to
 `''`.
 
-> 🛈 Note: The header's value must be properly encoded using
+> ℹ️ Note: The header's value must be properly encoded using
 > [`encodeURI`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/encodeURI)
 > or similar modules such as
 > [`encodeurl`](https://www.npmjs.com/package/encodeurl). Invalid characters
@@ -260,10 +260,10 @@ requires heavy resources to be sent after the `data`, for example,
 `Server-Timing` and `Etag`. It can ensure the client receives the response data
 as soon as possible.
 
-> 🛈 Note: The header `Transfer-Encoding: chunked` will be added once you use
+> ℹ️ Note: The header `Transfer-Encoding: chunked` will be added once you use
 > the trailer. It is a hard requirement for using trailer in Node.js.
 
-> 🛈 Note: Any error passed to `done` callback will be ignored. If you interested
+> ℹ️ Note: Any error passed to `done` callback will be ignored. If you interested
 > in the error, you can turn on `debug` level logging.*
 
 ```js
@@ -279,14 +279,14 @@ const { createHash } = require('node:crypto')
 reply.trailer('content-md5', function(reply, payload, done) {
   const hash = createHash('md5')
   hash.update(payload)
-  done(null, hash.disgest('hex'))
+  done(null, hash.digest('hex'))
 })
 
 // when you prefer async-await
 reply.trailer('content-md5', async function(reply, payload) {
   const hash = createHash('md5')
   hash.update(payload)
-  return hash.disgest('hex')
+  return hash.digest('hex')
 })
 ```
 
@@ -314,7 +314,7 @@ reply.getTrailer('server-timing') // undefined
 Redirects a request to the specified URL, the status code is optional, default
 to `302` (if status code is not already set by calling `code`).
 
-> 🛈 Note: The input URL must be properly encoded using
+> ℹ️ Note: The input URL must be properly encoded using
 > [`encodeURI`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/encodeURI)
 > or similar modules such as
 > [`encodeurl`](https://www.npmjs.com/package/encodeurl). Invalid URLs will
@@ -823,7 +823,7 @@ automatically create an error structured as the following:
 You can add custom properties to the Error object, such as `headers`, that will
 be used to enhance the HTTP response.
 
-> 🛈 Note: If you are passing an error to `send` and the statusCode is less than
+> ℹ️ Note: If you are passing an error to `send` and the statusCode is less than
 > 400, Fastify will automatically set it at 500.
 
 Tip: you can simplify errors by using the
@@ -871,7 +871,7 @@ fastify.get('/', {
 If you want to customize error handling, check out
 [`setErrorHandler`](./Server.md#seterrorhandler) API.
 
-> 🛈 Note: you are responsible for logging when customizing the error handler.
+> ℹ️ Note: you are responsible for logging when customizing the error handler.
 
 API:
 

package/docs/Reference/Request.md

@@ -84,7 +84,7 @@ This operation adds new values to the request headers, accessible via
 For performance reasons, `Symbol('fastify.RequestAcceptVersion')` may be added
 to headers on `not found` routes.
 
-> 🛈 Note: Schema validation may mutate the `request.headers` and
+> ℹ️ Note: Schema validation may mutate the `request.headers` and
 > `request.raw.headers` objects, causing the headers to become empty.
 
 ```js

package/docs/Reference/Routes.md

@@ -137,7 +137,7 @@ fastify.route(options)
 
 * `reply` is defined in [Reply](./Reply.md).
 
-> 🛈 Note: The documentation for `onRequest`, `preParsing`, `preValidation`,
+> ℹ️ Note: The documentation for `onRequest`, `preParsing`, `preValidation`,
 > `preHandler`, `preSerialization`, `onSend`, and `onResponse` is detailed in
 > [Hooks](./Hooks.md). To send a response before the request is handled by the
 > `handler`, see [Respond to a request from
@@ -233,7 +233,7 @@ const opts = {
 fastify.get('/', opts)
 ```
 
-> 🛈 Note: Specifying the handler in both `options` and as the third parameter to
+> ℹ️ Note: Specifying the handler in both `options` and as the third parameter to
 > the shortcut method throws a duplicate `handler` error.
 
 ### Url building
@@ -402,7 +402,7 @@ This approach supports both `callback-style` and `async-await` with minimal
 trade-off. However, it is recommended to use only one style for consistent
 error handling within your application.
 
-> 🛈 Note: Every async function returns a promise by itself.
+> ℹ️ Note: Every async function returns a promise by itself.
 
 ### Route Prefixing
 <a id="route-prefixing"></a>