Repository navigation
Add a React PDF starter with automatic previews and cleanup - #20
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.
React applications currently have to assemble their own input-to-preview lifecycle around the browser SDK. This adds a complete React/TypeScript starter using the published Fullbleed 0.3.0 package: automatic or on-demand rendering, editable invoice/report templates, previews and PDF downloads.
The reusable hook aborts superseded work, hides stale downloads, ignores obsolete results, and releases workers and Blob URLs on cancellation or unmount. The project supports nested static deployment paths and preserves the existing document designs.
Validation: strict TypeScript/production builds; 35 real-browser checks each in Chrome, Firefox and Playwright WebKit; the same 35 checks in a React development build with StrictMode. Checks cover real PDF text/page sizes, byte equality with the installed Node package, rapid edits, manual mode, cancellation/recovery, unmount/remount, resource cleanup and 1440/390/320px layouts. A dedicated CI workflow retains PDFs, screenshots and lifecycle observations. WebKit is not branded Safari certification; worker counts describe API handles, not native thread exits.
The engine and npm package versions are unchanged. This is an MIT-licensed example, not a new SDK release.