#!/usr/bin/env bash
set -e -o pipefail
export APP_ENV="${APP_ENV:-production}"
export WRANGLER_LOG="error"

LOG_FILE="logs/build.log"
LOCK_FILE=".build.lock"

while ! ( set -o noclobber; echo "$$" > "$LOCK_FILE" ) 2>/dev/null; do
  echo "Build already running (lock: $LOCK_FILE). Waiting..." >&2
  sleep 2
done

cleanup() {
  rm -f "$LOCK_FILE"
}

trap cleanup EXIT INT TERM

# reset logs/server.log before each build to prevent confusion
: > logs/server.log

# Snapshot build/{server,client} into an immutable build/{server,client}-<N>
# generation pair. The preview runtime serves from the newest COMPLETE
# generation, so requests never observe a half-written build (react-router
# build empties build/client and build/server in place, which caused
# SSR-HTML/client-chunk hash mismatches — React hydration `removeChild`
# errors — whenever a page loaded during a rebuild). The `mv` per directory
# is atomic; client is published before server because the runtime keys a
# generation's completeness on `server-<N>/index.js`.
publish_generation() {
  [ -d build/server ] && [ -d build/client ] || return 0
  local last=0 n d next staging
  for d in build/server-*; do
    n="${d##*-}"
    case "$n" in *[!0-9]* | '') continue ;; esac
    [ "$n" -gt "$last" ] && last="$n"
  done
  next=$((last + 1))
  staging="build/.staging-$next"
  rm -rf "$staging"
  mkdir -p "$staging"
  cp -Rp build/client "$staging/client"
  cp -Rp build/server "$staging/server"
  mv "$staging/client" "build/client-$next"
  mv "$staging/server" "build/server-$next"
  rm -rf "$staging"
  # Keep the two newest generations: pages rendered against N-1 may still
  # request its hashed assets while N is going live.
  for d in build/server-* build/client-*; do
    n="${d##*-}"
    case "$n" in *[!0-9]* | '') continue ;; esac
    [ "$n" -le $((next - 2)) ] && rm -rf "$d"
  done
  return 0
}

{
  pnpm clean
  pnpm typegen
  pnpm exec react-router build
  publish_generation
} 2>&1 | tee "$LOG_FILE"

exit ${PIPESTATUS[0]}
