Repository navigation
Add Node render queue guide and downloadable invoice batch - #76
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Node servers and automation consumers need a shared limit on PDF work during request bursts. Add a guide for the public
createRenderQueue()API and a standalone six-invoice project with editable HTML/CSS, a pinned npm lockfile, generated PDFs, and a preview. Explain waiting deadlines, overload responses, cancellation, shutdown, and the per-process, in-memory limits.Update the existing Node quickstart and invoice download to the verified npm 0.4.0 release while preserving their reviewed PDF and PNG bytes. Add the queue example to navigation and the gallery. CI executes the actual ZIP and guide snippet, checks worker lifetimes and exact replay, and reads invoice fields through pypdf and PDFium. Download sources use consistent line endings across checkouts.
Validation: strict MkDocs build; fresh public npm installation; all 53 queue-download checks on Windows including six invoices and the process-isolated guide snippet; invoice ZIP and both quickstart snippets; desktop/mobile browser review and actual download-byte checks. The package itself retains all 13 successful release CI jobs and npm signature/provenance evidence. No general throughput, memory-capacity, or native-crash-resolution claim.
Browser CI uses the reachable official Ubuntu archive when the runner supplies it, avoiding the observed stalled Azure mirror while retaining the browser checks.