Repository navigation
Verify npm 0.1.4 on Windows and update the Next.js starter - #13
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.
Update the Next.js starter to the publicly verified
fullbleed@0.1.4package (engine 2.5.7) and retain the npm publication record. Its HTTP invoice now matches the 40,289-byte release fixture; the preview pixels are unchanged. Other dependency versions and platform selectors stay pinned.The public Windows check exposed a locale-decoding failure when the font verifier read UTF-8 JSON containing supplementary-plane math text. Read and write verification JSON as UTF-8 explicitly, and run the real installed-package font check in the Windows / Node 22 CI job with Python UTF-8 mode disabled. This affects development verification only; it does not change the npm runtime or claim a fix for issue #7.
Validation: fresh GitHub and npm installations match all 18 package files and the release tarball integrity. ESM/CommonJS, timeout recovery, quickstart extraction, and all seven independent font comparisons pass. The production Next.js build passes all 15 isolated standalone HTTP checks; its PDF matches the npm fixture and its preview is byte-identical to the prior version.