Repository navigation
fix: inline exported assets on Node 20 - #167
Open
PromSereyreaksa wants to merge 1 commit into
Open
PromSereyreaksa wants to merge 1 commit into
PromSereyreaksa wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
PromSereyreaksa
force-pushed
the
fix/generation-quality
branch
from
October 14, 2026 19:45
30567fc to
9b55ffc
Compare
This branch was successfully deployed
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.
Follow-up to #164, which merged while its replacement CI run was finishing. The Templates link change is already in main. This keeps the exporter fix portable by reading fetched asset bytes directly from Response.arrayBuffer(), avoiding the jsdom/Node Blob realm mismatch that caused the export-font tests to fail on the Linux Node 20 runner.