The CLI

node xql-lint.mjs --schema xql-intellisense.json -e 'dataset = xdr_data | limit 10'
no problems found
exit 0

node xql-lint.mjs --schema xql-intellisense.json -e 'dataset = xdr_data | fields bogus_zzz'
<query>:1:29  error  bogus_zzz is not a valid field

1 error, 0 warnings
exit 1

node xql-lint.mjs --schema xql-intellisense.json -e 'dataset = xdr_data | filter (_time = 1'
<query>:1:38  error  missing  ')'

1 error, 0 warnings
exit 1

node xql-lint.mjs query.xql
xql-lint: no tenant schema found — validating syntax only. See --help.
no problems found
exit 0

node xql-lint.mjs --schema xql-intellisense.json query.xql
query.xql:3:13  error  field is invalid - does not exist

1 error, 0 warnings
exit 1

node xql-lint.mjs --schema xql-intellisense.json --json -e 'dataset = xdr_data | fields bogus_zzz'
[
  {
    "file": "<query>",
    "line": 1,
    "column": 29,
    "endLine": 1,
    "endColumn": 30,
    "severity": "error",
    "message": "bogus_zzz is not a valid field"
  }
]
exit 1

node xql-lint.mjs --schema xql-intellisense.json --strict -e 'datamodel = xdr_data | limit 5'
<query>:1:1  error  datamodel is planned for deprecation within the next year. We recommend transitioning to the new XDM schema-on-write datasets for enhanced performance and usability.
<query>:1:13  error  xdr_data is not a valid datamodel
<query>:1:22  error  operator is missing

3 errors, 0 warnings
exit 1

node xql-lint.mjs --help
xql-lint 1.0.0 — validate XQL queries offline.

Usage:
  xql-lint [options] [file ...]
  xql-lint [options] -e '<query>'
  cat query.xql | xql-lint [options]

Options:
  -e, --eval <query>   Lint the query given on the command line.
  -s, --schema <path>  Tenant schema JSON (get_intellisense_values output).
      --json           Emit findings as JSON.
      --strict         Treat warnings as errors.
  -q, --quiet          Print findings only — no summary, no schema notice.
  -v, --version        Print the version.
  -h, --help           Print this help.

Schema resolution, first hit wins:
  --schema <path>
  $XQL_SCHEMA
  xql-intellisense.json next to this script
  ~/.config/xql-toolchain/xql-intellisense.json
  ../crtxtool/config/xql-schema.json

Without a schema, validation degrades to syntax only: the grammar still reports
malformed queries, but field and dataset names cannot be resolved.

Refresh the schema with:  crtxtool xql schema
exit 0