chore(demo): take agent-web 0.0.13 so the panel explains CORS failures - #6
Merged
Merged
Conversation
The Vite alias redirects only this library to ../dist; the core resolves from npm. With `^0.0.12` that pins 0.0.12 exactly — caret does not cross the patch digit below 0.1.0 — so the deployed demo, which is where people connect their own MCP server and meet this failure, would keep showing the browser's bare "Failed to fetch" instead of naming the refused header. The published peer range is `>=0.0.12` and already admits 0.0.13, so consumers need nothing and this needs no release. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011FKop4At26QqqkwVGEjJur
siarheidudko
marked this pull request as ready for review
August 16, 2026 20:37
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
2 participants
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.
Why
@dudko.dev/agent-web@0.0.13diagnoses the CORS failure that kills browser MCP clients right after the consent screen — it names the refused header instead of repeating the browser's bareTypeError: Failed to fetch. The demo's MCP panel is exactly where someone meets that failure, and it would not have picked the fix up.The Vite alias redirects only this library to
../dist; the core is resolved from npm. And^0.0.12pins0.0.12exactly — below0.1.0, caret does not cross the patch digit. Verified rather than assumed:So the deployed demo would have kept showing the unhelpful message while the library that fixes it sat published.
What
^0.0.12 → ^0.0.13in the demo's dependencies and this package's devDependencies, with both lockfiles updated (demo/package-lock.jsonnow resolves0.0.13).No release needed for this package. The published
peerDependenciesrange is>=0.0.12, which already admits0.0.13, so nothing changes for consumers — this only affects what the repo and the deployed demo build against.Verification
typecheck,format:check,test(24 pass), demotypecheck, andtest:e2e(4 pass) all green.Generated by Claude Code