Repository navigation
Use Node 0.1.3 in the Next.js PDF starter - #10
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.
Upgrade the runnable Next.js starter to the published Fullbleed Node 0.1.3 package. Its render promise now waits for worker exit, so the route's capacity slot stays occupied during cleanup after success, failure, timeout, or cancellation. Document that behavior alongside the existing per-process limit.
The production standalone build passes all 15 HTTP/output/recovery checks on Windows with Node 26.10.0. Eight real Chrome checks pass, including pointer and keyboard PDF downloads, the narrow layout, and independent invoice text inspection. The PDF and preview bytes match the existing fixture. The release's engine remains 2.5.6.