fastify 5.9.0 → 5.10.0

package/PROJECT_CHARTER.md

@@ -50,7 +50,7 @@ experience with the least overhead and a plugin architecture.
 
 Technical leadership for the projects within the [OpenJS Foundation][openjs
 foundation] is delegated to the projects through their project charters by the
-[OpenJS Foundation Cross-Project Council](https://openjsf.org/about/governance/)
+[OpenJS Foundation Cross-Project Council](https://openjsf.org/governance)
 (CPC). In the case of the Fastify project, it is delegated to the [Fastify
 Collaborators](README.md#team). The OpenJS Foundation's business leadership is
 the Board of Directors (the "Board").

package/README.md

@@ -1,6 +1,6 @@
 <div align="center"> <a href="https://fastify.dev/">
     <img
-      src="https://github.com/fastify/graphics/raw/HEAD/fastify-landscape-outlined.svg"
+      src="https://raw.githubusercontent.com/fastify/graphics/HEAD/fastify-landscape-outlined.svg"
       width="650"
       height="auto"
     />
@@ -15,7 +15,7 @@ CI](https://github.com/fastify/fastify/actions/workflows/package-manager-ci.yml/
 [![Web
 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)
+[![CII Best Practices](https://www.bestpractices.dev/projects/7585/badge)](https://www.bestpractices.dev/en/projects/7585/passing)
 
 </div>
 
@@ -27,7 +27,7 @@ version](https://img.shields.io/npm/v/fastify.svg?style=flat)](https://www.npmjs
 downloads](https://img.shields.io/npm/dm/fastify.svg?style=flat)](https://www.npmjs.com/package/fastify)
 [![Security Responsible
 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)
+[![Discord](https://img.shields.io/discord/725613461949906985)](https://discord.com/invite/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)](https://github.com/sponsors/fastify#sponsors)
 
@@ -253,8 +253,8 @@ application. You should __always__ benchmark if performance matters to you.
   plugins.
 - [Live Examples](https://github.com/fastify/example) - Multirepo with a broad
   set of real working examples.
-- [Discord](https://discord.gg/D3FZYPy) - Join our discord server and chat with
-  the maintainers.
+- [Discord](https://discord.com/invite/D3FZYPy) - Join our discord server and
+  chat with the maintainers.
 
 ## Support
 Please visit [Fastify help](https://github.com/fastify/help) to view prior
@@ -312,7 +312,7 @@ listed in alphabetical order.
 * [__KaKa Ng__](https://github.com/climba03003),
   <https://www.npmjs.com/~climba03003>
 * [__Luis Orbaiceta__](https://github.com/luisorbaiceta),
-  <https://x.com/luisorbai>, <https://www.npmjs.com/~luisorbaiceta>
+  <https://www.npmjs.com/~luisorbaiceta>
 * [__Maksim Sinik__](https://github.com/fox1t),
   <https://x.com/maksimsinik>, <https://www.npmjs.com/~fox1t>
 * [__Manuel Spigolon__](https://github.com/eomm),
@@ -383,7 +383,7 @@ active contributor's group.
 ## Hosted by
 
 [<img
-src="https://github.com/openjs-foundation/artwork/blob/main/openjs_foundation/openjs_foundation-logo-horizontal-color.png?raw=true"
+src="https://raw.githubusercontent.com/openjs-foundation/artwork/main/openjs_foundation/openjs_foundation-logo-horizontal-color.png"
 width="250px;"/>](https://openjsf.org/projects)
 
 We are an [At-Large
@@ -402,9 +402,6 @@ This project is kindly sponsored by:
 - [NearForm](https://nearform.com)
 - [Platformatic](https://platformatic.dev)
 
-Past Sponsors:
-- [LetzDoIt](https://www.letzdoitapp.com/)
-
 This list includes all companies that support one or more team members
 in maintaining this project.
 

package/build/build-validation.js

@@ -32,7 +32,7 @@ const defaultInitOptions = {
   bodyLimit: 1024 * 1024, // 1 MiB
   caseSensitive: true,
   allowUnsafeRegex: false,
-  disableRequestLogging: false,
+  disableRequestLogging: false, // TODO: remove it in v6
   ignoreTrailingSlash: false,
   ignoreDuplicateSlashes: false,
   maxParamLength: 100,
@@ -40,7 +40,7 @@ const defaultInitOptions = {
   onConstructorPoisoning: 'error',
   pluginTimeout: 10000,
   requestIdHeader: false,
-  requestIdLogLabel: 'reqId',
+  requestIdLogLabel: 'reqId', // TODO: remove it in v6
   http2SessionTimeout: 72000, // 72 seconds
   exposeHeadRoutes: true,
   useSemicolonDelimiter: false,

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

@@ -447,7 +447,7 @@ served until we have everything ready. And there's more: we fail **FAST** and
 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
+code](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/503) we're
 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`

package/docs/Guides/Ecosystem.md

@@ -144,7 +144,7 @@ section.
 - [`@fastify/view`](https://github.com/fastify/point-of-view) Templates
   rendering (_ejs, pug, handlebars, marko_) plugin support for Fastify.
 - [`@fastify/vite`](https://github.com/fastify/fastify-vite) Integration with
-  [Vite](https://vitejs.dev/), allows for serving SPA/MPA/SSR Vite applications.
+  [Vite](https://vite.dev/), allows for serving SPA/MPA/SSR Vite applications.
 - [`@fastify/websocket`](https://github.com/fastify/fastify-websocket) WebSocket
   support for Fastify. Built upon [ws](https://github.com/websockets/ws).
 - [`@fastify/zipkin`](https://github.com/fastify/fastify-zipkin) Plugin
@@ -196,7 +196,7 @@ section.
   Run REST APIs and other web applications using your existing Node.js
   application framework (Express, Koa, Hapi and Fastify), on top of AWS Lambda,
   Huawei and many other clouds.
-- [`@hey-api/openapi-ts`](https://heyapi.dev/openapi-ts/plugins/fastify)
+- [`@hey-api/openapi-ts`](https://heyapi.dev/docs/openapi/typescript/plugins/fastify)
   The OpenAPI to TypeScript codegen. Generate clients, SDKs, validators, and more.
 - [`@immobiliarelabs/fastify-metrics`](https://github.com/immobiliare/fastify-metrics)
   Minimalistic and opinionated plugin that collects usage/process metrics and
@@ -232,6 +232,9 @@ section.
   Plugin to generate routes automatically with valid json content
 - [`@scalar/fastify-api-reference`](https://github.com/scalar/scalar/tree/main/integrations/fastify)
   Beautiful OpenAPI/Swagger API references for Fastify
+- [`@stitchapi/fastify`](https://github.com/rejifald/StitchAPI/tree/main/packages/fastify)
+  Decorate the app/request with a StitchAPI seam — request-scoped principal, SSE
+  streaming, error mapping, and a Pino-logger bridge.
 - [`@thecodepace/fastify-http-query`](https://github.com/TheCodePace/fastify-http-query)
   Fastify plugin enabling the HTTP `QUERY` method (a safe, idempotent, cacheable
   method with a body).
@@ -289,8 +292,8 @@ section.
   validator, keeping Fastify's default error shape.
 - [`fastify-auth0-verify`](https://github.com/nearform/fastify-auth0-verify):
   Auth0 verification plugin for Fastify, internally uses
-  [fastify-jwt](https://npm.im/fastify-jwt) and
-  [jsonwebtoken](https://npm.im/jsonwebtoken).
+  [fastify-jwt](https://www.npmjs.com/package/fastify-jwt) and
+  [jsonwebtoken](https://www.npmjs.com/package/jsonwebtoken).
 - [`fastify-autoroutes`](https://github.com/GiovanniCardamone/fastify-autoroutes)
   Plugin to scan and load routes based on filesystem path from a custom
   directory.
@@ -390,7 +393,7 @@ section.
 - [`fastify-formidable`](https://github.com/climba03003/fastify-formidable)
   Handy plugin to provide multipart support and fastify-swagger integration.
 - [`fastify-gcloud-trace`](https://github.com/mkinoshi/fastify-gcloud-trace)
-  [Google Cloud Trace API](https://cloud.google.com/trace/docs/reference)
+  [Google Cloud Trace API](https://docs.cloud.google.com/trace/docs/reference)
   Connector for Fastify.
 - [`fastify-get-head`](https://github.com/MetCoder95/fastify-get-head) Small
   plugin to set a new HEAD route handler for each GET route previously
@@ -561,7 +564,7 @@ middlewares into Fastify plugins
   to handle i18n using
   [node-polyglot](https://www.npmjs.com/package/node-polyglot).
 - [`fastify-postgraphile`](https://github.com/alemagio/fastify-postgraphile)
-  Plugin to integrate [PostGraphile](https://www.graphile.org/postgraphile/) in
+  Plugin to integrate [PostGraphile](https://postgraphile.org/postgraphile/4/) in
   a Fastify project.
 - [`fastify-postgres-dot-js`](https://github.com/kylerush/fastify-postgresjs) Fastify
   PostgreSQL connection plugin that uses [Postgres.js](https://github.com/porsager/postgres).
@@ -679,7 +682,7 @@ middlewares into Fastify plugins
   multiple subdomains to the same IP address, while running different servers on
   the same machine).
 - [`fastify-vue-plugin`](https://github.com/TheNoim/fastify-vue)
-  [Nuxt.js](https://nuxtjs.org) plugin for Fastify. Control the routes nuxt
+  [Nuxt.js](https://nuxt.com) plugin for Fastify. Control the routes nuxt
   should use.
 - [`fastify-wamp-router`](https://github.com/lependu/fastify-wamp-router) Web
   Application Messaging Protocol router for Fastify.

package/docs/Guides/Getting-Started.md

@@ -605,10 +605,10 @@ npm start
 
 - Slides
   - [Take your HTTP server to ludicrous
-    speed](https://mcollina.github.io/take-your-http-server-to-ludicrous-speed)
+    speed](https://mcollina.github.io/take-your-http-server-to-ludicrous-speed/)
     by [@mcollina](https://github.com/mcollina)
   - [What if I told you that HTTP can be
-    fast](https://delvedor.github.io/What-if-I-told-you-that-HTTP-can-be-fast)
+    fast](https://delvedor.dev/What-if-I-told-you-that-HTTP-can-be-fast/)
     by [@delvedor](https://github.com/delvedor)
 
 - Videos

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

@@ -10,7 +10,7 @@ work after upgrading.
 ### Fastify v4 Codemods
 
 To help with the upgrade, we’ve worked with the team at
-[Codemod](https://github.com/codemod-com/codemod) to
+[Codemod](https://github.com/codemod/codemod) to
 publish codemods that will automatically update your code to many of
 the new APIs and patterns in Fastify v4.
 
@@ -264,4 +264,4 @@ Into:
 Fastify now supports the [HTTP Trailer] response headers.
 
 
-[HTTP Trailer]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Trailer
+[HTTP Trailer]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Trailer

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

@@ -105,7 +105,7 @@ const fastify = require('fastify')({
 Starting with v5, Fastify instances will no longer default to supporting the use
 of semicolon delimiters in the query string as they did in v4.
 This is due to it being non-standard
-behavior and not adhering to [RFC 3986](https://www.rfc-editor.org/rfc/rfc3986#section-3.4).
+behavior and not adhering to [RFC 3986](https://datatracker.ietf.org/doc/html/rfc3986#section-3.4).
 
 If you still wish to use semicolons as delimiters, you can do so by
 setting `useSemicolonDelimiter: true` in the server configuration.

package/docs/Guides/Plugins-Guide.md

@@ -507,7 +507,7 @@ section of our documentation!
 
 If you want to see some real-world examples, check out:
 - [`@fastify/view`](https://github.com/fastify/point-of-view) Templates
-  rendering (*ejs, pug, handlebars, marko*) plugin support for Fastify.
+  rendering (*ejs, pug, handlebars*) plugin support for Fastify.
 - [`@fastify/mongodb`](https://github.com/fastify/fastify-mongodb) Fastify
   MongoDB connection plugin, with this you can share the same MongoDB connection
   pool in every part of your server.

package/docs/Guides/Prototype-Poisoning.md

@@ -232,7 +232,7 @@ itself), it is much harder getting it fixed.
 
 The first question people ask once a security issue is found is if there is
 going to be a CVE published. A CVE — Common Vulnerabilities and Exposures — is a
-[database](https://cve.mitre.org/) of known security issues. It is a critical
+[database](https://www.cve.org/) of known security issues. It is a critical
 component of web security. The benefit of publishing a CVE is that it
 immediately triggers alarms and informs and often breaks automated builds until
 the issue is resolved.
@@ -376,8 +376,8 @@ source maintainers.
 Because this work is important, I decided to try and make it not just
 financially sustainable but to grow and expand it. There is so much to improve.
 This is exactly what motivates me to implement the new [commercial licensing
-plan](https://web.archive.org/web/20190201220503/https://hueniverse.com/on-hapi-licensing-a-preview-f982662ee898)
+plan](https://web.archive.org/web/20190201220503/https://hueniverse.com/on-hapi-licensing-a-preview-f982662ee898?gi=b54e9a75bac6)
 coming in March. You can read more about it
-[here](https://web.archive.org/web/20190201220503/https://hueniverse.com/on-hapi-licensing-a-preview-f982662ee898).
+[here](https://web.archive.org/web/20190201220503/https://hueniverse.com/on-hapi-licensing-a-preview-f982662ee898?gi=b54e9a75bac6).
 
 

package/docs/Guides/Serverless.md

@@ -109,13 +109,6 @@ 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
-
-An example deployable with
-[claudia.js](https://claudiajs.com/tutorials/serverless-express.html) can be
-found
-[here](https://github.com/claudiajs/example-projects/tree/master/fastify-app-lambda).
-
 ### Considerations
 
 - API Gateway does not support streams yet, so you are not able to handle
@@ -126,7 +119,7 @@ found
 #### Beyond API Gateway
 
 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)
+[@h4ad/serverless-adapter](https://serverless-adapter.viniciusl.com.br/docs/main/frameworks/fastify)
 on Fastify to find out how to integrate.
 
 ## Genezio
@@ -134,7 +127,7 @@ on Fastify to find out how to integrate.
 [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/)
+[Genezio has a dedicated guide for deploying a Fastify application.](https://deployapps.dev/docs/frameworks/fastify/)
 
 ## Google Cloud Functions
 
@@ -265,7 +258,7 @@ curl -X POST https://$GOOGLE_REGION-$GOOGLE_PROJECT.cloudfunctions.net/me \
 
 ### References
 - [Google Cloud Functions - Node.js Quickstart
-  ](https://cloud.google.com/functions/docs/quickstart-nodejs)
+  ](https://docs.cloud.google.com/run/docs/quickstarts/functions/deploy-functions-gcloud)
 
 ## Google Firebase Functions
 
@@ -403,7 +396,7 @@ the way you would write your Fastify app normally.
 
 *Follow the steps below to deploy to Google Cloud Run if you are already
 familiar with gcloud or just follow their
-[quickstart](https://cloud.google.com/run/docs/quickstarts/build-and-deploy)*.
+[quickstart](https://docs.cloud.google.com/run/docs/quickstarts)*.
 
 ### Adjust Fastify server
 
@@ -590,7 +583,7 @@ Then it should work fine.
 
 [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
+[Fluid compute](https://vercel.com/docs/fluid-compute), you can combine
 server-like concurrency with the autoscaling properties of traditional
 serverless functions.
 
@@ -598,7 +591,7 @@ Get started with the
 [Fastify template on Vercel](
 https://vercel.com/templates/backend/fastify-on-vercel).
 
-[Fluid compute](https://vercel.com/docs/functions/fluid-compute) currently
+[Fluid compute](https://vercel.com/docs/fluid-compute) currently
 requires an explicit opt-in. Learn more about enabling Fluid compute
 [here](
 https://vercel.com/docs/fluid-compute#enabling-fluid-compute).

package/docs/Guides/Style-Guide.md

@@ -13,7 +13,7 @@ This guide is for anyone who loves to build with Fastify or wants to contribute
 to our documentation. You do not need to be an expert in writing technical
 documentation. This guide is here to help you.
 
-Visit the [contribute](https://fastify.dev/contribute) page on our website or
+Visit the [contribute](https://fastify.dev/contribute/) page on our website or
 read the
 [CONTRIBUTING.md](https://github.com/fastify/fastify/blob/main/CONTRIBUTING.md)
 file on GitHub to join our Open Source folks.

package/docs/Reference/Errors.md

@@ -49,6 +49,7 @@
     - [FST_ERR_LOG_INVALID_LOGGER_INSTANCE](#fst_err_log_invalid_logger_instance)
     - [FST_ERR_LOG_INVALID_LOGGER_CONFIG](#fst_err_log_invalid_logger_config)
     - [FST_ERR_LOG_LOGGER_AND_LOGGER_INSTANCE_PROVIDED](#fst_err_log_logger_and_logger_instance_provided)
+    - [FST_ERR_LOG_INVALID_LOG_CONTROLLER](#fst_err_log_invalid_log_controller)
     - [FST_ERR_REP_INVALID_PAYLOAD_TYPE](#fst_err_rep_invalid_payload_type)
     - [FST_ERR_REP_RESPONSE_BODY_CONSUMED](#fst_err_rep_response_body_consumed)
     - [FST_ERR_REP_READABLE_STREAM_LOCKED](#fst_err_rep_readable_stream_locked)
@@ -327,6 +328,7 @@ Below is a table with all the error codes used by Fastify.
 | <a id="fst_err_log_invalid_logger_instance">FST_ERR_LOG_INVALID_LOGGER_INSTANCE</a> | The `loggerInstance` only accepts a logger instance, not a configuration object. | To pass a configuration object, use `'logger'` instead. | [#5020](https://github.com/fastify/fastify/pull/5020) |
 | <a id="fst_err_log_invalid_logger_config">FST_ERR_LOG_INVALID_LOGGER_CONFIG</a> | The logger option only accepts a configuration object, not a logger instance. | To pass an instance, use `'loggerInstance'` instead.  | [#5020](https://github.com/fastify/fastify/pull/5020) |
 | <a id="fst_err_log_logger_and_logger_instance_provided">FST_ERR_LOG_LOGGER_AND_LOGGER_INSTANCE_PROVIDED</a> | You cannot provide both `'logger'` and `'loggerInstance'`. | Please provide only one option.  | [#5020](https://github.com/fastify/fastify/pull/5020) |
+| <a id="fst_err_log_invalid_log_controller">FST_ERR_LOG_INVALID_LOG_CONTROLLER</a> | The `logController` option must be an instance of `LogController`. | Extend the `LogController` class and pass an instance. | - |
 | <a id="fst_err_rep_invalid_payload_type">FST_ERR_REP_INVALID_PAYLOAD_TYPE</a> | Reply payload can be either a `string` or a `Buffer`. | Use a `string` or a `Buffer` for the payload. | [#1168](https://github.com/fastify/fastify/pull/1168) |
 | <a id="fst_err_rep_response_body_consumed">FST_ERR_REP_RESPONSE_BODY_CONSUMED</a> | Using `Response` as reply payload, but the body is being consumed. | Make sure you don't consume the `Response.body` | [#5286](https://github.com/fastify/fastify/pull/5286) |
 | <a id="fst_err_rep_readable_stream_locked">FST_ERR_REP_READABLE_STREAM_LOCKED</a> | Using `ReadableStream` as reply payload, but locked with another reader. | Make sure you don't call the `Readable.getReader` before sending or release lock with `reader.releaseLock()` before sending. | [#5920](https://github.com/fastify/fastify/pull/5920) |

package/docs/Reference/Hooks.md

@@ -51,7 +51,7 @@ It is easy to understand where each hook is executed by looking at the
 Hooks are affected by Fastify's encapsulation, and can thus be applied to
 selected routes. See the [Scopes](#scope) section for more information.
 
-There are eight different hooks that you can use in Request/Reply *(in order of
+There are ten different hooks that you can use in Request/Reply *(in order of
 execution)*:
 
 ### onRequest

package/docs/Reference/Logging.md

@@ -13,6 +13,9 @@ As Fastify is focused on performance, it uses
 [pino](https://github.com/pinojs/pino) as its logger, with the default log
 level set to `'info'` when enabled.
 
+The log level can be set per-route. See [the routes
+documentation](./Routes.md#custom-log-level).
+
 #### Basic Logging Setup
 The following enables the production JSON logger:
 

package/docs/Reference/Request.md

@@ -132,14 +132,14 @@ fastify.post('/:params', options, function (request, reply) {
   console.log(request.url)
   console.log(request.routeOptions.method)
   console.log(request.routeOptions.bodyLimit)
-  console.log(request.routeOptions.method)
+  console.log(request.routeOptions.handlerTimeout)
   console.log(request.routeOptions.url)
   console.log(request.routeOptions.attachValidation)
   console.log(request.routeOptions.logLevel)
   console.log(request.routeOptions.version)
   console.log(request.routeOptions.exposeHeadRoute)
   console.log(request.routeOptions.prefixTrailingSlash)
-  console.log(request.routeOptions.logLevel)
+  console.log(request.routeOptions.config)
   request.log.info('some info')
 })
 ```

package/docs/Reference/Server.md

@@ -23,6 +23,7 @@ describes the properties available in that options object.
   - [`logger`](#logger)
   - [`loggerInstance`](#loggerinstance)
   - [`disableRequestLogging`](#disablerequestlogging)
+  - [`logController`](#logcontroller)
   - [`serverFactory`](#serverfactory)
   - [`requestIdHeader`](#requestidheader)
   - [`requestIdLogLabel`](#requestidloglabel)
@@ -389,6 +390,10 @@ Pino interface by having the following methods: `info`, `error`, `debug`,
 ### `disableRequestLogging`
 <a id="factory-disable-request-logging"></a>
 
+> **Deprecated:** Use the [`logController`](#log-controller) option with
+> `disableRequestLogging` or `isLogDisabled` override instead.
+> This top-level option will be removed in `fastify@6`.
+
 + Default: `false`
 
 When logging is enabled, Fastify will issue an `info` level log
@@ -402,13 +407,23 @@ and returns a boolean. This allows for conditional request logging based on the
 request properties (e.g., URL, headers, decorations).
 
 ```js
+// Deprecated
 const fastify = require('fastify')({
   logger: true,
   disableRequestLogging: (request) => {
-    // Disable logging for health check endpoints
     return request.url === '/health' || request.url === '/ready'
   }
 })
+
+// Recommended: use logController instead
+const fastify = require('fastify')({
+  logger: true,
+  logController: {
+    disableRequestLogging: (request) => {
+      return request.url === '/health' || request.url === '/ready'
+    }
+  }
+})
 ```
 
 The other log entries that will be disabled are:
@@ -435,6 +450,86 @@ fastify.addHook('onResponse', (req, reply, done) => {
 })
 ```
 
+### `logController`
+<a id="factory-log-controller"></a>
+
++ Default: `undefined`
+
+Accepts an instance of `LogController` (or a subclass) to customize Fastify's
+internal log lines. Extend the `LogController` class and override only the
+methods you want to customize; all others keep their default behavior.
+
+The `LogController` class is exported from `fastify`:
+
+```js
+const { LogController } = require('fastify')
+```
+
+The constructor accepts an optional options object:
+
+| Property | Type | Default | Description |
+|----------|------|---------|-------------|
+| `disableRequestLogging` | `boolean \| (req) => boolean` | `false` | When `true` (or a function returning `true`), per-request log lines are suppressed. |
+| `requestIdLogLabel` | `string` | `'reqId'` | The label used for the request identifier when logging. |
+
+```js
+const { LogController } = require('fastify')
+
+class MyLogController extends LogController {
+  constructor () {
+    super({
+      requestIdLogLabel: 'traceId',
+      disableRequestLogging: (request) => {
+        return request.url === '/health'
+      }
+    })
+  }
+
+  incomingRequest (request, reply, metadata) {
+    // Use debug level instead of info for incoming requests
+    request.log.debug({ req: request }, 'incoming request')
+  }
+
+  requestCompleted (error, request, reply, metadata) {
+    // Add custom fields to the request completed log
+    if (error) {
+      reply.log.error({ res: reply, err: error, responseTime: reply.elapsedTime, customField: 'value' }, 'request errored')
+    } else {
+      reply.log.info({ res: reply, responseTime: reply.elapsedTime, customField: 'value' }, 'request completed')
+    }
+  }
+}
+
+const fastify = require('fastify')({
+  logger: true,
+  logController: new MyLogController()
+})
+```
+
+The error-related methods share a unified signature:
+`(error, request, reply, metadata)`, where `metadata` carries any extra
+per-method data (for example, the `statusCode` passed to `serializerError`).
+`incomingRequest` and `routeNotFound` omit the `error` argument, since they fire
+at lifecycle points where no error exists. `serviceUnavailable` is a further
+exception, since no route — and therefore no `request`/`reply` — is formed.
+
+| Method | Signature | Description |
+|--------|-----------|-------------|
+| `isLogDisabled` | `(request)` | Checks whether request logging is disabled for the given request. It impacts all other log methods. |
+| `incomingRequest` | `(request, reply, metadata)` | Logs an incoming request at `info` level. |
+| `requestCompleted` | `(error, request, reply, metadata)` | Logs the outcome of a completed request. Uses `error` level when an error is present, `info` otherwise. |
+| `defaultErrorLog` | `(error, request, reply, metadata)` | Logs an error handled by the default error handler. Uses `error` for 5xx, `info` for 4xx. |
+| `streamError` | `(error, request, reply, metadata)` | Logs stream-level errors after headers have been sent. |
+| `routeNotFound` | `(request, reply, metadata)` | Logs a "route not found" message at `info` level. |
+| `writeHeadError` | `(error, request, reply, metadata)` | Logs a warning when `writeHead` fails during error handling. |
+| `serializerError` | `(error, request, reply, metadata)` | Logs an error when the serializer for a given status code fails. The triggering status code is available as `metadata.statusCode`. |
+| `serviceUnavailable` | `(logger, server)` | Logs a 503 when the server is closing. Always emitted, not gated by `disableRequestLogging`. |
+
+**Note:** When you override a method, you take full control of it — the
+default `disableRequestLogging` check is **not** automatically applied.
+If you need conditional logging, call `this.isLogDisabled(request)` yourself
+or override `isLogDisabled` as well.
+
 ### `serverFactory`
 <a id="custom-http-server"></a>
 
@@ -501,6 +596,9 @@ const fastify = require('fastify')({
 ### `requestIdLogLabel`
 <a id="factory-request-id-log-label"></a>
 
+> **Deprecated:** Use the [`logController`](#log-controller) option with
+> `requestIdLogLabel` instead. This top-level option will be removed in `fastify@6`.
+
 + Default: `'reqId'`
 
 Defines the label used for the request identifier when logging the request.
@@ -519,9 +617,9 @@ generation behavior as shown below. For generating `UUID`s you may want to check
 out [hyperid](https://github.com/mcollina/hyperid).
 
 > ℹ️ Note:
-> `genReqId` will be not called if the header set in
+> `genReqId` will not be called if the header set in
 > <code>[requestIdHeader](#requestidheader)</code> is available (defaults to
-> 'request-id').
+> `false`).
 
 ```js
 let i = 0
@@ -853,7 +951,7 @@ function to sanitize a route's store object to use with the `prettyPrint`
 functions. This function should accept a single object and return an object.
 
 ```js
-fastify.get('/user/:username', (request, reply) => {
+const fastify = require('fastify')({
   routerOptions: {
     buildPrettyMeta: route => {
       const cleanMeta = Object.assign({}, route.store)
@@ -864,7 +962,7 @@ fastify.get('/user/:username', (request, reply) => {
       })
 
       return cleanMeta // this will show up in the pretty print output!
-    })
+    }
   }
 })
 ```
@@ -1068,8 +1166,9 @@ objects and do not provide Fastify's decorated helpers.
 ### `querystringParser`
 <a id="querystringparser"></a>
 
-The default query string parser that Fastify uses is the Node.js's core
-`querystring` module.
+The default query string parser that Fastify uses is a more performant fork
+of Node.js's core `querystring` module called
+[`fast-querystring`](https://github.com/anonrig/fast-querystring).
 
 You can use this option to use a custom parser, such as
 [`qs`](https://www.npmjs.com/package/qs).
@@ -1090,7 +1189,7 @@ You can also use Fastify's default parser but change some handling behavior,
 like the example below for case insensitive keys and values:
 
 ```js
-const querystring = require('node:querystring')
+const querystring = require('fast-querystring')
 const fastify = require('fastify')({
   routerOptions: {
     querystringParser: str => querystring.parse(str.toLowerCase())

package/docs/Reference/Type-Providers.md

@@ -34,10 +34,10 @@ $ npm i @fastify/type-provider-json-schema-to-ts
 ```
 
 ```typescript
-import fastify from 'fastify'
+import Fastify from 'fastify'
 import { JsonSchemaToTsProvider } from '@fastify/type-provider-json-schema-to-ts'
 
-const server = fastify().withTypeProvider<JsonSchemaToTsProvider>()
+const server = Fastify().withTypeProvider<JsonSchemaToTsProvider>()
 
 server.get('/route', {
   schema: {
@@ -57,6 +57,26 @@ server.get('/route', {
 })
 ```
 
+When using raw JSON Schema objects with `JsonSchemaToTsProvider`, TypeScript
+must be able to see the exact literal values in the schema. Inline schemas, like
+the example above, are inferred from the route call. If the schema is moved into
+a separate variable, use `as const`:
+
+```typescript
+const querystringSchema = {
+  type: 'object',
+  properties: {
+    foo: { type: 'number' },
+    bar: { type: 'string' },
+  },
+  required: ['foo', 'bar']
+} as const
+```
+
+Without `as const`, TypeScript may widen schema values such as `type: 'object'`
+to `type: string`, which prevents `json-schema-to-ts` from inferring the route
+types. This assertion has no effect on the schema used by Fastify at runtime.
+
 ### TypeBox
 
 The following sets up a TypeBox Type Provider:
@@ -66,11 +86,11 @@ $ npm i typebox @fastify/type-provider-typebox
 ```
 
 ```typescript
-import fastify from 'fastify'
+import Fastify from 'fastify'
 import { TypeBoxTypeProvider } from '@fastify/type-provider-typebox'
 import { Type } from 'typebox'
 
-const server = fastify().withTypeProvider<TypeBoxTypeProvider>()
+const server = Fastify().withTypeProvider<TypeBoxTypeProvider>()
 
 server.get('/route', {
   schema: {

package/docs/Reference/TypeScript.md

@@ -658,8 +658,8 @@ unfortunate limitation of using TypeScript and is unavoidable as of right now.
 
 However, there are a couple of suggestions to help improve this experience:
 - Make sure the `no-unused-vars` rule is enabled in
-  [ESLint](https://eslint.org/docs/rules/no-unused-vars) and any imported plugin
-  are actually being loaded.
+  [ESLint](https://eslint.org/docs/latest/rules/no-unused-vars) and any
+  imported plugin are actually being loaded.
 - Use a module such as [depcheck](https://www.npmjs.com/package/depcheck) or
   [npm-check](https://www.npmjs.com/package/npm-check) to verify plugin
   dependencies are being used somewhere in your project.
@@ -828,7 +828,7 @@ fastify.addHook('preHandler', async (req, reply) => {
 ## Code Completion In Vanilla JavaScript
 
 Vanilla JavaScript can use the published types to provide code completion (e.g.
-[Intellisense](https://code.visualstudio.com/docs/editor/intellisense)) by
+[Intellisense](https://code.visualstudio.com/docs/editing/intellisense)) by
 following the [TypeScript JSDoc
 Reference](https://www.typescriptlang.org/docs/handbook/jsdoc-supported-types.html).