Repository navigation
Use process isolation in the Next.js PDF route - #17
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.
Use released Fullbleed 0.2.0 with
isolation: 'process'in the Next.js invoice route. A failed render child returns the existing generic HTTP error while the server can handle the next download. The route keeps its capacity slot until the child exits and IPC disconnects.The standalone verifier now deliberately fails all verified copies of the render-child entrypoint in its temporary artifact, checks the HTTP error and live server, restores those files, and downloads a valid PDF. This covers Next's renamed external-package copy as well as its ordinary traced package. The guide explains host requirements and process startup/memory costs.
Local production build and all 17 standalone checks pass with the published npm package; the invoice PDF and preview remain byte-identical. The npm publication record also retains a fresh public install, worker/process output equality, and child-termination recovery. The native crash investigation in #7 remains open.