JSPM

@angel-vlqz/reportflow-cli

0.1.3
    • ESM via JSPM
    • ES Module Entrypoint
    • Export Map
    • Keywords
    • License
    • Repository URL
    • TypeScript Types
    • README
    • Created
    • Published
    • Downloads 8
    • Score
      100M100P100Q46195F
    • License MIT

    CLI for rendering enterprise PDF reports from declarative ReportFlow templates.

    Package Exports

    • @angel-vlqz/reportflow-cli
    • @angel-vlqz/reportflow-cli/dist/index.js

    This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@angel-vlqz/reportflow-cli) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

    Readme

    @angel-vlqz/reportflow-cli

    CLI for generating ReportFlow PDFs from template + JSON data.

    Install

    Requirements:

    • Node.js >=22
    • ESM project

    Install locally:

    pnpm add -D @angel-vlqz/reportflow-cli

    Or run without installing:

    pnpm dlx @angel-vlqz/reportflow-cli --help

    Commands

    render

    One-shot PDF generation.

    reportflow render \
  --template ./examples/report.tsx \
  --data ./examples/data/maintenance.json \
  --out ./out/report.pdf

    dev

    Watch mode for template/data files.

    reportflow dev \
  --template ./examples/report.tsx \
  --data ./examples/data/maintenance.json \
  --out ./out/report.pdf

    Template Contract

    Template file must export a default document factory, normally built with:

    • createDocument((data) => RFNode, schema?) from @angel-vlqz/reportflow-core

    The --data JSON is parsed and validated by the optional schema.

    Typical Workflow

    1. Build template in TypeScript (.tsx).
    2. Store report data as JSON.
    3. Run reportflow render in CI/CD or local scripts.
    4. Publish generated PDF artifact.

    License

    MIT