Repository navigation
Add a Next.js PDF starter with standalone verification - #2
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
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 users can render a file, but the package has no runnable web-app starting point. Add a Next.js App Router example that serves the designed Northstar invoice, keeps Fullbleed on the Node server, and traces its worker, WASM, fonts and templates into a standalone deployment artifact.
The route returns private PDF attachments, rejects unknown fixture IDs, bounds active rendering, and recovers after real engine failures. The fictional lookup is explicitly separate from application authentication. The starter includes a checked-in PDF preview, locked dependencies, a production start command and a guide for adapting it.
Local validation on Windows / Node 24.21: production build; 15 isolated standalone HTTP checks; 8 Chrome checks covering native and keyboard downloads, PDF content and narrow layout; separate
npm startcheck. PDF output and the actual preview were visually inspected. Add Linux Node 22/24 and Windows Node 24 CI for the standalone artifact. The example uses the existing released Node 0.1.1 tarball; no engine/API change or new package release.