Docusaurus v3 (#272)

* Upgrade to Docusaurus v3 and React v18

* Escape curly braces in MDX for v5 docs

This needs to be fixed in source.

MDX v2 allows expressions inside curly braces
outside of codefences

* Escape curly braces in MDX for v4 docs

Manually fixed as v4 docs are not updated anymore

MDX v2 allows expressions inside curly braces
outside of codefences

* Remove unused @svgr/webpack dependency

* Replace classnames dependency with clsx

clsx is faster, has same syntax and is also used in docusaurus

* Fix summary in details-elements

Summary got wrapped in the contents paragraph-element
MDX v2 doesn't produce blocks for single line ocntent. We fix this by
adding a blank line after summary, or just wrap text in ex. div-element

* Upgrade to 3.0.0-beta.0

* Remove legacy prefix from versioned sidebars

Support removed in 3.0.0-beta.0. Fix was documented in build error

* Replace deprecated caution admonitions

`:::caution` is deprecated in v3. `:::warning` has been updated with
the same styling, so only real change is default title.

* Upgrade to 3.0.0-rc.0

* Make config prism-react-renderer v2 compatible

Remove xml as additional language

* Cleanup dependencies

Removes unused url-loader and file-loader.
Adds prism-react-renderer as direct deps to support
strict package manages without hoisting.

* Bump Docusaurus to 3.0 GA

Author: fflaten

docs/assertions/assertions.mdx

@@ -232,7 +232,7 @@ Set-Content -Path TestDrive:\file.txt -Value 'I am a file.'
 ```
 :::
 
-:::caution
+:::warning
 Make sure the input is either a quoted string or an Item object. Otherwise PowerShell will try to invoke the
 path, likely throwing an error `Cannot run a document in the middle of a pipeline`.
 
@@ -352,7 +352,7 @@ so the following assertion will pass:
 Wildcard-characters `?*[]` can be escaped using backtick, ex `` `*``.
 :::
 
-:::caution
+:::warning
 The input object must be a ScriptBlock, otherwise it is processed outside of the assertion.
 
 ```powershell

docs/assertions/custom-assertions.mdx

@@ -28,7 +28,7 @@ If a problem occurs in your function, ex. it was called with invalid parameters,
 `Should` accepts the value to assert by pipeline but passes it to the assertion using `-ActualValue $ActualValue`. This means `ValueFromPipelineByPropertyName` is not available inside your function, but you can write your own logic to work with complex types provided to `ActualValue`.
 :::
 
-:::caution Using advanced functions as assertions
+:::warning Using advanced functions as assertions
 Advanced functions, typically enabled by using `[CmdletBinding()]` or `[Parameter()]`, disallows arguments by default. In this scenario, make sure to accept all mandatory parameters in your param-block to avoid errors even if you don't use them. They are `ActualValue`, `Negate` and `CallerSessionState`.
 :::
 

docs/commands/Assert-MockCalled.mdx

@@ -42,7 +42,7 @@ Assert-MockCalled [-CommandName] <String> [[-Times] <Int32>] [-ParameterFilter <
 
 ## DESCRIPTION
 
-{{ Fill in the Description }}
+\{\{ Fill in the Description \}\}
 
 ## EXAMPLES
 
@@ -52,13 +52,13 @@ Assert-MockCalled [-CommandName] <String> [[-Times] <Int32>] [-ParameterFilter <
 PS C:\> {{ Add example code here }}
 ```
 
-{{ Add example description here }}
+\{\{ Add example description here \}\}
 
 ## PARAMETERS
 
 ### -CommandName
 
-{{ Fill CommandName Description }}
+\{\{ Fill CommandName Description \}\}
 
 ```yaml
 Type: String
@@ -74,7 +74,7 @@ Accept wildcard characters: False
 
 ### -Times
 
-{{ Fill Times Description }}
+\{\{ Fill Times Description \}\}
 
 ```yaml
 Type: Int32
@@ -90,7 +90,7 @@ Accept wildcard characters: False
 
 ### -ParameterFilter
 
-{{ Fill ParameterFilter Description }}
+\{\{ Fill ParameterFilter Description \}\}
 
 ```yaml
 Type: ScriptBlock
@@ -106,7 +106,7 @@ Accept wildcard characters: False
 
 ### -ExclusiveFilter
 
-{{ Fill ExclusiveFilter Description }}
+\{\{ Fill ExclusiveFilter Description \}\}
 
 ```yaml
 Type: ScriptBlock
@@ -122,7 +122,7 @@ Accept wildcard characters: False
 
 ### -ModuleName
 
-{{ Fill ModuleName Description }}
+\{\{ Fill ModuleName Description \}\}
 
 ```yaml
 Type: String
@@ -138,7 +138,7 @@ Accept wildcard characters: False
 
 ### -Scope
 
-{{ Fill Scope Description }}
+\{\{ Fill Scope Description \}\}
 
 ```yaml
 Type: String
@@ -154,7 +154,7 @@ Accept wildcard characters: False
 
 ### -Exactly
 
-{{ Fill Exactly Description }}
+\{\{ Fill Exactly Description \}\}
 
 ```yaml
 Type: SwitchParameter

docs/commands/Assert-VerifiableMock.mdx

@@ -31,7 +31,7 @@ Assert-VerifiableMock [<CommonParameters>]
 
 ## DESCRIPTION
 
-{{ Fill in the Description }}
+\{\{ Fill in the Description \}\}
 
 ## EXAMPLES
 
@@ -41,7 +41,7 @@ Assert-VerifiableMock [<CommonParameters>]
 PS C:\> {{ Add example code here }}
 ```
 
-{{ Add example description here }}
+\{\{ Add example description here \}\}
 
 ## PARAMETERS
 

docs/usage/_GetEmoji.mdx

@@ -1,22 +1,24 @@
 <details>
-<summary>Required code for samples (PowerShell 6 or later)</summary>
-To run the sample below, place this file in the same folder as Get-Emoji.Tests.ps1.
+    <summary>Required code for samples (PowerShell 6 or later)</summary>
+    <div>
+        To run the sample below, place this file in the same folder as Get-Emoji.Tests.ps1.
 
-```powershell title="Get-Emoji.ps1"
-$emojis = @(
-    @{ Name = 'apple'; Symbol = '🍎'; Kind = 'Fruit' }
-    @{ Name = 'beaming face with smiling eyes'; Symbol = '😁'; Kind = 'Face' }
-    @{ Name = 'cactus'; Symbol = '🌵'; Kind = 'Plant' }
-    @{ Name = 'giraffe'; Symbol = '🦒'; Kind = 'Animal' }
-    @{ Name = 'pencil'; Symbol = '✏️'; Kind = 'Item' }
-    @{ Name = 'penguin'; Symbol = '🐧'; Kind = 'Animal' }
-    @{ Name = 'pensive'; Symbol = '😔'; Kind = 'Face' }
-    @{ Name = 'slightly smiling face'; Symbol = '🙂'; Kind = 'Face' }
-    @{ Name = 'smiling face with smiling eyes'; Symbol = '😊'; Kind = 'Face' }
-) | ForEach-Object { [PSCustomObject]$_ }
+        ```powershell title="Get-Emoji.ps1"
+        $emojis = @(
+            @{ Name = 'apple'; Symbol = '🍎'; Kind = 'Fruit' }
+            @{ Name = 'beaming face with smiling eyes'; Symbol = '😁'; Kind = 'Face' }
+            @{ Name = 'cactus'; Symbol = '🌵'; Kind = 'Plant' }
+            @{ Name = 'giraffe'; Symbol = '🦒'; Kind = 'Animal' }
+            @{ Name = 'pencil'; Symbol = '✏️'; Kind = 'Item' }
+            @{ Name = 'penguin'; Symbol = '🐧'; Kind = 'Animal' }
+            @{ Name = 'pensive'; Symbol = '😔'; Kind = 'Face' }
+            @{ Name = 'slightly smiling face'; Symbol = '🙂'; Kind = 'Face' }
+            @{ Name = 'smiling face with smiling eyes'; Symbol = '😊'; Kind = 'Face' }
+        ) | ForEach-Object { [PSCustomObject]$_ }
 
-function Get-Emoji ([string]$Name = '*') {
-    $emojis | Where-Object Name -like $Name | ForEach-Object Symbol
-}
-```
+        function Get-Emoji ([string]$Name = '*') {
+            $emojis | Where-Object Name -like $Name | ForEach-Object Symbol
+        }
+        ```
+    </div>
 </details>

docs/usage/_PesterDemoFunctions.mdx

@@ -1,53 +1,55 @@
 <details>
-<summary>Required code for samples (PowerShell 6 or later)</summary>
-This module is required for the Emoji and Fruit tests below. Copy and paste this in your console before running the tests.
+    <summary>Required code for samples (PowerShell 6 or later)</summary>
+    <div>
+        This module is required for the Emoji and Fruit tests below. Copy and paste this in your console before running the tests.
 
-```powershell
-Get-Module PesterDemoFunctions | Remove-Module
-New-Module PesterDemoFunctions -ScriptBlock {
-    $emojis = @(
-        @{ Name = 'apple'; Symbol = '🍎'; Kind = 'Fruit' }
-        @{ Name = 'beaming face with smiling eyes'; Symbol = '😁'; Kind = 'Face' }
-        @{ Name = 'cactus'; Symbol = '🌵'; Kind = 'Plant' }
-        @{ Name = 'giraffe'; Symbol = '🦒'; Kind = 'Animal' }
-        @{ Name = 'pencil'; Symbol = '✏️'; Kind = 'Item' }
-        @{ Name = 'penguin'; Symbol = '🐧'; Kind = 'Animal' }
-        @{ Name = 'pensive'; Symbol = '😔'; Kind = 'Face' }
-        @{ Name = 'slightly smiling face'; Symbol = '🙂'; Kind = 'Face' }
-        @{ Name = 'smiling face with smiling eyes'; Symbol = '😊'; Kind = 'Face' }
-    ) | ForEach-Object { [PSCustomObject]$_ }
+        ```powershell
+        Get-Module PesterDemoFunctions | Remove-Module
+        New-Module PesterDemoFunctions -ScriptBlock {
+            $emojis = @(
+                @{ Name = 'apple'; Symbol = '🍎'; Kind = 'Fruit' }
+                @{ Name = 'beaming face with smiling eyes'; Symbol = '😁'; Kind = 'Face' }
+                @{ Name = 'cactus'; Symbol = '🌵'; Kind = 'Plant' }
+                @{ Name = 'giraffe'; Symbol = '🦒'; Kind = 'Animal' }
+                @{ Name = 'pencil'; Symbol = '✏️'; Kind = 'Item' }
+                @{ Name = 'penguin'; Symbol = '🐧'; Kind = 'Animal' }
+                @{ Name = 'pensive'; Symbol = '😔'; Kind = 'Face' }
+                @{ Name = 'slightly smiling face'; Symbol = '🙂'; Kind = 'Face' }
+                @{ Name = 'smiling face with smiling eyes'; Symbol = '😊'; Kind = 'Face' }
+            ) | ForEach-Object { [PSCustomObject]$_ }
 
-    function Get-Emoji ([string]$Name = '*') {
-        $script:emojis | Where-Object Name -like $Name | ForEach-Object Symbol
-    }
+            function Get-Emoji ([string]$Name = '*') {
+                $script:emojis | Where-Object Name -like $Name | ForEach-Object Symbol
+            }
 
-    function Get-EmojiKind {
-        param(
-            [Parameter(Mandatory = $true, ValueFromPipeline = $true)]
-            [string]$Emoji
-        )
-        process {
-            $script:emojis | Where-Object Symbol -eq $Emoji | Foreach-Object Kind
-        }
-    }
+            function Get-EmojiKind {
+                param(
+                    [Parameter(Mandatory = $true, ValueFromPipeline = $true)]
+                    [string]$Emoji
+                )
+                process {
+                    $script:emojis | Where-Object Symbol -eq $Emoji | Foreach-Object Kind
+                }
+            }
 
-    $fruitBasket = [System.Collections.ArrayList]@('🍎','🍌','🥝','🥑','🍇','🍐')
+            $fruitBasket = [System.Collections.ArrayList]@('🍎','🍌','🥝','🥑','🍇','🍐')
 
-    function Get-FruitBasket {
-        $script:fruitBasket
-    }
+            function Get-FruitBasket {
+                $script:fruitBasket
+            }
 
-    function Remove-FruitBasket {
-        param(
-            [Parameter(Mandatory = $true)]
-            [string]$Item
-        )
-        $script:fruitBasket.Remove($Item)
-    }
+            function Remove-FruitBasket {
+                param(
+                    [Parameter(Mandatory = $true)]
+                    [string]$Item
+                )
+                $script:fruitBasket.Remove($Item)
+            }
 
-    function Reset-FruitBasket {
-        $script:fruitBasket = [System.Collections.ArrayList]@('🍎','🍌','🥝','🥑','🍇','🍐')
-    }
-} | Import-Module
-```
+            function Reset-FruitBasket {
+                $script:fruitBasket = [System.Collections.ArrayList]@('🍎','🍌','🥝','🥑','🍇','🍐')
+            }
+        } | Import-Module
+        ```
+    </div>
 </details>

docs/usage/importing-tested-functions.mdx

@@ -32,11 +32,11 @@ BeforeAll {
 
 This avoids spelling out the name of the referenced file every time.
 
-:::caution
+:::warning
 The code above is using `string.Replace()` method which is case sensitive. Make sure you say `Tests` and that the test file is named `.Tests.ps1`.
 :::
 
-:::caution
+:::warning
 Pester v4 users might be inclined not to use the `BeforeAll` block or to use `$MyInvocation.MyCommand.Path` in `BeforeAll`. Neither will work. See [Migrating from Pester v4](#migrating-from-pester-v4).
 :::
 

docs/usage/modules.mdx

@@ -112,7 +112,7 @@ Describe "Unit testing the module's internal Build function:" {
 
 Notice that when using `InModuleScope`, you no longer need to specify a `-ModuleName` parameter when calling `Mock` or `Should -Invoke` for commands within that module. You are also able to directly call the `Build` function, which the module does not export.
 
-:::caution Avoid putting in InModuleScope around your Describe and It blocks.
+:::warning Avoid putting in InModuleScope around your Describe and It blocks.
 
 `InModuleScope` is a simple way to expose your internal module functions to be tested, but it prevents you from properly testing your published functions, does not ensure that your functions are actually published and slows down test discovery by loading the module. Aim to avoid it altogether by using `-ModuleName` on `Mock` when possible or at least limit it to inside the It block like the sample above.
 :::

docs/usage/skip.mdx

@@ -54,7 +54,7 @@ Tests completed in 1.03s
 Tests Passed: 1, Failed: 0, Skipped: 4, Total: 5, NotRun: 0
 ```
 
-:::caution
+:::warning
 Pending is translated to skipped, Inconclusive does not exist anymore.
 :::
 

docs/usage/test-file-structure.mdx

@@ -25,7 +25,7 @@ Describe "Get-Emoji" {
 }
 ```
 
-:::caution
+:::warning
 Put all your code into `It`, `BeforeAll`, `BeforeEach`, `AfterAll` or `AfterEach`. Put no code directly into `Describe`, `Context` or on the top of your file, without wrapping it in one of these blocks, unless you have a good reason to do so.
 
 All misplaced code will run during Discovery, and its results won't be available during Run which will lead to confusing results.