From cacff32ae7ba027bfc37eb45f2e885a768edfda2 Mon Sep 17 00:00:00 2001 From: Frazer Smith Date: Sat, 13 Jan 2024 15:38:07 +0000 Subject: [PATCH] docs(readme): replace `fastify.io` links with `fastify.dev` (#195) Signed-off-by: Frazer Smith --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 400ce24..facf333 100644 --- a/README.md +++ b/README.md @@ -68,7 +68,7 @@ async function subsystem (fastify, opts) { ### Hooks and middleware __Every registered middleware will be run during the `onRequest` hook phase__, so the registration order is important. -Take a look at the [Lifecycle](https://www.fastify.io/docs/latest/Reference/Lifecycle/) documentation page to understand better how every request is executed. +Take a look at the [Lifecycle](https://www.fastify.dev/docs/latest/Reference/Lifecycle/) documentation page to understand better how every request is executed. ```js const fastify = require('fastify')() @@ -106,7 +106,7 @@ It is possible to change the Fastify hook that the middleware will be attached t To change the hook, pass a `hook` option like so: -*Note you can access `req.body` from the `preParsing`, `onError`, `preSerialization` and `onSend` lifecycle steps. Take a look at the [Lifecycle](https://www.fastify.io/docs/latest/Reference/Lifecycle/) documentation page to see the order of the steps.* +*Note you can access `req.body` from the `preParsing`, `onError`, `preSerialization` and `onSend` lifecycle steps. Take a look at the [Lifecycle](https://www.fastify.dev/docs/latest/Reference/Lifecycle/) documentation page to see the order of the steps.* ```js const fastify = require('fastify')()