Repository navigation
Use the published npm package in docs and the Next.js starter - #3
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.
Fullbleed 0.1.1 is now published on npm. Use the registry install command in the README and pin the Next.js starter to the same npm package; the tarball integrity is unchanged from the verified GitHub release.
Retain the registry publication record, including byte equality with the release, all 18 installed files, and a fresh-cache install with an empty npm user configuration. ESM/CommonJS rendering and recovery from a cold timeout produce the previously verified PDF/PNG hashes. The Next.js starter also passes a fresh install, preview render, production build, and all 15 standalone-server checks on Windows / Node 24. CI checks the other supported environments.