Repository navigation
Ship readable standalone Visualize vendor modules - #6
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.
Visualize currently ships oversized vendor bundles and a minified axe program, including a second minified program embedded inside Puppeteer. This changes their packaging to readable local modules while preserving the helper entrypoints and top-level library versions.
The maintained change is limited to a pinned maintainer build, generated parser/Puppeteer/axe modules, an inline axe module loader, notices, and package verification. The inline loader preserves artifacts with inline-only CSP. Users still run the installed skill without npm installation; Node and Chrome requirements stay the same. Culori, jq, hooks, publishing helpers, skill instructions, and the Claude plugin source pin are unchanged.
Most of the diff is regenerated third-party source. The largest generated file is 190,939 bytes; the skill contains 283 files. This addresses the Visualize code-readability/size concerns; it does not claim scanner approval or removal of the remaining jq binary warnings.
Validation:
npm cirebuild in a different directory produces byte-identical output hashes.Focused injection timing: approximately 95ms versus 48ms before (10 alternating samples), about 47ms extra setup for browser checks. Hooks are unchanged. No directory scanner was available to rerun.
Need help on this PR? Tag
@codesmith-botwith what you need.