Skip to content

Add compiled document batches across JavaScript runtimes - #61

Merged
krflol merged 3 commits into
mainfrom
fix/engine-2-5-29
Oct 30, 2026
Merged

krflol merged 3 commits into
mainfrom
fix/engine-2-5-29

Conversation

@krflol

@krflol krflol commented Oct 30, 2026 •

Copy link
Copy Markdown
Contributor

Generating a family of notices or statements currently requires JavaScript applications to render each record separately and track page ranges themselves. This adds renderPdfBatch() to Node, the render queue, the browser renderer, and Cloudflare Workers. It compiles one template per request and returns one PDF in record order, with page ranges and missing-character reports for each record.

Reflow is the default; fixed layout retains the compiled geometry and selected fonts. Records are snapshotted before asynchronous work, share the source-byte budget, and retain existing cancellation, queue, and process-shutdown behavior. Component-authored templates use the same API, with required renderer options preserved by TypeScript. The adapter pins the published Fullbleed 2.5.46 core for its compiled reports; historical rendering fixtures and expected hashes are preserved.

Local Windows qualification:

  • 123 Node tests, 82 Python verifier tests, and all TypeScript configurations pass.
  • 421 native/WASI fixtures match PDF and preview bytes, including seven batch fixtures and their reports.
  • The isolated npm install checks ESM, CommonJS/process, queue behavior, failure recovery, and both actual README examples. Independent readers checked nine PDFs / 19 pages; visual evidence is retained.
  • Chrome, Firefox, and Playwright WebKit each pass 523 browser fixtures, downloaded bytes, record snapshots, limits, malformed reports, cancellation, and recovery.
  • Local workerd passes 16 retained results and 15 error cases. The standalone invoice starter also passes six PDF results and ten error cases, with independent checks of all ten pages. This is local runtime evidence, not a hosted/free-plan claim.

The current-engine font-layout reference retains every expected PDF, preview, text, and font value from the 2.5.43 reference. Independent reinspection of the actual Linux CI output passes all seven font specimens; the original reference and comparison logic remain intact.

The draft remains pending the exact-source CI matrix and release-artifact qualification. Version 0.9.0 has not been published to npm. Selected-font diagnostics do not establish layout, shaping, accessibility, or PDF conformance.

@krflol
krflol marked this pull request as ready for review October 30, 2026 22:54
@krflol
krflol merged commit c3d1d88 into main Oct 30, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant