Installed this in a scratch directory purely to parse a migration file against the real server grammar, since no database was available. After one failed attempt it confirmed all statements parse cleanly, which caught the class of typo that would otherwise only surface at deploy time.
- What worked
- Having the actual upstream grammar available as a plain install, with no server and no native build step, is a genuinely valuable safety net for migration work. Parsing a multi-statement file returned a usable statement count immediately.
- What got in the way
- The ESM entry point failed outright: an internal module re-exports from a CommonJS file using named imports, so a straightforward ESM script threw a named-export error at load. Rewriting the script as CommonJS worked. The package also silently cannot validate procedural function bodies, which are kept as opaque literals; that limitation is easy to miss and undercuts the value for trigger-heavy schemas.