chore(deps): migrate docusaurus to v3 (Farfetch#512)

.github/workflows/deploy-website.yml

@@ -21,7 +21,7 @@ jobs:
         with:
           dotnet-version: '6.0.x'
 
-      - run: dotnet tool install --global gsferreira.XmlDocMarkdown.Docusaurus --version 0.0.1-beta1 # using this version while the Pull Request isn't accepted here: https://github.com/ejball/XmlDocMarkdown/pull/126
+      - run: dotnet tool install --global gsferreira.XmlDocMarkdown.Docusaurus --version 0.0.1-beta2 # using this version while the Pull Request isn't accepted here: https://github.com/ejball/XmlDocMarkdown/pull/126
         shell: bash
 
       - name: .NET Publish

.github/workflows/test-deploy-website.yml

@@ -15,7 +15,7 @@ jobs:
         with:
           dotnet-version: '6.0.x'
 
-      - run: dotnet tool install --global gsferreira.XmlDocMarkdown.Docusaurus --version 0.0.1-beta1 # using this version while the Pull Request isn't accepted here: https://github.com/ejball/XmlDocMarkdown/pull/126
+      - run: dotnet tool install --global gsferreira.XmlDocMarkdown.Docusaurus --version 0.0.1-beta2 # using this version while the Pull Request isn't accepted here: https://github.com/ejball/XmlDocMarkdown/pull/126
         shell: bash
 
       - name: .NET Publish

website/docs/guides/admin/dashboard.md

@@ -10,7 +10,7 @@ KafkaFlow provides a Dashboard where you can visualize information related to yo
 
 :::caution
 It is important to note that the Dashboard runs, shows information, and manages the consumers on all application instances. This means that if you have 10 machines running your application, the Dashboard will run in every instance. **Any operation will affect the consumer in all the machines**.
-:::caution
+:::
 
 ## Adding the Dashboard
 

website/docs/guides/global-events.md

@@ -7,12 +7,13 @@ sidebar_position: 9
 In this section, we will delve into the concept of Global Events in KafkaFlow, which provides a mechanism to subscribe to various events that are triggered during the message production and consumption processes.
 
 KafkaFlow offers a range of Global Events that can be subscribed to. These events can be used to monitor and react to different stages of message handling. Below is a list of available events:
-  - [Message Produce Started Event](#message-produce-started-event)
-  - [Message Produce Completed Event](#message-produce-completed-event)
-  - [Message Produce Error Event](#message-produce-error-event)
-  - [Message Consume Started Event](#message-consume-started-event)
-  - [Message Consume Completed Event](#message-consume-completed-event)
-  - [Message Consume Error Event](#message-consume-error-event)
+
+- [Message Produce Started Event](#message-produce-started-event)
+- [Message Produce Completed Event](#message-produce-completed-event)
+- [Message Produce Error Event](#message-produce-error-event)
+- [Message Consume Started Event](#message-consume-started-event)
+- [Message Consume Completed Event](#message-consume-completed-event)
+- [Message Consume Error Event](#message-consume-error-event)
 
 ## Message Produce Started Event {#message-produce-started-event}
 

website/docs/guides/middlewares/serializer-middleware.md

@@ -24,7 +24,7 @@ Both classes can be provided as an argument through a factory method too.
 
 :::tip
 For topics that have just one message type, use the `AddSingleTypeSerializer`/`AddSingleTypeDeserializer` method.
-:::tip
+:::
 
 
 ```csharp

website/docusaurus.config.js

@@ -1,8 +1,9 @@
 // @ts-check
 // Note: type annotations allow type checking and IDEs autocompletion
 
-const lightCodeTheme = require('prism-react-renderer/themes/github');
-const darkCodeTheme = require('prism-react-renderer/themes/dracula');
+const {themes} = require('prism-react-renderer');
+const lightCodeTheme = themes.github;
+const darkCodeTheme = themes.dracula;
 
 /** @type {import('@docusaurus/types').Config} */
 const config = {
@@ -146,7 +147,7 @@ const config = {
       prism: {
         theme: lightCodeTheme,
         darkTheme: darkCodeTheme,
-        additionalLanguages: ['csharp']
+        additionalLanguages: ['csharp', 'bash', 'json']
       },
     }),
 };

website/package.json

@@ -14,17 +14,17 @@
     "write-heading-ids": "docusaurus write-heading-ids"
   },
   "dependencies": {
-    "@docusaurus/core": "^2.4.0",
-    "@docusaurus/preset-classic": "^2.4.0",
-    "@mdx-js/react": "^1.6.22",
+    "@docusaurus/core": "^3.1.0",
+    "@docusaurus/preset-classic": "^3.1.0",
+    "@mdx-js/react": "^3.0.0",
     "clsx": "^1.2.1",
-    "prism-react-renderer": "^1.3.5",
-    "react": "^17.0.2",
-    "react-dom": "^17.0.2",
-    "react-lite-youtube-embed": "^2.3.52"
+    "prism-react-renderer": "^2.3.1",
+    "react": "^18.2.0",
+    "react-dom": "^18.2.0",
+    "react-lite-youtube-embed": "^2.4.0"
   },
   "devDependencies": {
-    "@docusaurus/module-type-aliases": "^2.2.0"
+    "@docusaurus/module-type-aliases": "^3.1.0"
   },
   "browserslist": {
     "production": [
@@ -39,6 +39,6 @@
     ]
   },
   "engines": {
-    "node": ">=16.14"
+    "node": ">=18.0"
   }
 }

website/versioned_docs/version-2.x/guides/admin/dashboard.md

@@ -10,7 +10,7 @@ KafkaFlow provides a Dashboard where you can visualize information related to yo
 
 :::caution
 It is important to note that the Dashboard runs, shows information, and manages the consumers on all application instances. This means that if you have 10 machines running your application, the Dashboard will run in every instance. **Any operation will affect the consumer in all the machines**.
-:::caution
+:::
 
 ## Adding the Dashboard
 

website/versioned_docs/version-2.x/guides/global-events.md

@@ -7,12 +7,13 @@ sidebar_position: 9
 In this section, we will delve into the concept of Global Events in KafkaFlow, which provides a mechanism to subscribe to various events that are triggered during the message production and consumption processes. 
 
 KafkaFlow offers a range of Global Events that can be subscribed to. These events can be used to monitor and react to different stages of message handling. Below is a list of available events:
-  - [Message Produce Started Event](#message-produce-started-event)
-  - [Message Produce Completed Event](#message-produce-completed-event)
-  - [Message Produce Error Event](#message-produce-error-event)
-  - [Message Consume Started Event](#message-consume-started-event)
-  - [Message Consume Completed Event](#message-consume-completed-event)
-  - [Message Consume Error Event](#message-consume-error-event)
+
+- [Message Produce Started Event](#message-produce-started-event)
+- [Message Produce Completed Event](#message-produce-completed-event)
+- [Message Produce Error Event](#message-produce-error-event)
+- [Message Consume Started Event](#message-consume-started-event)
+- [Message Consume Completed Event](#message-consume-completed-event)
+- [Message Consume Error Event](#message-consume-error-event)
 
 ## Message Produce Started Event {#message-produce-started-event}
 
@@ -84,7 +85,7 @@ The Message Consume Completed Event signals the successful completion of message
 
 :::info
 Please note that the current event is not compatible with Batch Consume in the current version (v2). However, this limitation is expected to be addressed in future releases (v3+).
-:::info
+:::
 
 ```csharp
 services.AddKafka(

website/versioned_docs/version-2.x/guides/middlewares/serializer-middleware.md

@@ -30,7 +30,7 @@ Both classes can be provided as an argument through a factory method too.
 
 :::tip
 For topics that have just one message type, use the `AddSingleTypeSerializer` method.
-:::tip
+:::
 
 
 ```csharp