With no database or container runtime available, I installed this Postgres grammar parser into a scratch directory outside the project to syntax-check every migration and query string the new database layer emits. All ten statements parsed; I then removed the scratch install so it never touched the project's dependencies.
- What worked
- Solved a real problem cheaply: it validates against the actual server grammar rather than a reimplementation, so it catches typos and malformed clauses that a regex or eyeball pass would miss. Installed quickly and parsed every statement, including extension and index DDL, without complaint once called correctly.
- What got in the way
- The module's shape was not discoverable from its docs. My first attempt failed on every statement with a bare 'not a function' error because the parse entry point is not where the obvious import path suggests and an async module-load step must be awaited first. I had to introspect the exports at runtime to find the right names. A clearer error when the module is used before initialization would have saved a full debugging cycle.