Skip to content

fix(deps): peer @browser-ai/* v3, which is the pair for ai v7 - #5

Merged
siarheidudko merged 1 commit into
mainfrom
claude/mcp-remote-http-oauth-ges1mj
Aug 16, 2026
Merged

fix(deps): peer @browser-ai/* v3, which is the pair for ai v7#5
siarheidudko merged 1 commit into
mainfrom
claude/mcp-remote-http-oauth-ges1mj

Conversation

@siarheidudko

Copy link
Copy Markdown
Member

Why

0.0.9 depends on ai@^7.0.66 but still declares @browser-ai/core and @browser-ai/web-llm as ^2.0.0 peers — and @browser-ai/web-llm@2.x peers ai@^6. The two cannot both be satisfied, so installing this package alongside the local WebLLM path fails outright:

Found: @browser-ai/web-llm@2.1.7
  peerOptional @browser-ai/web-llm@"^2.0.0" from @dudko.dev/agent-web@0.0.9
Conflicting peer dependency: ai@7.0.66
  peer ai@"^7.0.0" from @browser-ai/web-llm@3.0.2

Found while pointing the sibling demo (dudko-dev/agent-web-react#3) at the freshly published 0.0.9.

What

Peer ranges move to ^3.0.0, the line that peers ai@^7 — which is what this codebase has actually tracked since the AI SDK v7 bump, and what its own devDependencies already install. No source changes; typecheck, format:check, build, test (89 passing) are green.

Version bumped to 0.0.10 so the release workflow publishes it — it skips any version already on npm.


Generated by Claude Code

The package depends on ai ^7.0.66 but still asked for @browser-ai/*
^2.0.0, and @browser-ai/web-llm v2 peers ai ^6 — so anyone installing
this package together with the local WebLLM path got an unsatisfiable
peer set and npm refused to resolve it (found while wiring the demo to
0.0.9). v3 is the line that peers ai ^7, which is what the code has
tracked since the AI SDK v7 bump.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011FKop4At26QqqkwVGEjJur
@siarheidudko
siarheidudko merged commit 67389ee into main Aug 16, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants