pre_commit_hook.sh

#!/usr/bin/env sh

# This line is very important, otherwise the hook doesn't prevent the commit or merge
#   in case of a failure.
set -e

set -x

simulated_git_branch="$1"

git_branch="$(git rev-parse --abbrev-ref HEAD)"

# Assumption for all `if [ "$branch" = "main" ]` blocks:
#   - we develop on branches other than `main`
#   - we release new versions on `main`

if [ "$simulated_git_branch" == "" ]; then
  if [ "$git_branch" = "main" ]; then
    check_mode="full"
  elif [ "$git_branch" == "beetpx.dev" ]; then
    check_mode="none"
  else
    check_mode="dev"
  fi
else
  if [ "$simulated_git_branch" == "main" ]; then
    check_mode="full"
  elif [ "$simulated_git_branch" == "beetpx.dev" ]; then
    check_mode="none"
  else
    check_mode="dev"
  fi
fi

if [ "$check_mode" == "none" ]; then
  exit 0
fi

if [ "$check_mode" == "full" ]; then
  # If version got bumped in package.json, update the version in package-lock.json as well
  npm install
fi

# Make sure everything is formatted as desired
npm run format

if [ "$check_mode" == "full" ]; then
  # Make sure TypeScript types and Jest tests didn't break due to most recent changes.
  # We do this on a `main` branch only in order to allow broken tests while development
  #   is in progress.
  npm run test
fi

if [ "$check_mode" == "full" ]; then
  echo "Checking the playground project ..."
  cd ./playground/
  npm install
  npm run format
  npm run tsc
  npm run test --if-present
  cd ../
fi

# Generate up-to-date JS and .d.ts files out of the TypeScript source.
#   Thanks to this command being run on every commit, users can refer to
#   any commit of this repo in their `package.json` files and have BeetPx
#   ready to use there.
# We do this on all branches, because during engine development we might
#   want to install a specific non-versioned commit of BeetPx in a game
#   repository.
npm run compile

# Whatever was changed due to commands above, let's add it to the commit
git add --all .