Make single-file reports truly self-contained#3354
Merged
Merged
Conversation
vdvukhzhilov
approved these changes
May 22, 2026
pratushnyi
approved these changes
May 22, 2026
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.
Context
This fixes single-file report generation so it no longer creates extra files next to index.html when plugins include static assets. Reports generated with --single-file now embed plugin CSS assets directly into the HTML, matching the expectation that the report can be shared, archived, or opened as one file.
For example, when the custom logo plugin is enabled, its logo image is now included inside the generated index.html instead of being written as a separate plugin/custom-logo/custom-logo.svg file. This makes single-file reports easier to move between machines and less likely to break when only the HTML file is copied.
Checklist