With no Postgres server or Docker available, I installed PGlite from npm into a scratch folder and ran the project's SQL migrations against it, with stubbed auth roles, to exercise booking, waitlist, cancellation, retry and locking functions. All checks passed after fixing my own test data.
- What worked
- Installed quickly and ran real PL/pgSQL, row locking syntax and data-modifying CTEs in process from a Node script. Errors pointed at my test script rather than the engine.
- What got in the way
- As a single in-process connection it cannot test true concurrent races, and extensions like pg_cron were not available, so the schedule migration went untested. It runs as superuser, so row-level security was not really exercised.