feat(build): ✨ Introduce build.ps1 for streamlined packaging and installation

* Replaced `package-and-install.ps1` and `package-and-install.bat` with a unified `build.ps1` script.
* Added support for bootstrapping dependencies and running various tasks (e.g., `Test`, `Install`, `Package`).
* Updated `README.md` and `PACKAGING.md` to reflect new build process.
* Enhanced `package.json` scripts for improved task execution.
* Added `psake.ps1` for build task management and CI integration.
* Introduced `requirements.psd1` for dependency management.
* Added tests for `package.json` validation.

Author: HeyItsGilbert

PACKAGING.md

@@ -3,36 +3,51 @@
 This document explains how to package and install the PowerShell Localization
 extension for development and testing purposes.
 
+> [!NOTE]
+> Tasks are split between psake and yarn. This is due to the fact that
+> psake can setup more robust dependencies. Several tasks can only be called via
+> Node so those calls stay in the package.json
+
 ## Quick Start
 
-### Option 1: PowerShell Script (Recommended)
+### Bootstrap
+
+To install all the necessary dependencies ensure that you bootstrap your
+environment.
 
 ```powershell
-.\package-and-install.ps1
+.\build.ps1 -Bootstrap
 ```
 
-### Option 2: Batch File (Windows)
+### Option 1: PowerShell Build Script (Recommended)
 
-```cmd
-package-and-install.bat
+```powershell
+# To run through the compile, lint, and test
+.\build.ps1 -Task Test
+# To run all the tests + Install
+.\build.ps1 -Task Install
+# To see all the possible tasks
+.\build.ps1 -Help
 ```
 
-### Option 3: NPM Scripts
+This will configure the environment and perform a clean build, compile, lint,
+package, and install the extension.
 
-```bash
-# Package and install
-yarn package-install
+#### To install
 
-# Package only (skip installation)
-yarn package-only
+### Option 2: NPM Scripts
 
-# Package using vsce directly
+```bash
+# Package (calls psake)
 yarn package
+
+# Get a list of packages
+yarn run
 ```
 
 ## Script Features
 
-The `package-and-install.ps1` script provides the following functionality:
+The `build.ps1` script provides the following functionality (via `psake.ps1`):
 
 - ✅ **Dependency Check**: Automatically installs `vsce` if not present
 - 🧹 **Clean Build**: Removes previous builds and packages
@@ -43,18 +58,23 @@ The `package-and-install.ps1` script provides the following functionality:
 
 ## Script Parameters
 
+See
+[Parameters & Properties](https://psake.dev/docs/tutorial-basics/parameters-properties)
+for a more detailed explanation. It is highly unlikely you'll need to modify any
+of the properties.
+
 ```powershell
-# Package and install (default)
-.\package-and-install.ps1
+# Test (default)
+.\build.ps1
 
-# Package only, skip installation
-.\package-and-install.ps1 -SkipInstall
+# Package only to a different output directory
+.\build.ps1 -Task Package -Parameters @{ OutDir = '/path/to/dir' }
 
 # Force installation even if already installed
-.\package-and-install.ps1 -Force
+.\build.ps1 -Parameters @{ Force = $true }
 
 # Combine parameters
-.\package-and-install.ps1 -SkipInstall -Force
+.\build.ps1 -Parameters @{ SkipInstall = $true; Force = $true }
 ```
 
 ## Manual Steps
@@ -82,12 +102,12 @@ If you prefer to run the steps manually:
 4. **Package extension**:
 
    ```bash
-   vsce package
+   vsce package --allow-missing-repository --out $script:outDir
    ```
 
 5. **Install extension**:
 
-   ```bash
+   ```shell
    code --install-extension powershelllocalization-*.vsix
    ```
 
@@ -116,22 +136,19 @@ After installation:
 1. Reload VS Code (`Ctrl+Shift+P` → "Developer: Reload Window")
 2. Open a PowerShell file (`.ps1`, `.psm1`, or `.psd1`)
 3. Check that the extension is active in the Extensions panel
+4. You should see logs in the Output panel.
 
-### Clean Installation
+### Continuous Integration
 
-To completely clean and reinstall:
+For GitHub Actions or other CI systems, use the `CI` task to output build/package information:
 
 ```powershell
-# Remove old packages
-Remove-Item *.vsix -Force
-
-# Clean compiled output
-Remove-Item -Recurse out -Force
-
-# Run full package and install
-.\package-and-install.ps1 -Force
+.\build.ps1 -Task CI
 ```
 
+This will output the VSIX path, name, and Changelog information to
+`$env:GITHUB_OUTPUT` for use in workflows.
+
 ## Development Workflow
 
 For active development, you can use the watch mode:

README.md

@@ -4,7 +4,8 @@ A Visual Studio Code extension that displays PowerShell localization variable
 values as decorations in your editor, making it easier to develop and debug
 internationalized PowerShell modules.
 
-![Example showing the inline decorator](static/image.png)
+<!-- Full image URL with https required for vscode -->
+![Example showing the inline decorator](https://github.com/PSInclusive/PowerShellLocalization/raw/main/static/image.png)
 
 ## Features
 
@@ -53,15 +54,15 @@ This extension contributes the following settings:
 
 To build and install this extension:
 
-```bash
-# Using PowerShell script
-.\package-and-install.ps1
-
-# Using npm scripts
-yarn package-install
-
-# Package only
-yarn package-only
+```pwsh
+# Using pwsh (all OS's)
+./build.ps1 -Task Test
+# Use the -Bootstrap flag to install all the dependancies.
+./build.ps1 -Task Test -Bootstrap
+# You can also list all the available tasks with -Help
+./build.ps1 -Help
+# To install a local build
+./build.ps1 -Task Install
 ```
 
 ## Usage

build.ps1

@@ -0,0 +1,48 @@
+[CmdletBinding(DefaultParameterSetName = 'Task')]
+param(
+  # Build task(s) to execute
+  [parameter(ParameterSetName = 'task', position = 0)]
+  [string[]]$Task = 'default',
+
+  # Bootstrap dependencies
+  [switch]$Bootstrap,
+
+  # List available build tasks
+  [parameter(ParameterSetName = 'Help')]
+  [switch]$Help,
+
+  # Optional properties to pass to psake
+  [hashtable]$Properties,
+
+  # Optional parameters to pass to psake
+  [hashtable]$Parameters
+)
+
+$ErrorActionPreference = 'Stop'
+
+# Bootstrap dependencies
+if ($Bootstrap.IsPresent) {
+  Get-PackageProvider -Name Nuget -ForceBootstrap | Out-Null
+  Set-PSRepository -Name PSGallery -InstallationPolicy Trusted
+  if ((Test-Path -Path ./requirements.psd1)) {
+    if (-not (Get-Module -Name PSDepend -ListAvailable)) {
+      Install-Module -Name PSDepend -Repository PSGallery -Scope CurrentUser -Force
+    }
+    Import-Module -Name PSDepend -Verbose:$false
+    Invoke-PSDepend -Path './requirements.psd1' -Install -Import -Force -WarningAction SilentlyContinue
+  } else {
+    Write-Warning 'No [requirements.psd1] found. Skipping build dependency installation.'
+  }
+} else {
+  Invoke-PSDepend -Path './requirements.psd1' -Import -Force -WarningAction SilentlyContinue
+}
+
+# Execute psake task(s)
+$psakeFile = './psake.ps1'
+if ($PSCmdlet.ParameterSetName -eq 'Help') {
+  Get-PSakeScriptTasks -BuildFile $psakeFile |
+    Format-Table -Property Name, Description, Alias, DependsOn
+} else {
+  Invoke-psake -buildFile $psakeFile -taskList $Task -nologo -properties $Properties -parameters $Parameters
+  exit ([int](-not $psake.build_success))
+}

cspell.json

@@ -6,6 +6,7 @@
         "powershell"
     ],
     "words": [
+        "psake",
         "psinclusive",
         "powershelllocalization"
     ],