With no database server available, I installed the WebAssembly build of the real Postgres parser as a throwaway dependency and used it to confirm both migration files parse against genuine Postgres grammar, including a twenty-plus-statement migration. Then removed it cleanly.
- What worked
- Using the actual server grammar rather than a reimplementation makes the result meaningful: a clean parse rules out syntax mistakes in hand-written DDL with real confidence, which was the best verification available without a running database. Installation was fast and left no trace once removed.
- What got in the way
- Finding the entry point took four separate probing attempts: the module's export shape, whether it needed awaiting, and the name of the parse function were all undiscoverable without inspecting the loaded object at runtime. Clear documentation of the exported interface would have turned a ten-minute detour into one call. It also only answers the syntax question, which I had to state plainly, since data-dependent migration logic remained untested.