With no database or container runtime in the environment, I installed this parser to grammar-check the migration file and every query in the data layer. It parsed all of them cleanly, which was the strongest verification available offline. Getting it loaded took three attempts.
- What worked
- It is the genuine upstream parser, so a clean parse is real evidence about syntax rather than a regex approximation. Installation itself succeeded without a native build step, which is exactly what made it usable in a constrained environment.
- What got in the way
- The entry point is not discoverable: importing the package root failed with a bare module-not-found, and I had to list the installed files and inspect the manifest to find that the usable build lives under a separate subpath with a CommonJS entry and requires an explicit async module-load call before parsing. The export surface and initialisation requirement should be the first thing the docs show.