fastify 4.0.0 → 4.0.1

package/docs/Guides/Ecosystem.md

@@ -12,8 +12,8 @@ section.
   [accepts](https://www.npmjs.com/package/accepts) in your request object.
 - [`@fastify/accepts-serializer`](https://github.com/fastify/fastify-accepts-serializer)
   to serialize to output according to `Accept` header.
-- [`@fastify/any-schema`](https://github.com/fastify/any-schema-you-like) Save multiple
-  schemas and decide which one to use to serialize the payload
+- [`@fastify/any-schema`](https://github.com/fastify/any-schema-you-like) Save
+  multiple schemas and decide which one to use to serialize the payload
 - [`@fastify/auth`](https://github.com/fastify/fastify-auth) Run multiple auth
   functions in Fastify.
 - [`@fastify/autoload`](https://github.com/fastify/fastify-autoload) Require all
@@ -21,13 +21,13 @@ section.
 - [`@fastify/awilix`](https://github.com/fastify/fastify-awilix) Dependency
   injection support for Fastify, based on
   [awilix](https://github.com/jeffijoe/awilix).
-- [`@fastify/aws-lambda`](https://github.com/fastify/aws-lambda-fastify) allows you to
-  easily build serverless web applications/services and RESTful APIs using Fastify
-  on top of AWS Lambda and Amazon API Gateway.
+- [`@fastify/aws-lambda`](https://github.com/fastify/aws-lambda-fastify) allows
+  you to easily build serverless web applications/services and RESTful APIs
+  using Fastify on top of AWS Lambda and Amazon API Gateway.
 - [`@fastify/basic-auth`](https://github.com/fastify/fastify-basic-auth) Basic
   auth plugin for Fastify.
-- [`@fastify/bearer-auth`](https://github.com/fastify/fastify-bearer-auth) Bearer
-  auth plugin for Fastify.
+- [`@fastify/bearer-auth`](https://github.com/fastify/fastify-bearer-auth)
+  Bearer auth plugin for Fastify.
 - [`@fastify/caching`](https://github.com/fastify/fastify-caching) General
   server-side cache and ETag support.
 - [`@fastify/circuit-breaker`](https://github.com/fastify/fastify-circuit-breaker)
@@ -38,7 +38,8 @@ section.
   cookie headers.
 - [`@fastify/cors`](https://github.com/fastify/fastify-cors) Enables the use of
   CORS in a Fastify application.
-- [`@fastify/csrf-protection`](https://github.com/fastify/csrf-protection) A plugin for adding
+- [`@fastify/csrf-protection`](https://github.com/fastify/csrf-protection) A
+  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)
@@ -59,14 +60,16 @@ section.
   function.
 - [`@fastify/helmet`](https://github.com/fastify/fastify-helmet) Important
   security headers for Fastify.
-- [`@fastify/hotwire`](https://github.com/fastify/fastify-hotwire) Use the Hotwire pattern with Fastify.
+- [`@fastify/hotwire`](https://github.com/fastify/fastify-hotwire) Use the
+  Hotwire pattern with Fastify.
 - [`@fastify/http-proxy`](https://github.com/fastify/fastify-http-proxy) Proxy
   your HTTP requests to another server, with hooks.
-- [`@fastify/jwt`](https://github.com/fastify/fastify-jwt) JWT utils for Fastify,
-  internally uses [fast-jwt](https://github.com/nearform/fast-jwt).
+- [`@fastify/jwt`](https://github.com/fastify/fastify-jwt) JWT utils for
+  Fastify, internally uses [fast-jwt](https://github.com/nearform/fast-jwt).
 - [`@fastify/leveldb`](https://github.com/fastify/fastify-leveldb) Plugin to
   share a common LevelDB connection across Fastify.
-- [`@fastify/middie`](https://github.com/fastify/middie) Middleware engine for Fastify.
+- [`@fastify/middie`](https://github.com/fastify/middie) Middleware engine for
+  Fastify.
 - [`@fastify/mongodb`](https://github.com/fastify/fastify-mongodb) Fastify
   MongoDB connection plugin, with which you can share the same MongoDB
   connection pool across every part of your server.
@@ -99,8 +102,8 @@ section.
 - [`@fastify/schedule`](https://github.com/fastify/fastify-schedule) Plugin for
   scheduling periodic jobs, based on
   [toad-scheduler](https://github.com/kibertoad/toad-scheduler).
-- [`@fastify/sensible`](https://github.com/fastify/fastify-sensible) Defaults for
-  Fastify that everyone can agree on. It adds some useful decorators such as
+- [`@fastify/sensible`](https://github.com/fastify/fastify-sensible) Defaults
+  for Fastify that everyone can agree on. It adds some useful decorators such as
   HTTP errors and assertions, but also more request and reply methods.
 - [`@fastify/session`](https://github.com/fastify/session) a session plugin for
   Fastify.
@@ -109,10 +112,11 @@ section.
 - [`@fastify/swagger`](https://github.com/fastify/fastify-swagger) Plugin for
   serving Swagger/OpenAPI documentation for Fastify, supporting dynamic
   generation.
-- [`@fastify/under-pressure`](https://github.com/fastify/under-pressure) Measure process
-  load with automatic handling of _"Service Unavailable"_ plugin for Fastify.
-- [`@fastify/url-data`](https://github.com/fastify/fastify-url-data) Decorate the
-  `Request` object with a method to access raw URL components.
+- [`@fastify/under-pressure`](https://github.com/fastify/under-pressure) Measure
+  process load with automatic handling of _"Service Unavailable"_ plugin for
+  Fastify.
+- [`@fastify/url-data`](https://github.com/fastify/fastify-url-data) Decorate
+  the `Request` object with a method to access raw URL components.
 - [`@fastify/view`](https://github.com/fastify/point-of-view) Templates
   rendering (_ejs, pug, handlebars, marko_) plugin support for Fastify.
 - [`@fastify/websocket`](https://github.com/fastify/fastify-websocket) WebSocket
@@ -134,7 +138,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!
+- [`@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!
 - [`@mgcrea/fastify-graceful-exit`](https://github.com/mgcrea/fastify-graceful-exit)
   A plugin to close the server gracefully
 - [`@mgcrea/fastify-request-logger`](https://github.com/mgcrea/fastify-request-logger)
@@ -250,8 +256,8 @@ section.
   Fastify feature flags plugin with multiple providers support (e.g. env,
   [config](https://lorenwest.github.io/node-config/),
   [unleash](https://unleash.github.io/)).
-- [`fastify-file-routes`](https://github.com/spa5k/fastify-file-routes)
-  Get Next.js based file system routing into fastify.
+- [`fastify-file-routes`](https://github.com/spa5k/fastify-file-routes) Get
+  Next.js based file system routing into fastify.
 - [`fastify-file-upload`](https://github.com/huangang/fastify-file-upload)
   Fastify plugin for uploading files.
 - [`fastify-firebase`](https://github.com/now-ims/fastify-firebase) Fastify
@@ -302,8 +308,8 @@ section.
   An error handling plugin for Fastify that uses enhanced HTTP errors.
 - [`fastify-https-redirect`](https://github.com/tomsvogel/fastify-https-redirect)
   Fastify plugin for auto-redirect from HTTP to HTTPS.
-- [`fatify-impressions`](https://github.com/manju4ever/fastify-impressions) Fastify
-  plugin to track impressions of all the routes.
+- [`fatify-impressions`](https://github.com/manju4ever/fastify-impressions)
+  Fastify plugin to track impressions of all the routes.
 - [`fastify-influxdb`](https://github.com/alex-ppg/fastify-influxdb) Fastify
   InfluxDB plugin connecting to an InfluxDB instance via the Influx default
   package.
@@ -353,7 +359,8 @@ section.
   for handling multipart/form-data, which is primarily used for uploading files.
 - [`fastify-nats`](https://github.com/mahmed8003/fastify-nats) Plugin to share
   [NATS](https://nats.io) client across Fastify.
-- [`fastify-next-auth`](https://github.com/wobsoriano/fastify-next-auth) NextAuth.js plugin for Fastify.
+- [`fastify-next-auth`](https://github.com/wobsoriano/fastify-next-auth)
+  NextAuth.js plugin for Fastify.
 - [`fastify-no-additional-properties`](https://github.com/greguz/fastify-no-additional-properties)
   Add `additionalProperties: false` by default to your JSON Schemas.
 - [`fastify-no-icon`](https://github.com/jsumners/fastify-no-icon) Plugin to
@@ -412,7 +419,8 @@ section.
 - [`fastify-qs`](https://github.com/webdevium/fastify-qs) A plugin for Fastify
   that adds support for parsing URL query parameters with
   [qs](https://github.com/ljharb/qs).
-- [`fastify-racing`](https://github.com/metcoder95/fastify-racing) Fastify's plugin that adds support to handle an aborted request asynchronous.
+- [`fastify-racing`](https://github.com/metcoder95/fastify-racing) Fastify's
+  plugin that adds support to handle an aborted request asynchronous.
 - [`fastify-raw-body`](https://github.com/Eomm/fastify-raw-body) Add the
   `request.rawBody` field.
 - [`fastify-rbac`](https://gitlab.com/m03geek/fastify-rbac) Fastify role-based
@@ -460,7 +468,9 @@ section.
   client plugin for Fastify.
 - [`fastify-socket.io`](https://github.com/alemagio/fastify-socket.io) a
   Socket.io plugin for Fastify.
-- [`fastify-split-validator`](https://github.com/MetCoder95/fastify-split-validator) Small plugin to allow you use multiple validators in one route based on each HTTP part of the request.
+- [`fastify-split-validator`](https://github.com/MetCoder95/fastify-split-validator)
+  Small plugin to allow you use multiple validators in one route based on each
+  HTTP part of the request.
 - [`fastify-sse`](https://github.com/lolo32/fastify-sse) to provide Server-Sent
   Events with `reply.sse( … )` to Fastify.
 - [`fastify-sse-v2`](https://github.com/nodefactoryio/fastify-sse-v2) to provide
@@ -499,8 +509,8 @@ section.
   waterline. Decorates Fastify with waterline models.
 - [`fastify-webpack-hmr`](https://github.com/lependu/fastify-webpack-hmr)
   Webpack hot module reloading plugin for Fastify.
-- [`fastify-webpack-hot`](https://github.com/gajus/fastify-webpack-hot)
-  Webpack Hot Module Replacement for Fastify.
+- [`fastify-webpack-hot`](https://github.com/gajus/fastify-webpack-hot) Webpack
+  Hot Module Replacement for Fastify.
 - [`fastify-ws`](https://github.com/gj/fastify-ws) WebSocket integration for
   Fastify — with support for WebSocket lifecycle hooks instead of a single
   handler function. Built upon [ws](https://github.com/websockets/ws) and
@@ -531,5 +541,5 @@ section.
   and lightweight Sequelize plugin for Fastify.
 
 #### [Community Tools](#community-tools)
-- [`fast-maker`](https://github.com/imjuni/fast-maker) route configuration generator by 
-  directory structure.
+- [`fast-maker`](https://github.com/imjuni/fast-maker) route configuration
+  generator by directory structure.

package/docs/Guides/Index.md

@@ -21,6 +21,8 @@ This table of contents is in alphabetical order.
   written with a fluent API and used in Fastify.
 + [Getting Started](./Getting-Started.md): Introduction tutorial for Fastify.
   This is where beginners should start.
++ [Migration Guide (v4)](./Migration-Guide-V4.md): Details how to migrate to
+  Fastify v4 from earlier versions.
 + [Migration Guide (v3)](./Migration-Guide-V3.md): Details how to migrate to
   Fastify v3 from earlier versions.
 + [Plugins Guide](./Plugins-Guide.md): An informal introduction to writing

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

@@ -0,0 +1,55 @@
+# V4 Migration Guide
+
+This guide is intended to help with migration from Fastify v3 to v4.
+
+Before migrating to v4, please ensure that you have fixed all deprecation
+warnings from v3. All v3 deprecations have been removed and they will no longer
+work after upgrading.
+
+## Breaking Changes
+
+### Deprecation of `app.use()`
+
+Starting this version of Fastify, we have deprecated the use of `app.use()`. We
+have decided not to support the use of middlewares. Both
+[`@fastify/middie`](https://github.com/fastify/middie) and
+[`@fastify/express`](https://github.com/fastify/fastify-express) will still be
+there and maintained. Use Fastify's [hooks](./Reference/Hooks.md) instead.
+
+## Non Breaking Changes
+
+### Change of schema for multiple types
+
+
+Since Fastiy v4 has upgraded to Ajv v8. The "type" keywords with multiple types
+(other than with "null") are prohibited. Read more
+['here'](https://ajv.js.org/strict-mode.html#strict-types)
+
+You may encounter a console warning such as
+
+```
+strict mode: use allowUnionTypes to allow union type keyword at "#/properties/image" (strictTypes)
+```
+So schemas like below will need to be changed from
+```
+type: 'object',
+properties: {
+  api_key: { type: 'string' },
+  image: { type: ['object', 'array'] }
+  }
+}
+```
+to
+
+```
+type: 'object',
+properties: {
+  api_key: { type: 'string' },
+  image: {
+    anyOf: [
+      { type: 'array' },
+      { type: 'object' }
+    ]
+  }
+}
+```

package/docs/Guides/Serverless.md

@@ -36,8 +36,9 @@ The sample provided allows you to easily build serverless web
 applications/services and RESTful APIs using Fastify on top of AWS Lambda and
 Amazon API Gateway.
 
-*Note: Using [@fastify/aws-lambda](https://github.com/fastify/aws-lambda-fastify)
-is just one possible way.*
+*Note: Using
+[@fastify/aws-lambda](https://github.com/fastify/aws-lambda-fastify) is just one
+possible way.*
 
 ### app.js
 
@@ -64,8 +65,7 @@ if (require.main === module) {
 
 When executed in your lambda function we do not need to listen to a specific
 port, so we just export the wrapper function `init` in this case. The
-[`lambda.js`](#lambdajs) file
-will use this export.
+[`lambda.js`](#lambdajs) file will use this export.
 
 When you execute your Fastify application like always, i.e. `node app.js` *(the
 detection for this could be `require.main === module`)*, you can normally listen
@@ -93,11 +93,10 @@ exports.handler = proxy;
 We just require
 [@fastify/aws-lambda](https://github.com/fastify/aws-lambda-fastify) (make sure
 you install the dependency `npm i @fastify/aws-lambda`) and our
-[`app.js`](#appjs) file and call
-the exported `awsLambdaFastify` function with the `app` as the only parameter.
-The resulting `proxy` function has the correct signature to be used as a lambda
-`handler` function. This way all the incoming events (API Gateway requests) are
-passed to the `proxy` function of
+[`app.js`](#appjs) file and call the exported `awsLambdaFastify` function with
+the `app` as the only parameter. The resulting `proxy` function has the correct
+signature to be used as a lambda `handler` function. This way all the incoming
+events (API Gateway requests) are passed to the `proxy` function of
 [@fastify/aws-lambda](https://github.com/fastify/aws-lambda-fastify).
 
 ### Example
@@ -237,7 +236,9 @@ gcloud functions logs read
 
 #### Example request to `/hello` endpoint
 ```bash
-curl -X POST https://$GOOGLE_REGION-$GOOGLE_PROJECT.cloudfunctions.net/me -H "Content-Type: application/json" -d '{ "name": "Fastify" }'
+curl -X POST https://$GOOGLE_REGION-$GOOGLE_PROJECT.cloudfunctions.net/me \
+  -H "Content-Type: application/json" \
+  -d '{ "name": "Fastify" }'
 {"message":"Hello Fastify!"}
 ```
 
@@ -443,8 +444,8 @@ 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:
+applications. To use it now, it is as simple as configuring your `vercel.json`
+file like the following:
 
 ```json
 {

package/docs/Reference/ContentTypeParser.md

@@ -2,12 +2,12 @@
 
 ## `Content-Type` Parser
 Natively, Fastify only supports `'application/json'` and `'text/plain'` content
-types. If the content type is not one of these, an `FST_ERR_CTP_INVALID_MEDIA_TYPE` 
-error will be thrown.
+types. If the content type is not one of these, an
+`FST_ERR_CTP_INVALID_MEDIA_TYPE` error will be thrown.
 
-The default charset is `utf-8`. If you need to support different content
-types, you can use the `addContentTypeParser` API. *The default JSON and/or
-plain text parser can be changed or removed.*
+The default charset is `utf-8`. If you need to support different content types,
+you can use the `addContentTypeParser` API. *The default JSON and/or plain text
+parser can be changed or removed.*
 
 *Note: If you decide to specify your own content type with the `Content-Type`
 header, UTF-8 will not be the default. Be sure to include UTF-8 like this
@@ -21,8 +21,11 @@ available only in that scope and its children.
 Fastify automatically adds the parsed request payload to the [Fastify
 request](./Request.md) object which you can access with `request.body`.
 
-Note that for `GET` and `HEAD` requests the payload is never parsed. For `OPTIONS` and `DELETE` requests the payload is only parsed if 
-the content type is given in the content-type header. If it is not given, the [catch-all](#catch-all) parser is not executed as with `POST`, `PUT` and `PATCH`, but the payload is simply not parsed.
+Note that for `GET` and `HEAD` requests the payload is never parsed. For
+`OPTIONS` and `DELETE` requests the payload is only parsed if the content type
+is given in the content-type header. If it is not given, the
+[catch-all](#catch-all) parser is not executed as with `POST`, `PUT` and
+`PATCH`, but the payload is simply not parsed.
 
 ### Usage
 ```js
@@ -69,7 +72,8 @@ more specific one, like in the example below.
 fastify.addContentTypeParser('application/vnd.custom+xml', (request, body, done) => {} )
 fastify.addContentTypeParser('application/vnd.custom', (request, body, done) => {} )
 
-// Here the desired behavior is achieved because fastify first tries to match the `application/vnd.custom+xml` content type parser
+// Here the desired behavior is achieved because fastify first tries to match the
+// `application/vnd.custom+xml` content type parser
 fastify.addContentTypeParser('application/vnd.custom', (request, body, done) => {} )
 fastify.addContentTypeParser('application/vnd.custom+xml', (request, body, done) => {} )
 ```
@@ -115,9 +119,9 @@ fastify.removeContentTypeParser(['application/json', 'text/plain'])
 In the example from just above, it is noticeable that we need to specify each
 content type that we want to remove. To solve this problem Fastify provides the
 `removeAllContentTypeParsers` API. This can be used to remove all currently
-existing content type parsers. In the example below we achieve the same
-as in the example above except that we do not need to specify each content type
-to delete. Just like `removeContentTypeParser`, this API supports encapsulation.
+existing content type parsers. In the example below we achieve the same as in
+the example above except that we do not need to specify each content type to
+delete. Just like `removeContentTypeParser`, this API supports encapsulation.
 The API is especially useful if you want to register a [catch-all content type
 parser](#catch-all) that should be executed for every content type and the
 built-in parsers should be ignored as well.
@@ -223,8 +227,8 @@ fastify.route({
 For piping file uploads you may want to check out [this
 plugin](https://github.com/fastify/fastify-multipart).
 
-If you want the content type parser to be executed on all content types
-and not only on those that don't have a specific one, you should call the
+If you want the content type parser to be executed on all content types and not
+only on those that don't have a specific one, you should call the
 `removeAllContentTypeParsers` method first.
 
 ```js

package/docs/Reference/Errors.md

@@ -54,9 +54,10 @@ When a custom error handler has been defined through
 receive the error passed to the `done()` callback (or through other supported
 automatic error handling mechanisms). If `setErrorHandler` has been used
 multiple times to define multiple handlers, the error will be routed to the most
-precedent handler defined within the error [encapsulation context](./Encapsulation.md).
-Error handlers are fully encapsulated, so a `setErrorHandler` call within a
-plugin will limit the error handler to that plugin's context.
+precedent handler defined within the error [encapsulation
+context](./Encapsulation.md). Error handlers are fully encapsulated, so a
+`setErrorHandler` call within a plugin will limit the error handler to that
+plugin's context.
 
 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
@@ -72,8 +73,8 @@ Some things to consider in your custom error handler:
   - strings, buffers, and streams are sent to the client, with appropriate
     headers (no serialization)
 
-- You can throw a new error in your custom error handler
-	- errors (new error or the received error parameter re-thrown) - will call the parent `errorHandler`.
+- You can throw a new error in your custom error handler - errors (new error or
+	the received error parameter re-thrown) - will call the parent `errorHandler`.
   - `onError` hook will be triggered once only for the first error being thrown.
   - an error will not be triggered twice from a lifecycle hook - Fastify
     internally monitors the error invocation to avoid infinite loops for errors

package/docs/Reference/Plugins.md

@@ -9,10 +9,12 @@ By default, `register` creates a *new scope*, this means that if you make some
 changes to the Fastify instance (via `decorate`), this change will not be
 reflected by the current context ancestors, but only by its descendants. This
 feature allows us to achieve plugin *encapsulation* and *inheritance*, in this
-way we create a *directed acyclic graph* (DAG) and we will not have issues caused
-by cross dependencies.
+way we create a *directed acyclic graph* (DAG) and we will not have issues
+caused by cross dependencies.
 
-You may have already seen in the [Getting Started]((../Guides/Getting-Started.md#your-first-plugin)) guide how easy it is to use this API:
+You may have already seen in the [Getting
+Started]((../Guides/Getting-Started.md#your-first-plugin)) guide how easy it is
+to use this API:
 ```
 fastify.register(plugin, [options])
 ```
@@ -96,9 +98,9 @@ If you pass an option with the key `prefix` with a `string` value, Fastify will
 use it to prefix all the routes inside the register, for more info check
 [here](./Routes.md#route-prefixing).
 
-Be aware that if you use
-[`fastify-plugin`](https://github.com/fastify/fastify-plugin) this option will
-not work.
+Be aware that if you wrap your routes with
+[`fastify-plugin`](https://github.com/fastify/fastify-plugin), this option will
+not work (there is a [workaround](./Routes.md#fastify-plugin) available).
 
 #### Error handling
 <a id="error-handling"></a>

package/docs/Reference/Reply.md

@@ -129,7 +129,11 @@ 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 [`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 will result in a 500 `TypeError` response.
+> 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
+> will result in a 500 `TypeError` response.
 
 For more information, see
 [`http.ServerResponse#setHeader`](https://nodejs.org/dist/latest-v14.x/docs/api/http.html#http_response_setheader_name_value).
@@ -208,11 +212,16 @@ Returns a boolean indicating if the specified header has been set.
 ### .trailer(key, function)
 <a id="trailer"></a>
 
-Sets a response trailer. Trailer is usually used when you need a header that 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.
+Sets a response trailer. Trailer is usually used when you need a header that
+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 the trailer. It is a hard requirement for using trailer in Node.js.*
+*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: Currently, the computation function only supports synchronous function. That means `async-await` and `promise` are not supported.*
+*Note: Currently, the computation function only supports synchronous function.
+That means `async-await` and `promise` are not supported.*
 
 ```js
 reply.trailer('server-timing', function() {
@@ -254,7 +263,11 @@ 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 [`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 result in a 500 `TypeError` response.
+> 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
+> result in a 500 `TypeError` response.
 
 Example (no `reply.code()` call) sets status code to `302` and redirects to
 `/home`
@@ -310,7 +323,8 @@ Sets the content type for the response. This is a shortcut for
 ```js
 reply.type('text/html')
 ```
-If the `Content-Type` has a JSON subtype, and the charset parameter is not set, `utf-8` will be used as the charset by default.
+If the `Content-Type` has a JSON subtype, and the charset parameter is not set,
+`utf-8` will be used as the charset by default.
 
 ### .serializer(func)
 <a id="serializer"></a>
@@ -366,22 +380,22 @@ Another example of the misuse of `Reply.raw` is explained in
 <a id="sent"></a>
 
 As the name suggests, `.sent` is a property to indicate if a response has been
-sent via `reply.send()`.
-It will also be `true` in case `reply.hijack()` was used.
+sent via `reply.send()`. It will also be `true` in case `reply.hijack()` was
+used.
 
 In case a route handler is defined as an async function or it returns a promise,
 it is possible to call `reply.hijack()` to indicate that the automatic
 invocation of `reply.send()` once the handler promise resolve should be skipped.
-By calling `reply.hijack()`, an application claims full responsibility for
-the low-level request and response. Moreover, hooks will not be invoked.
+By calling `reply.hijack()`, an application claims full responsibility for the
+low-level request and response. Moreover, hooks will not be invoked.
 
-*Modifying the `.sent` property directly is deprecated. Please use the aforementioned
-`.hijack()` method to achieve the same effect.*
+*Modifying the `.sent` property directly is deprecated. Please use the
+aforementioned `.hijack()` method to achieve the same effect.*
 
 <a name="hijack"></a>
 ### .hijack()
-Sometimes you might need to halt the execution of the normal request lifecycle and
-handle sending the response manually.
+Sometimes you might need to halt the execution of the normal request lifecycle
+and handle sending the response manually.
 
 To achieve this, Fastify provides the `reply.hijack()` method that can be called
 during the request lifecycle (At any point before `reply.send()` is called), and
@@ -561,8 +575,8 @@ fastify.setNotFoundHandler(function (request, reply) {
 <a id="payload-type"></a>
 
 The type of the sent payload (after serialization and going through any
-[`onSend` hooks](./Hooks.md#onsend)) must be one of the following
-types, otherwise, an error will be thrown:
+[`onSend` hooks](./Hooks.md#onsend)) must be one of the following types,
+otherwise, an error will be thrown:
 
 - `string`
 - `Buffer`

package/docs/Reference/Request.md

@@ -13,7 +13,7 @@ Request is a core Fastify object containing the following fields:
 - [`headers`](#headers) - the headers getter and setter
 - `raw` - the incoming HTTP request from Node core
 - `server` - The Fastify server instance, scoped to the current [encapsulation
->>>>>>> main:docs/Reference/Request.md
+  context](./Encapsulation.md)
 - `id` - the request ID
 - `log` - the logger instance of the incoming request
 - `ip` - the IP address of the incoming request
@@ -55,8 +55,8 @@ This operation will add to the request headers the new values that can be read
 calling `request.headers.bar`. Moreover, you can still access the standard
 request's headers with the `request.raw.headers` property.
 
-> Note: For performance reason on `not found` route, you may see that we will add
-an extra property `Symbol('fastify.RequestAcceptVersion')` on the headers.
+> Note: For performance reason on `not found` route, you may see that we will
+add an extra property `Symbol('fastify.RequestAcceptVersion')` on the headers.
 
 ```js
 fastify.post('/:params', options, function (request, reply) {