Repository navigation
0.1.3: browser checks don't wait for photos from other sites - #3
Merged
Merged
Conversation
Remote images get a blank stand-in. A slow image host held each page's load for up to 30 seconds per color scheme, which pushed TagKit's browser checks past their 5-minute limit. 0.1.3. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
TagKit's two
--browsertests have timed out at 5 minutes since its gallery and nonprofit starter added picsum.photos photos (they took 6–11 s before).--browserwaits for the page'sloadevent, which waits for every image, so a slow image host holds each page up to 30 s in each color scheme.http:/https:) are answered with a 1×1 blank GIF. Contrast reads background colors and overflow reads layout, and an<img>withwidth/heightkeeps its size, so neither check changes.With this file dropped into TagKit's
node_modules, its two browser tests pass in 6 s. Tests here: 31 passed.After merging:
cd ~/github/tagstack/tagcheck && git checkout main && git pull && npm test && npm publish, then TagKit moves to^0.1.3.🤖 Generated with Claude Code