fastify 4.25.2 → 4.26.1

package/EXPENSE_POLICY.md

@@ -0,0 +1,105 @@
+# Expense Policy
+
+Fastify collaborators accept donations through the [Open Collective](https://opencollective.com/fastify/)
+platform and [GitHub Sponsors](https://github.com/sponsors/fastify)
+to enhance the project and support the community.
+
+This Collective is run by and for the benefit of the independent contributors to
+the Fastify open source software project.
+This Collective is not endorsed or administered by OpenJS Foundation, Inc.
+(the “OpenJS Foundation”). The OpenJS Foundation does not receive or have
+control over any funds contributed. The OpenJS Foundation does not direct or
+otherwise supervise the actions of any contributor to the Fastify project,
+and all donations made will be expended for the private benefit of or otherwise
+to reimburse individuals that do not have an employer/employee, contractor, or
+other agency relationship with the OpenJS Foundation.
+The Fastify marks used herein are used under license from the OpenJS Foundation
+for the benefit of the open source software community.
+
+The admins of the Fastify Collective are the [lead maintainers](./GOVERNANCE.md)
+of the project.
+
+This document outlines the process for requesting reimbursement or an invoice
+for expenses.
+
+## Reimbursement
+
+Reimbursement is applicable for expenses already paid, such as:
+
+- Stickers
+- Gadgets
+- Hosting
+
+**Before making any purchases**, initiate a [new discussion](https://github.com/orgs/fastify/discussions)
+in the `fastify` organization with the following information:
+
+- What is needed
+- Why it is needed
+- Cost
+- Deadline
+
+Once the discussion is approved by a lead maintainer and with no unresolved objections,
+the purchase can proceed, and an expense can be submitted to the [Open Collective][submit].
+This process takes a minimum of 3 business days from the request to allow time for
+discussion approval.
+
+The discussion helps prevent misunderstandings and ensures the expense is not rejected.
+As a project under the OpenJS Foundation, Fastify benefits from the Foundation's
+resources, including servers, domains, and [travel funds](https://github.com/openjs-foundation/community-fund/tree/main/programs/travel-fund).
+
+Always seek approval first.
+
+## Invoice
+
+Invoices are for services provided to the Fastify project, such as PR reviews,
+documentation, etc.
+A VAT number is not required to submit an invoice.
+Refer to the [Open Collective documentation][openc_docs] for details.
+
+### Adding a bounty to an issue
+
+Issues become eligible for a bounty when the core team adds the `bounty` label,
+with the amount determined by the core team based on `estimated hours * rate`
+(suggested $50 per hour).
+
+> Example: If the estimated time to fix the issue is 2 hours,
+> the bounty will be $100.
+
+To add a bounty:
+
+- Apply the `bounty` label to the issue
+- Comment on the issue with the bounty amount
+- Edit the first comment of the issue using this template:
+
+```
+## 💰 Bounty
+
+This issue has a bounty of [$AMOUNT](LINK TO THE BOUNTY COMMENT).
+_Read more about [the bounty program](./EXPENSE_POLICY.md)_
+```
+
+For discussions on bounties or determining amounts, open a [new discussion](https://github.com/orgs/fastify/discussions/new?category=bounty).
+
+### Outstanding contributions
+
+The lead team can decide to add a bounty to an issue or PR not labeled as `bounty`
+if the contribution is outstanding.
+
+### Claiming a bounty
+
+To claim a bounty:
+
+- Submit a PR that fixes the issue
+- If multiple submissions exist, a core member will choose the best solution
+- Once merged, the PR author can claim the bounty by:
+  - Submitting an expense to the [Open Collective][submit] with the PR link
+  - Adding a comment on the PR with a link to their Open Collective expense to
+    ensure the claimant is the issue resolver
+- The expense will be validated by a lead maintainer and then the payment will be
+  processed by Open Collective
+
+If the Open Collective budget is insufficient, the expense will be rejected.  
+Unclaimed bounties are available for other issues.
+
+[submit]: https://opencollective.com/fastify/expenses/new
+[openc_docs]: https://docs.oscollective.org/how-it-works/basics/invoice-and-reimbursement-examples

package/GOVERNANCE.md

@@ -1,105 +1,4 @@
 # Fastify Project Governance
 
-<!-- TOC -->
-
-* [Lead Maintainers](#lead-maintainers)
-* [Collaborators](#collaborators)
-  * [Collaborator activities](#collaborator-activities)
-* [Great Contributors](#great-contributors)
-* [Collaborator nominations](#collaborator-maintainers-nominations)
-* [Lead Maintainers nominations](#lead-maintainers-nominations)
-* [Consensus seeking process](#consensus-seeking-process)
-
-<!-- /TOC -->
-
-## Lead Maintainers
-
-Fastify Lead Maintainers are the organization owners.
-They are the only members of the `@fastify/leads` team. The Lead
-Maintainers are the curator of the Fastify project and their key responsibility
-is to issue releases of Fastify and its dependencies.
-
-## Collaborators
-
-Fastify Collaborators maintain the projects of the Fastify organization.
-
-They are split into the following teams:
-
-|  Team | Responsibility  |  Repository |
-|---|---|---|
-| `@fastify/leads` | Fastify Lead Maintainers | GitHub organization owners |
-| `@fastify/core`   |  Fastify Core development  |  `fastify`, `fast-json-stringify`, `light-my-request`, `fastify-plugin`, `middie` |
-| `@fastify/plugins`   |  Build, maintain and release Fastify plugins  |  All plugins repositories |
-| `@fastify/benchmarks`   |  Build and maintain our benchmarks suite  |  `benchmarks` |
-| `@fastify/docs-chinese`   |  Translate the Fastify documentation in Chinese  |  `docs-chinese` |
-
-Every member of the org is also part of `@fastify/fastify`.
-
-Collaborators have:
-
-* Commit access to the projects repository of the team they belong
- * Grant to release new versions of the project
-
-Both Collaborators and non-Collaborators may propose changes to the source code
-of the projects of the organization. The mechanism to propose such a change is a
-GitHub pull request. Collaborators review and merge (_land_) pull requests
-following the [CONTRIBUTING](CONTRIBUTING.md#rules) guidelines.
-
-### Collaborator activities
-
-* Helping users and novice contributors
-* Contributing code and documentation changes that improve the project
-* Reviewing and commenting on issues and pull requests
-* Participation in working groups
-* Merging pull requests
-* Release plugins
-
-The Lead Maintainers can remove inactive Collaborators or provide them with
-_Past Collaborators_ status. Past Collaborators may request that the Lead
-Maintainers restore them to active status.
-
-
-## Great Contributors
-
-Great contributors on a specific area in the Fastify ecosystem will be invited
-to join this group by Lead Maintainers. This group has the same permissions of a
-contributor.
-
-## Collaborator nominations
-
-Individuals making significant and valuable contributions to the project may be
-a candidate to join the Fastify organization.
-
-A Collaborator needs to open a private team discussion on GitHub and list the
-candidates they want to sponsor with a link to the user's contributions. For
-example:
-
-* Activities in the Fastify organization
-  `[USERNAME](https://github.com/search?q=author:USERNAME+org:fastify)`
-
-Otherwise, a Contributor may self-apply if they believe they meet the above
-criteria by reaching out to a Lead Maintainer privately with the links to their
-valuable contributions. The Lead Maintainers will reply to the Contributor and
-will decide if candidate it to be made a collaborator.
-
-The consensus to grant a new candidate Collaborator status is reached when:
-
-- at least one of the Lead Maintainers approve
-- at least two of the Team Members approve
-
-After these conditions are satisfied, the [onboarding
-process](CONTRIBUTING.md#onboarding-collaborators) may start.
-
-
-## Lead Maintainers nominations
-
-A Team Member may be promoted to a Lead Maintainers only through nomination by a
-Lead maintainer and with agreement from the rest of Lead Maintainers.
-
-
-## Consensus seeking process
-
-The Fastify organization follows a [Consensus Seeking][] decision-making model.
-
-[Consensus Seeking]:
-    https://en.wikipedia.org/wiki/Consensus-seeking_decision-making
+Please see Fastify's [organization-wide governance
+](https://github.com/fastify/.github/blob/main/GOVERNANCE.md) document.

package/LICENSE

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

package/README.md

@@ -29,6 +29,7 @@ downloads](https://img.shields.io/npm/dm/fastify.svg?style=flat)](https://www.np
 Disclosure](https://img.shields.io/badge/Security-Responsible%20Disclosure-yellow.svg)](https://github.com/fastify/fastify/blob/main/SECURITY.md)
 [![Discord](https://img.shields.io/discord/725613461949906985)](https://discord.gg/fastify)
 [![Contribute with Gitpod](https://img.shields.io/badge/Contribute%20with-Gitpod-908a85?logo=gitpod&color=blue)](https://gitpod.io/#https://github.com/fastify/fastify)
+![Open Collective backers and sponsors](https://img.shields.io/opencollective/all/fastify)
 
 </div>
 
@@ -171,15 +172,6 @@ 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>.
 
-
-### Fastify v1.x and v2.x
-
-Code for Fastify's **v1.x** is in [**`branch
-1.x`**](https://github.com/fastify/fastify/tree/1.x), so all Fastify 1.x related
-changes should be based on **`branch 1.x`**. In a similar way, all Fastify
-**v2.x** related changes should be based on [**`branch
-2.x`**](https://github.com/fastify/fastify/tree/2.x).
-
 > ## Note
 > `.listen` binds to the local host, `localhost`, interface by default
 > (`127.0.0.1` or `::1`, depending on the operating system configuration). If
@@ -275,6 +267,12 @@ application, you should __always__ benchmark if performance matters to you.
 Please visit [Fastify help](https://github.com/fastify/help) to view prior
 support issues and to ask new support questions.
 
+## Contributing
+
+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.
+
 ## Team
 
 _Fastify_ is the result of the work of a great community. Team members are
@@ -383,6 +381,12 @@ We are a [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/).
 
+## Sponsors
+
+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
 
 This project is kindly sponsored by:

package/SECURITY.md

@@ -1,159 +1,4 @@
 # Security Policy
 
-This document describes the management of vulnerabilities for the Fastify
-project and its official plugins.
-
-## Reporting vulnerabilities
-
-Individuals who find potential vulnerabilities in Fastify are invited to
-complete a vulnerability report via the dedicated HackerOne page:
-[https://hackerone.com/fastify](https://hackerone.com/fastify).
-
-### Strict measures when reporting vulnerabilities
-
-It is of the utmost importance that you read carefully and follow these
-guidelines to ensure the ecosystem as a whole isn't disrupted due to improperly
-reported vulnerabilities:
-
-* Avoid creating new "informative" reports on HackerOne. Only create new
-  HackerOne reports on a vulnerability if you are absolutely sure this should be
-  tagged as an actual vulnerability. Third-party vendors and individuals are
-  tracking any new vulnerabilities reported in HackerOne and will flag them as
-  such for their customers (think about snyk, npm audit, ...).
-* HackerOne reports should never be created and triaged by the same person. If
-  you are creating a HackerOne report for a vulnerability that you found, or on
-  behalf of someone else, there should always be a 2nd Security Team member who
-  triages it. If in doubt, invite more Fastify Collaborators to help triage the
-  validity of the report. In any case, the report should follow the same process
-  as outlined below of inviting the maintainers to review and accept the
-  vulnerability.
-* ***Do not*** attempt to show CI/CD vulnerabilities by creating new pull
-  requests to any of the Fastify organization's repositories. Doing so will
-  result in a [content report][cr] to GitHub as an unsolicited exploit.
-  The proper way to provide such reports is by creating a new repository,
-  configured in the same manner as the repository you would like to submit
-  a report about, and with a pull request to your own repository showing
-  the proof of concept.
-
-[cr]: https://docs.github.com/en/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam#reporting-an-issue-or-pull-request
-
-### Vulnerabilities found outside this process
-
-⚠ The Fastify project does not support any reporting outside the HackerOne
-process.
-
-## Handling vulnerability reports
-
-When a potential vulnerability is reported, the following actions are taken:
-
-### Triage
-
-**Delay:** 4 business days
-
-Within 4 business days, a member of the security team provides a first answer to
-the individual who submitted the potential vulnerability. The possible responses
-can be:
-
-* Acceptance: what was reported is considered as a new vulnerability
-* Rejection: what was reported is not considered as a new vulnerability
-* Need more information: the security team needs more information in order to
-  evaluate what was reported.
-
-Triaging should include updating issue fields:
-* Asset - set/create the module affected by the report
-* Severity - TBD, currently left empty
-
-Reference: [HackerOne: Submitting
-Reports](https://docs.hackerone.com/hackers/submitting-reports.html)
-
-### Correction follow-up
-
-**Delay:** 90 days
-
-When a vulnerability is confirmed, a member of the security team volunteers to
-follow up on this report.
-
-With the help of the individual who reported the vulnerability, they contact the
-maintainers of the vulnerable package to make them aware of the vulnerability.
-The maintainers can be invited as participants to the reported issue.
-
-With the package maintainer, they define a release date for the publication of
-the vulnerability. Ideally, this release date should not happen before the
-package has been patched.
-
-The report's vulnerable versions upper limit should be set to:
-* `*` if there is no fixed version available by the time of publishing the
-  report.
-* the last vulnerable version. For example: `<=1.2.3` if a fix exists in `1.2.4`
-
-### Publication
-
-**Delay:** 90 days
-
-Within 90 days after the triage date, the vulnerability must be made public.
-
-**Severity**: Vulnerability severity is assessed using [CVSS
-v.3](https://www.first.org/cvss/user-guide). More information can be found on
-[HackerOne documentation](https://docs.hackerone.com/hackers/severity.html)
-
-If the package maintainer is actively developing a patch, an additional delay
-can be added with the approval of the security team and the individual who
-reported the vulnerability.
-
-At this point, a CVE should be requested through the HackerOne platform through
-the UI, which should include the Report ID and a summary.
-
-Within HackerOne, this is handled through a "public disclosure request".
-
-Reference: [HackerOne:
-Disclosure](https://docs.hackerone.com/hackers/disclosure.html)
-
-## The Fastify Security team
-
-The core team is responsible for the management of HackerOne program and this
-policy and process.
-
-Members of this team are expected to keep all information that they have
-privileged access to by being on the team completely private to the team. This
-includes agreeing to not notify anyone outside the team of issues that have not
-yet been disclosed publicly, including the existence of issues, expectations of
-upcoming releases, and patching of any issues other than in the process of their
-work as a member of the Fastify Core team.
-
-### Members
-
-* [__Matteo Collina__](https://github.com/mcollina),
-  <https://twitter.com/matteocollina>, <https://www.npmjs.com/~matteo.collina>
-* [__Tomas Della Vedova__](https://github.com/delvedor),
-  <https://twitter.com/delvedor>, <https://www.npmjs.com/~delvedor>
-* [__Vincent Le Goff__](https://github.com/zekth)
-* [__KaKa Ng__](https://github.com/climba03003)
-* [__James Sumners__](https://github.com/jsumners),
-  <https://twitter.com/jsumners79>, <https://www.npmjs.com/~jsumners>
-
-## OpenSSF CII Best Practices
-
-[![CII Best Practices](https://bestpractices.coreinfrastructure.org/projects/7585/badge)](https://bestpractices.coreinfrastructure.org/projects/7585)
-
-There are three “tiers”: passing, silver, and gold.
-
-### Passing
-We meet 100% of the “passing” criteria.
-
-### Silver
-We meet 87% of the “silver” criteria. The gaps are as follows:
-  - we do not have a DCO or a CLA process for contributions.
-  - we do not currently document
-    “what the user can and cannot expect in terms of security” for our project.
-  - we do not currently document ”the architecture (aka high-level design)”
-    for our project.
-
-### Gold
-We meet 70% of the “gold” criteria. The gaps are as follows:
-  - we do not yet have the “silver” badge; see all the gaps above.
-  - We do not include a copyright or license statement in each source file.
-    Efforts are underway to change this archaic practice into a
-    suggestion instead of a hard requirement.
-  - There are a few unanswered questions around cryptography that are
-    waiting for clarification.
-
+Please see Fastify's [organization-wide security policy
+](https://github.com/fastify/.github/blob/main/SECURITY.md).

package/SPONSORS.md

@@ -0,0 +1,20 @@
+# Sponsors
+
+All active sponsors of Fastify are listed here, in order of contribution!
+Our sponsors are the reason why we can work on some issues or features
+that otherwise would be impossible to do.
+
+If you want to become a sponsor, please check out our [Open Collective page](https://opencollective.com/fastify)
+or [GitHub Sponsors](https://github.com/sponsors/fastify)!
+
+## Tier 4
+
+_Be the first!_
+
+## Tier 3
+
+_Be the first!_
+
+## Tier 2
+
+_Be the first!_

package/build/build-validation.js

@@ -41,7 +41,8 @@ const defaultInitOptions = {
   requestIdHeader: 'request-id',
   requestIdLogLabel: 'reqId',
   http2SessionTimeout: 72000, // 72 seconds
-  exposeHeadRoutes: true
+  exposeHeadRoutes: true,
+  useSemicolonDelimiter: true
 }
 
 const schema = {
@@ -101,6 +102,7 @@ const schema = {
     requestIdLogLabel: { type: 'string', default: defaultInitOptions.requestIdLogLabel },
     http2SessionTimeout: { type: 'integer', default: defaultInitOptions.http2SessionTimeout },
     exposeHeadRoutes: { type: 'boolean', default: defaultInitOptions.exposeHeadRoutes },
+    useSemicolonDelimiter: { type: 'boolean', default: defaultInitOptions.useSemicolonDelimiter },
     // deprecated style of passing the versioning constraint
     versioning: {
       type: 'object',

package/docs/Guides/Ecosystem.md

@@ -13,7 +13,7 @@ section.
 - [`@fastify/accepts-serializer`](https://github.com/fastify/fastify-accepts-serializer)
   to serialize to output according to the `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
+  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
@@ -53,6 +53,8 @@ section.
   configuration.
 - [`@fastify/etag`](https://github.com/fastify/fastify-etag) Automatically
   generate ETags for HTTP responses.
+- [`@fastify/express`](https://github.com/fastify/fastify-express) Express
+  compatibility layer for Fastify.
 - [`@fastify/flash`](https://github.com/fastify/fastify-flash) Set and get flash
   messages using the session.
 - [`@fastify/formbody`](https://github.com/fastify/fastify-formbody) Plugin to
@@ -69,6 +71,8 @@ section.
   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/kafka`](https://github.com/fastify/fastify-kafka) Plugin to interact
+  with Apache Kafka.
 - [`@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
@@ -78,6 +82,8 @@ section.
   connection pool across every part of your server.
 - [`@fastify/multipart`](https://github.com/fastify/fastify-multipart) Multipart
   support for Fastify.
+- [`@fastify/mysql`](https://github.com/fastify/fastify-mysql) Fastify MySQL
+  connection plugin.
 - [`@fastify/nextjs`](https://github.com/fastify/fastify-nextjs) React
   server-side rendering support for Fastify with
   [Next](https://github.com/zeit/next.js/).
@@ -85,6 +91,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/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
   PostgreSQL connection plugin, with this you can share the same PostgreSQL
   connection pool in every part of your server.
@@ -104,6 +112,8 @@ section.
   A simple plugin that enables response validation for Fastify.
 - [`@fastify/routes`](https://github.com/fastify/fastify-routes) Plugin that
   provides a `Map` of routes.
+- [`@fastify/routes-stats`](https://github.com/fastify/fastify-routes-stats)
+  Provide stats for routes using `node:perf_hooks`.
 - [`@fastify/schedule`](https://github.com/fastify/fastify-schedule) Plugin for
   scheduling periodic jobs, based on
   [toad-scheduler](https://github.com/kibertoad/toad-scheduler).
@@ -121,15 +131,17 @@ section.
 - [`@fastify/swagger`](https://github.com/fastify/fastify-swagger) Plugin for
   serving Swagger/OpenAPI documentation for Fastify, supporting dynamic
   generation.
+- [`@fastify/swagger-ui`](https://github.com/fastify/fastify-swagger-ui) Plugin
+  for serving Swagger UI.
 - [`@fastify/throttle`](https://github.com/fastify/fastify-throttle) Plugin for
   throttling the download speed of a request.
 - [`@fastify/type-provider-json-schema-to-ts`](https://github.com/fastify/fastify-type-provider-json-schema-to-ts)
   Fastify
-  [type provider](https://www.fastify.dev/docs/latest/Reference/Type-Providers/)
+  [type provider](https://fastify.dev/docs/latest/Reference/Type-Providers/)
   for [json-schema-to-ts](https://github.com/ThomasAribart/json-schema-to-ts).
 - [`@fastify/type-provider-typebox`](https://github.com/fastify/fastify-type-provider-typebox)
   Fastify
-  [type provider](https://www.fastify.dev/docs/latest/Reference/Type-Providers/)
+  [type provider](https://fastify.dev/docs/latest/Reference/Type-Providers/)
   for [Typebox](https://github.com/sinclairzx81/typebox).
 - [`@fastify/under-pressure`](https://github.com/fastify/under-pressure) Measure
   process load with automatic handling of _"Service Unavailable"_ plugin for
@@ -142,6 +154,8 @@ section.
   [Vite](https://vitejs.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
+  for Zipkin distributed tracing system.
 
 #### [Community](#community)
 
@@ -206,9 +220,6 @@ section.
 - [`apitally`](https://github.com/apitally/nodejs-client) Fastify plugin to
   integrate with [Apitally](https://apitally.io), a simple API monitoring &
   API key management solution.
-- [`apollo-server-fastify`](https://github.com/apollographql/apollo-server/tree/master/packages/apollo-server-fastify)
-  Run an [Apollo Server](https://github.com/apollographql/apollo-server) to
-  serve GraphQL with Fastify.
 - [`arecibo`](https://github.com/nucleode/arecibo) Fastify ping responder for
   Kubernetes Liveness and Readiness Probes.
 - [`cls-rtracer`](https://github.com/puzpuzpuz/cls-rtracer) Fastify middleware
@@ -375,6 +386,8 @@ section.
   Providers.
 - [`fastify-guard`](https://github.com/hsynlms/fastify-guard) A Fastify plugin
   that protects endpoints by checking authenticated user roles and/or scopes.
+- [`fastify-hana`](https://github.com/yoav0gal/fastify-hana) connects your
+  application to [`SAP-HANA`](https://help.sap.com/docs/SAP_HANA_CLIENT).
 - [`fastify-hashids`](https://github.com/andersonjoseph/fastify-hashids) A Fastify
   plugin to encode/decode IDs using [hashids](https://github.com/niieani/hashids.js).
 - [`fastify-hasura`](https://github.com/ManUtopiK/fastify-hasura) A Fastify
@@ -384,6 +397,11 @@ section.
 - [`fastify-hemera`](https://github.com/hemerajs/fastify-hemera) Fastify Hemera
   plugin, for writing reliable & fault-tolerant microservices with
   [nats.io](https://nats.io/).
+- [`fastify-hl7`](https://github.com/Bugs5382/fastify-hl7) A Fastify Plugin to
+  create a server, build, and send HL7 formatted Hl7 messages. Using
+  [node-hl7-client](https://github.com/Bugs5382/node-hl7-client) and
+  [node-hl7-server](https://github.com/Bugs5382/node-hl7-server) as the
+  underlining technology to do this.
 - [`fastify-http-client`](https://github.com/kenuyx/fastify-http-client) Plugin
   to send HTTP(s) requests. Built upon [urllib](https://github.com/node-modules/urllib).
 - [`fastify-http-context`](https://github.com/thorough-developer/fastify-http-context)
@@ -537,7 +555,7 @@ middlewares into Fastify plugins
   [qs](https://github.com/ljharb/qs).
 - [`fastify-rabbitmq`](https://github.com/Bugs5382/fastify-rabbitmq) Fastify
   RabbitMQ plugin that uses
-  [node-amqp-connection-manager](https://github.com/jwalton/node-amqp-connection-manager)
+  [node-rabbitmq-client](https://github.com/cody-greene/node-rabbitmq-client)
   plugin as a wrapper.
 - [`fastify-racing`](https://github.com/metcoder95/fastify-racing) Fastify's
   plugin that adds support to handle an aborted request asynchronous.
@@ -600,6 +618,8 @@ middlewares into Fastify plugins
   HTTP part of the request.
 - [`fastify-sqlite`](https://github.com/Eomm/fastify-sqlite) connects your
   application to a sqlite3 database.
+- [`fastify-sqlite-typed`](https://github.com/yoav0gal/fastify-sqlite-typed) connects
+  your application to a SQLite database with full Typescript support.
 - [`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
@@ -625,11 +645,11 @@ middlewares into Fastify plugins
   Useful functions for Twitch Extension Backend Services (EBS).
 - [`fastify-type-provider-effect-schema`](https://github.com/daotl/fastify-type-provider-effect-schema)
   Fastify
-  [type provider](https://www.fastify.dev/docs/latest/Reference/Type-Providers/)
+  [type provider](https://fastify.dev/docs/latest/Reference/Type-Providers/)
   for [@effect/schema](https://github.com/effect-ts/schema).
 - [`fastify-type-provider-zod`](https://github.com/turkerdev/fastify-type-provider-zod)
   Fastify
-  [type provider](https://www.fastify.dev/docs/latest/Reference/Type-Providers/)
+  [type provider](https://fastify.dev/docs/latest/Reference/Type-Providers/)
   for [zod](https://github.com/colinhacks/zod).
 - [`fastify-typeorm-plugin`](https://github.com/inthepocket/fastify-typeorm-plugin)
   Fastify plugin to work with TypeORM.

package/docs/Guides/Getting-Started.md

@@ -55,6 +55,14 @@ fastify.listen({ port: 3000 }, function (err, address) {
 })
 ```
 
+> If you are using ECMAScript Modules (ESM) in your project, be sure to
+> include "type": "module" in your package.json.
+>```js
+>{
+>  "type": "module"
+>}
+>```
+
 Do you prefer to use `async/await`? Fastify supports it out-of-the-box.
 
 ```js
@@ -172,13 +180,14 @@ fastify.listen({ port: 3000 }, function (err, address) {
 })
 ```
 
+
 ```js
 // our-first-route.js
 
 /**
  * Encapsulates the routes
  * @param {FastifyInstance} fastify  Encapsulated Fastify Instance
- * @param {Object} options plugin options, refer to https://www.fastify.dev/docs/latest/Reference/Plugins/#plugin-options
+ * @param {Object} options plugin options, refer to https://fastify.dev/docs/latest/Reference/Plugins/#plugin-options
  */
 async function routes (fastify, options) {
   fastify.get('/', async (request, reply) => {
@@ -186,6 +195,10 @@ async function routes (fastify, options) {
   })
 }
 
+//ESM
+export default routes;
+
+// CommonJs
 module.exports = routes
 ```
 In this example, we used the `register` API, which is the core of the Fastify
@@ -293,7 +306,7 @@ const fastifyPlugin = require('fastify-plugin')
 /**
  * Connects to a MongoDB database
  * @param {FastifyInstance} fastify Encapsulated Fastify Instance
- * @param {Object} options plugin options, refer to https://www.fastify.dev/docs/latest/Reference/Plugins/#plugin-options
+ * @param {Object} options plugin options, refer to https://fastify.dev/docs/latest/Reference/Plugins/#plugin-options
  */
 async function dbConnector (fastify, options) {
   fastify.register(require('@fastify/mongodb'), {
@@ -312,7 +325,7 @@ module.exports = fastifyPlugin(dbConnector)
 /**
  * A plugin that provide encapsulated routes
  * @param {FastifyInstance} fastify encapsulated fastify instance
- * @param {Object} options plugin options, refer to https://www.fastify.dev/docs/latest/Reference/Plugins/#plugin-options
+ * @param {Object} options plugin options, refer to https://fastify.dev/docs/latest/Reference/Plugins/#plugin-options
  */
 async function routes (fastify, options) {
   const collection = fastify.mongo.db.collection('test_collection')