Added build scripts for linux, macos and windows to help new contributors get setup quickly (#21)

Co-authored-by: Vijay A <vraravam@users.noreply.github.com>
Co-authored-by: André Oliveira <oliveira.andrerodrigues95@gmail.com>

8 files changed, 324 insertions, 82 deletions

diff --git a/.devcontainer/Dockerfile b/.devcontainer/Dockerfile
index 048cebe2d..1fe3880c8 100644
--- a/.devcontainer/Dockerfile
+++ b/.devcontainer/Dockerfile
@@ -1,7 +1,7 @@
 # See here for image contents: https://github.com/microsoft/vscode-dev-containers/tree/v0.174.0/containers/javascript-node/.devcontainer/base.Dockerfile
 
-# [Choice] Node.js version: 14, 12, 10
-ARG VARIANT="14-buster"
+# [Choice] Node.js version: 18
+ARG VARIANT="18-buster"
 FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:0-${VARIANT}
 
 # [Optional] Uncomment this section to install additional OS packages.
@@ -13,4 +13,4 @@ FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:0-${VARIANT}
 # RUN su node -c "source /usr/local/share/nvm/nvm.sh && nvm install ${EXTRA_NODE_VERSION}"
 
 # [Optional] Uncomment if you want to install more global node modules
-# RUN su node -c "npm install -g <your-package-list-here>"
+# RUN su node -c "npm i -g <your-package-list-here>"
diff --git a/.devcontainer/devcontainer.json b/.devcontainer/devcontainer.json
index 85a9c5a3b..54d7c459b 100644
--- a/.devcontainer/devcontainer.json
+++ b/.devcontainer/devcontainer.json
@@ -24,7 +24,7 @@
   // "forwardPorts": [],
 
   // Use 'postCreateCommand' to run commands after the container is created.
-  // "postCreateCommand": "npm install",
+  // "postCreateCommand": "npm i",
 
   // Comment out connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root.
   "remoteUser": "node"
diff --git a/.github/workflows/builds.yml b/.github/workflows/builds.yml
index 914f2fefd..b84729522 100644
--- a/.github/workflows/builds.yml
+++ b/.github/workflows/builds.yml
@@ -23,10 +23,10 @@ on:
   workflow_dispatch:
     inputs:
       message:
-        description: 'Message for build'
+        description: "Message for build"
         required: true
   schedule:
-    - cron: '15 0 * * *' # every night at 12:15 am (to allow for dependency builds to complete)
+    - cron: "15 0 * * *" # every night at 12:15 am (to allow for dependency builds to complete)
 
 env:
   USE_HARD_LINKS: false
@@ -35,7 +35,7 @@ env:
 jobs:
   check_updates:
     runs-on: ubuntu-latest
-    name: 'Check latest commit: ${{ github.event.inputs.message }}'
+    name: "Check latest commit: ${{ github.event.inputs.message }}"
     outputs:
       should_run: ${{ steps.should_run.outputs.should_run }}
     steps:
@@ -51,7 +51,7 @@ jobs:
         uses: actions/setup-node@v3
         if: ${{ github.event_name == 'schedule' || (github.event_name == 'workflow_dispatch' && contains(github.event.inputs.message, '[nightly branch]')) }}
         with:
-          node-version-file: '.nvmrc'
+          node-version-file: ".nvmrc"
       - id: should_run
         name: Check whether there are any commits since this run was last triggered and push them and/or set the output
         if: ${{ github.event_name == 'schedule' || (github.event_name == 'workflow_dispatch' && contains(github.event.inputs.message, '[nightly branch]')) }}
@@ -93,7 +93,7 @@ jobs:
           fi
 
   build_mac:
-    name: 'macos ${{ github.event.inputs.message }}'
+    name: "macos ${{ github.event.inputs.message }}"
     needs: check_updates
     if: ${{ (needs.check_updates.outputs.should_run != 'false') && (github.event_name != 'workflow_dispatch' || (github.event_name == 'workflow_dispatch' && (contains(github.event.inputs.message, '[macOS]') || (!contains(github.event.inputs.message, '[macOS]') && !contains(github.event.inputs.message, '[Linux]') && !contains(github.event.inputs.message, '[Windows]'))))) }}
     runs-on: macos-latest
@@ -136,13 +136,11 @@ jobs:
       - name: Use Node.js specified in the '.nvmrc' file
         uses: actions/setup-node@v3
         with:
-          node-version-file: '.nvmrc'
+          node-version-file: ".nvmrc"
       - name: Install npm
-        run: npm i -gf npm@8.7.0
+        run: npm i -gf "npm@$(jq --raw-output .engines.npm ./package.json)" && npm -v
       - name: Install pnpm
-        uses: pnpm/action-setup@v2.0.1
-        with:
-          version: 6.32.8
+        run: npm i -gf "pnpm@$(jq --raw-output .engines.pnpm ./recipes/package.json)" && pnpm -v
       - name: Install node dependencies
         run: npm i
       - name: Package recipes
@@ -180,7 +178,7 @@ jobs:
           # CSC_KEY_PASSWORD: ${{ secrets.CSC_KEY_PASSWORD }}
 
   build_linux:
-    name: 'ubuntu ${{ github.event.inputs.message }}'
+    name: "ubuntu ${{ github.event.inputs.message }}"
     needs: check_updates
     if: ${{ (needs.check_updates.outputs.should_run != 'false') && (github.event_name != 'workflow_dispatch' || (github.event_name == 'workflow_dispatch' && (contains(github.event.inputs.message, '[Linux]') || (!contains(github.event.inputs.message, '[macOS]') && !contains(github.event.inputs.message, '[Linux]') && !contains(github.event.inputs.message, '[Windows]'))))) }}
     runs-on: ubuntu-20.04
@@ -223,13 +221,11 @@ jobs:
       - name: Use Node.js specified in the '.nvmrc' file
         uses: actions/setup-node@v3
         with:
-          node-version-file: '.nvmrc'
+          node-version-file: ".nvmrc"
       - name: Install npm
-        run: npm i -gf npm@8.7.0
+        run: npm i -gf "npm@$(jq --raw-output .engines.npm ./package.json)" && npm -v
       - name: Install pnpm
-        uses: pnpm/action-setup@v2.0.1
-        with:
-          version: 6.32.8
+        run: npm i -gf "pnpm@$(jq --raw-output .engines.pnpm ./recipes/package.json)" && pnpm -v
       - name: Install node dependencies
         run: npm i
       - name: Figure out used package.json version
@@ -288,7 +284,7 @@ jobs:
         shell: bash
 
   build_windows:
-    name: 'windows ${{ github.event.inputs.message }}'
+    name: "windows ${{ github.event.inputs.message }}"
     needs: check_updates
     if: ${{ (needs.check_updates.outputs.should_run != 'false') && (github.event_name != 'workflow_dispatch' || (github.event_name == 'workflow_dispatch' && (contains(github.event.inputs.message, '[Windows]') || (!contains(github.event.inputs.message, '[macOS]') && !contains(github.event.inputs.message, '[Linux]') && !contains(github.event.inputs.message, '[Windows]'))))) }}
     runs-on: windows-latest
@@ -315,13 +311,11 @@ jobs:
       - name: Use Node.js specified in the '.nvmrc' file
         uses: actions/setup-node@v3
         with:
-          node-version-file: '.nvmrc'
+          node-version-file: ".nvmrc"
       - name: Install npm
-        run: npm i -gf npm@8.7.0
+        run: npm i -gf "npm@$(jq --raw-output .engines.npm package.json)" && npm -v
       - name: Install pnpm
-        uses: pnpm/action-setup@v2.0.1
-        with:
-          version: 6.32.8
+        run: npm i -gf "pnpm@$(jq --raw-output .engines.pnpm ./recipes/package.json)" && pnpm -v
       - name: Install node dependencies
         uses: nick-invision/retry@v2.4.0
         with:
diff --git a/.vscode/launch.json b/.vscode/launch.json
index 78db6562c..24002a53b 100644
--- a/.vscode/launch.json
+++ b/.vscode/launch.json
@@ -2,6 +2,13 @@
     "version": "0.2.0",
     "configurations": [
         {
+            "name": "PowerShell Launch Current File",
+            "type": "PowerShell",
+            "request": "launch",
+            "script": "${file}",
+            "cwd": "${workspaceFolder}"
+        },
+        {
             "type": "node",
             "request": "launch",
             "name": "Ferdium - Test API",
diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
index 93d858182..ab89b2307 100644
--- a/CODE_OF_CONDUCT.md
+++ b/CODE_OF_CONDUCT.md
@@ -2,7 +2,7 @@
 
 As contributors and maintainers of the Ferdium project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities.
 
-Communication through GitHub, Slack, email or any other channel must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct.
+Communication through GitHub, Discord, email or any other channel must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct.
 
 We promise to extend courtesy and respect to everyone involved in this project regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to the project to do the same.
 
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index abcbac9f2..78b9a36be 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -1,4 +1,4 @@
-# Contributing to Ferdium 5
+# Contributing to Ferdium 6
 
 :tada: First off, thanks for taking the time and your effort to make Ferdium better! :tada:
 
@@ -6,95 +6,99 @@
 
 <!-- TOC depthFrom:2 depthTo:2 withLinks:1 updateOnSave:1 orderedList:0 -->
 
-- [Contributing to Ferdium 5](#contributing-to-ferdium-5)
-  - [Table of contents](#table-of-contents)
-  - [Code of Conduct](#code-of-conduct)
-  - [What should I know before I get started?](#what-should-i-know-before-i-get-started)
-  - [How Can I Contribute?](#how-can-i-contribute)
-  - [Setting up your Development machine](#setting-up-your-development-machine)
-    - [Install System-level dependencies](#install-system-level-dependencies)
-      - [Node.js, npm, pnpm](#nodejs-npm-pnpm)
-      - [Git](#git)
-      - [Debian/Ubuntu](#debianubuntu)
-      - [Fedora](#fedora)
-      - [Windows](#windows)
-    - [Clone repository with submodule](#clone-repository-with-submodule)
-    - [Local caching of dependencies](#local-caching-of-dependencies)
-    - [Install dependencies](#install-dependencies)
-    - [Fix native modules to match current electron node version](#fix-native-modules-to-match-current-electron-node-version)
-    - [Package recipe repository](#package-recipe-repository)
-    - [Using Docker to build a linux-targetted packaged app](#using-docker-to-build-a-linux-targetted-packaged-app)
-    - [Code Signing on a mac](#code-signing-on-a-mac)
-    - [Start development app](#start-development-app)
-    - [Styleguide](#styleguide)
-      - [Git Commit Messages format](#git-commit-messages-format)
-      - [Javascript Coding style-checker](#javascript-coding-style-checker)
-  - [Packaging](#packaging)
-  - [Release](#release)
-    - [Nightly releases](#nightly-releases)
-    - [Updating the code after a hiatus](#updating-the-code-after-a-hiatus)
+- [Table of contents](#table-of-contents)
+- [Code of Conduct](#code-of-conduct)
+- [What should I know before I get started?](#what-should-i-know-before-i-get-started)
+- [How can I contribute?](#how-can-i-contribute)
+- [Setting up your development machine](#setting-up-your-development-machine)
+  - [Install system-level dependencies](#install-system-level-dependencies)
+    - [Node.js, npm, pnpm](#nodejs-npm-pnpm)
+    - [Git](#git)
+    - [On Debian/Ubuntu](#on-debianubuntu)
+    - [On Fedora](#on-fedora)
+    - [On Windows](#on-windows)
+  - [Clone repository with submodule](#clone-repository-with-submodule)
+  - [Local caching of dependencies](#local-caching-of-dependencies)
+  - [Install dependencies](#install-dependencies)
+  - [Fix native modules to match current electron node version](#fix-native-modules-to-match-current-electron-node-version)
+  - [Package recipe repository](#package-recipe-repository)
+  - [Using Docker to build a linux-targetted packaged app](#using-docker-to-build-a-linux-targetted-packaged-app)
+  - [Code Signing on a mac](#code-signing-on-a-mac)
+  - [Start development app](#start-development-app)
+  - [Styleguide](#styleguide)
+    - [Git Commit Messages format](#git-commit-messages-format)
+    - [Javascript Coding style-checker](#javascript-coding-style-checker)
+- [Packaging](#packaging)
+- [Release](#release)
+  - [Nightly releases](#nightly-releases)
+  - [Updating the code after a hiatus](#updating-the-code-after-a-hiatus)
 
 <!-- /TOC -->
 
 ## Code of Conduct
 
-This project and everyone participating in it is governed by the [Ferdium Code of Conduct](CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code. Please report unacceptable behavior to [hello@ferdium.org](mailto:hello@ferdium.org).
+This project and everyone participating in it is governed by the [Ferdium Code of Conduct](CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code.
+Please report unacceptable behavior to [hello@ferdium.org](mailto:hello@ferdium.org).
 
 ## What should I know before I get started?
 
-For the moment, Ferdium's development is a bit slow but all contributions are highly appreciated. [Check this issue for discussion](https://github.com/ferdium/ferdium-app/issues/956).
+For the moment, Ferdium's development is only starting, aiming at releasing a 6.0.0 version with the rebranded assets and tooling upgrade completed.
+You can join the Discord official chat here : https://discord.com/invite/xpNTzgKmHM.
 
-## How Can I Contribute?
+## How can I contribute?
 
-As a basic rule, before filing issues, feature requests or anything else. Take a look at the issues and check if this has not already been reported by another user. If so, engage in the already existing discussion.
+As a basic rule, before filing issues, feature requests or anything else : take a look at the existing issues and check if this has not already been reported by another user.
+If so, engage in the already existing discussion.
 
-## Setting up your Development machine
+## Setting up your development machine
 
-### Install System-level dependencies
+### Install system-level dependencies
+
+_Note:_ This list can likely get outdated. If so, please refer to the specific version of the [electronuserland builder](https://hub.docker.com/r/electronuserland/builder) that we use in our [Dockerfile](./Dockerfile).
 
 #### Node.js, npm, pnpm
 
-Please make sure you are conforming to the `engines` requirements used by the developers/contributors as specified in the [package.json file](./package.json#engines).
+Please make sure you are conforming to the `engines` requirements used by the developers/contributors as specified in the [`package.json`](./package.json#engines) and [`recipes/package.json`](./recipes/package.json#engine) files.
 
 Currently, these are the combinations of system dependencies that work for MacOS/Linux/Windows:
 
 ```bash
-node -v
-v18.0.0
-npm -v
-8.7.0
-pnpm -v
-6.32.8
-python -v
-3.10.4
+$ jq --null-input '[inputs.engines] | add' < ./package.json < ./recipes/package.json
+{
+  "node": "18.0.0",
+  "npm": "8.7.0",
+  "pnpm": "6.32.8"
+}
+
+$ python --version
+Python 3.10.4
 ```
 
-_Note:_ You can choose any package manager to manage multiple versions of `node` and `npm`. For eg, [nvm](https://github.com/nvm-sh/nvm) or [asdf](https://github.com/asdf-vm/asdf).
+_Note:_ You can choose any version manager to manage multiple versions of `node` and `npm`. For eg, [nvm](https://github.com/nvm-sh/nvm) or [asdf](https://github.com/asdf-vm/asdf).
 
 #### Git
 
 The version [2.23.0](https://github.com/git-for-windows/git/releases/tag/v2.23.0.windows.1) for Git is working fine for development. You can then use the console from Git to do the development procedure.
 
-_Note:_ This list can likely get outdated. If so, please refer to the specific version of the [electronuserland builder](https://hub.docker.com/r/electronuserland/builder) that we use in our [Dockerfile](./Dockerfile).
-
-#### Debian/Ubuntu
+#### On Debian/Ubuntu
 
 ```bash
 apt-get update -y && apt-get install --no-install-recommends -y rpm ruby gem && gem install fpm --no-ri --no-rdoc --no-document
 ```
 
-#### Fedora
+#### On Fedora
 
 ```bash
 dnf install libX11-devel libXext-devel libXScrnSaver-devel libxkbfile-devel rpm
 ```
 
-#### Windows
+#### On Windows
 
 Please make sure you have the following installed:
 
 - Python 3 or higher (we recommend the latest version: [3.10.4](https://www.python.org/ftp/python/3.10.4/python-3.10.4-amd64.exe))
 - Microsoft Visual Studio Build Tools (2019 or higher) - Only tested with 2019 so far.
+
 ### Clone repository with submodule
 
 ```bash
@@ -103,20 +107,18 @@ cd ferdium
 git submodule update --init --recursive --remote --rebase --force
 ```
 
-It is important you execute the last command to get the required submodules (recipes).
+It is important you execute the last command to get the required submodule (ferdium-recipes).
 
 ### Local caching of dependencies
 
 Set these env vars into your profile (or if you use [direnv](https://direnv.net/), you can manage them via the respective `.envrc` file)
 
 ```bash
+# On bash or equivalent
 export ELECTRON_CACHE=$HOME/.cache/electron
 export ELECTRON_BUILDER_CACHE=$HOME/.cache/electron-builder
-```
 
-#### If you are using Powershell:
-If you are using Powershell make sure you set the following env vars
-```
+# On Powershell
 $env:CI = $true
 $env:ELECTRON_CACHE = $HOME + '\.cache\electron'
 $env:ELECTRON_BUILDER_CACHE = $HOME + '\.cache\electron-builder'
@@ -218,7 +220,11 @@ Note: please prefer [`debug()`](https://github.com/visionmedia/debug) over `cons
 ## Packaging
 
 ```bash
-npm run build
+# On Unix
+./scripts/build-unix.sh
+
+# On Windows
+.\scripts\build-windows.ps1
 ```
 
 Assets will be available in the `out` folder.
diff --git a/scripts/build-unix.sh b/scripts/build-unix.sh
new file mode 100755
index 000000000..e80c38059
--- /dev/null
+++ b/scripts/build-unix.sh
@@ -0,0 +1,135 @@
+#!/bin/bash
+
+# INTRO:
+# This file is used to build ferdium on both x64 and arm-based for macos and linux (not tested on arm for linux).
+# It also handles any corrupted node modules with the 'CLEAN' env var (set it to 'true' for cleaning)
+# It will install the system dependencies except for node (which is still verified)
+# I sometimes symlink my 'recipes' folder so that any changes that I need to do in it can also be committed and pushed
+# This file can live anywhere in your PATH
+
+set -e
+
+export ELECTRON_CACHE=$HOME/.cache/electron
+export ELECTRON_BUILDER_CACHE=$HOME/.cache/electron-builder
+export CSC_IDENTITY_AUTO_DISCOVERY=false
+export CI=true
+
+# -----------------------------------------------------------------------------
+#                  Utility functions
+fail_with_docs() {
+  printf "\n*************** FAILING ***************\n"
+  echo "$1"
+  echo ""
+  echo "Please read the developer documentation in CONTRIBUTING.md"
+  exit 1
+}
+
+command_exists() {
+  type "$1" &>/dev/null 2>&1
+}
+
+# -----------------------------------------------------------------------------
+#                  Checking the developer environment
+# checking for installed programmes
+command_exists node || fail_with_docs "Node is not installed"
+command_exists jq || fail_with_docs "jq is not installed"
+
+EXPECTED_NODE_VERSION=$(cat .nvmrc)
+ACTUAL_NODE_VERSION=$(node -v)
+if [ "v$EXPECTED_NODE_VERSION" != "$ACTUAL_NODE_VERSION" ]; then
+  fail_with_docs "You are not running the expected version of node!
+    expected: [v$EXPECTED_NODE_VERSION]
+    actual  : [$ACTUAL_NODE_VERSION]"
+fi
+
+# Check if the 'recipes' folder is present either as a git submodule or a symbolic link
+if ! [ -f "recipes/package.json" ]; then
+  fail_with_docs "'recipes' folder is missing or submodule has not been checked out"
+fi
+
+# This log statement is only to remind me which 'recipes' folder I am using (symlink or git submodule)
+if [[ -L recipes ]]; then
+  printf "\n*************** CONTINUING for 'recipes' symlinked ***************\n"
+else
+  printf "\n*************** CONTINUING for 'recipes' submodule ***************\n"
+fi
+
+# -----------------------------------------------------------------------------
+# If you are moving to a new version of node or any other system dependency, then cleaning is recommended
+# so that there's no irregular results due to cached modules
+if [ "$CLEAN" != "true" ]; then
+  printf "\n*************** SKIPPING Cleaning ***************\n"
+else
+  printf "\n*************** Cleaning!!!!!! ***************\n"
+  npm cache clean --force
+  rm -rf ~/.npm ~/.node-gyp ~/.asdf/installs/nodejs/*/.npm/
+  if [[ -s 'pnpm-lock.yaml' ]]; then
+    pnpm store prune || true # in case the pnpm executable itself is not present
+    rm -rf ~/.pnpm-store ~/.pnpm-state
+  fi
+
+  git -C recipes clean -fxd # Clean recipes folder/submodule
+  git clean -fxd            # Note: This will blast away the 'recipes' folder if you have symlinked it
+fi
+
+# -----------------------------------------------------------------------------
+printf "\n*************** Installing node dependencies ***************\n"
+# If 'asdf' is installed, reshim for new nodejs if necessary
+command_exists asdf && asdf reshim nodejs
+
+# Ensure that the system dependencies are at the correct version
+EXPECTED_NPM_VERSION=$(jq --raw-output .engines.npm <"package.json")
+EXPECTED_PNPM_VERSION=$(jq --raw-output .engines.pnpm <"./recipes/package.json")
+if [[ "$(npm --version)" != "$EXPECTED_NPM_VERSION" ]]; then
+  npm i -gf "npm@$EXPECTED_NPM_VERSION"
+fi
+if [[ "$(pnpm --version)" != "$EXPECTED_PNPM_VERSION" ]]; then
+  npm i -gf "pnpm@$EXPECTED_PNPM_VERSION"
+fi
+
+# If 'asdf' is installed, reshim for new nodejs if necessary
+command_exists asdf && asdf reshim nodejs
+
+# This is useful if we move from 'npm' to 'pnpm' for the main repo as well
+if [[ -s 'pnpm-lock.yaml' ]]; then
+  BASE_CMD=pnpm
+else
+  BASE_CMD=npm
+fi
+
+# Now the meat.....
+$BASE_CMD i
+$BASE_CMD run prepare-code
+
+# -----------------------------------------------------------------------------
+printf "\n*************** Building recipes ***************\n"
+# Note: 'recipes' is already using only pnpm - can switch to $BASE_CMD AFTER both repos are using pnpm
+pushd recipes
+pnpm i
+pnpm run package
+popd
+
+# -----------------------------------------------------------------------------
+printf "\n*************** Building app ***************\n"
+if [[ "$(uname -m)" =~ "arm" ]]; then
+  TARGET_ARCH=arm64
+else
+  TARGET_ARCH=x64
+fi
+
+if [[ "$(uname)" =~ "Darwin" ]]; then
+  TARGET_OS="mac"
+else
+  TARGET_OS="linux"
+fi
+
+$BASE_CMD run build -- "--$TARGET_ARCH" --"$TARGET_OS" --dir
+
+printf "\n*************** App successfully built! ***************\n"
+# Final check to ensure that the version built is the same as the latest commit
+cat build/buildInfo.json
+git --no-pager log -1
+if [[ $(git rev-parse --short HEAD) != $(jq --raw-output .gitHashShort <"build/buildInfo.json") ]]; then
+  echo "The built version is not on the latest commit"
+  exit 1
+fi
diff --git a/scripts/build-windows.ps1 b/scripts/build-windows.ps1
new file mode 100644
index 000000000..9d4219ffb
--- /dev/null
+++ b/scripts/build-windows.ps1
@@ -0,0 +1,100 @@
+# INTRO:
+# This file is used to build ferdium on windows.
+# It also handles any corrupted node modules with the 'CLEAN' env var (set it to 'true' for cleaning)
+# It will install the system dependencies except for node (which is still verified)
+# I sometimes symlink my 'recipes' folder so that any changes that I need to do in it can also be committed and pushed
+# This file can live anywhere in your PATH
+
+#CHECK PYTHON
+#CHECK NODE.JS
+#CHECK NPM
+#CHECK MSVS_VERSION and MSVS Tools
+
+$USERHOME = "${env:HOMEDRIVE}${env:HOMEPATH}"
+
+$env:ELECTRON_CACHE = $USERHOME + '/.cache/electron'
+$env:ELECTRON_BUILDER_CACHE = $USERHOME + '/.cache/electron-builder'
+$env:CSC_IDENTITY_AUTO_DISCOVERY = $false
+
+$env:CI = $true
+
+$EXPECTED_NODE_VERSION = (Get-Content .\.nvmrc)
+$ACTUAL_NODE_VERSION = (node -v)
+
+if ( "v$EXPECTED_NODE_VERSION" -ne $ACTUAL_NODE_VERSION)
+{
+  Write-Host "You are not running the expected version of node!"
+  Write-Host "  expected: [v$EXPECTED_NODE_VERSION]"
+  Write-Host "  actual  : [$ACTUAL_NODE_VERSION]"
+  exit 1
+}
+
+if ( $env:CLEAN -eq "true" )
+{
+  $NPM_PATH = "$USERHOME\.npm"
+  $NODE_GYP = "$USERHOME\.node-gyp"
+
+  Write-Host "Cleaning!"
+  npm cache clean --force
+  Remove-Item -Path $NPM_PATH -Recurse
+  Remove-Item -Path $NODE_GYP -Recurse
+
+  if ( Test-Path -Path ".\pnpm-lock.yaml" -and (Get-Command -ErrorAction Ignore -Type Application pnpm) )
+  {
+    $PNPM_STORE = "$USERHOME\.pnpm-store"
+    $PNPM_STATE = "$USERHOME\.pnpm-state"
+
+    pnpm store prune
+
+    Remove-Item -Path $PNPM_STORE -Recurse
+    Remove-Item -Path $PNPM_STATE -Recurse
+  }
+
+  git -C recipes clean -fxd
+  git clean -fxd # Note: This will blast away the 'recipes' folder if you have symlinked it
+}
+
+# Ensure that the system dependencies are at the correct version
+npm i -gf npm@8.7.0
+npm i -gf pnpm@6.32.8
+
+# This is useful if we move from 'npm' to 'pnpm' for the main repo as well
+if ( (Test-Path -Path ".\pnpm-lock.yaml") -and (Get-Command -ErrorAction Ignore -Type Application pnpm) )
+{
+  $BASE_CMD="pnpm"
+  $env:EXEC_CMD="pnpm dlx"
+}
+else
+{
+  $BASE_CMD="npm"
+  $env:EXEC_CMD="npx"
+}
+
+# Now the meat.....
+& $BASE_CMD i
+& $BASE_CMD run prepare-code
+
+# Check if the 'recipes' folder is present either as a git submodule or a symbolic link
+if (-not (Test-Path -Path ".\recipes\package.json"))
+{
+  try {
+    git submodule update --init --recursive --remote --rebase --force
+  } catch {
+    Write-Host "FAILING since 'recipes' folder/submodule has not been checked out"
+    exit 1
+  }
+}
+
+# Note: 'recipes' is already using only pnpm - can switch to $BASE_CMD AFTER both repos are using pnpm
+Set-Location recipes
+pnpm i
+pnpm run package
+Set-Location ..
+
+$TARGET_ARCH="x64"
+& $BASE_CMD run build -- --$TARGET_ARCH --dir
+
+# Final check to ensure that the version built is the same as the latest commit
+# TODO: Need to make this an assertion similar to tthe unix-equivalent
+Get-Content "build/buildInfo.json" | ConvertFrom-Json
+git log -1