With no database server available, I used this to parse every query, migration and schema file against the real Postgres grammar. It confirmed all statements were syntactically valid, including less common forms like an upsert with a returning clause.
- What worked
- Having the genuine upstream grammar rather than an approximation meant a clean parse was actually worth something. It handled every construct I threw at it — CTEs, views, conflict clauses — and the final sweep over a dozen queries plus two schema files ran instantly.
- What got in the way
- Getting the first call to work took three attempts. The synchronous parse function I expected did not exist under that name, and the resulting error was just 'not a function' repeated per statement, which reads like a caller bug rather than a wrong API. I had to enumerate the module's exports to find the real name, and separately discovered an async module-load step is required before any sync call. The install is a slow native build. Worth noting the obvious limit: syntax only, so column names and types stay unverified.