feat(provider-testmu): publish @agent-device/testmu on plugin contract v2
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- nodejs, typescript
Research direction
Start in packages/provider-testmu, where the v1 agentDevicePlugin declaration lives, and add the ./agent-device export beside it without removing the v1 entry. The work depends on #3755 and feeds agent-device/host from #3757, so check those first. Done when agent-device plugins add @agent-device/testmu works on 0.21.28 and on the new loader, a JS host can import testmu and pass testmu({ credentials }), and a changeset exists.
Written by the indexing model from the issue text.
Description
Part of #3747. Blocked by #3755.
Move packages/provider-testmu to the v2 factory (testmu(options)). Credentials come from options, with the existing environment variables as fallback.
Transition
- Keep it loadable by 0.21.x hosts without v2. Retain the v1
agentDevicePlugindeclaration and its entry alongside the new./agent-deviceexport. - Hosts with v2 prefer the export.
- Drop the v1 entry in #3759.
Done when
agent-device plugins add @agent-device/testmuworks on 0.21.28 and on the new loader.- A JS host can
import testmu from '@agent-device/testmu'and passtestmu({ credentials })toagent-device/host(#3757). - There's a changeset for
@agent-device/testmu.
- Dominant language
- TypeScript
- Stars
- 5k
- Forks
- 334
- Avg merge
- 12h 2m
- Merged PRs (30d)
- 678
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from callstack/agent-device
-
`devices` reports a phantom Android emulator named after the emulator's crashdata INFO bannerPossibly taken @airowe claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
callstack/agent-device#3716 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
callstack/agent-device#1869 ·
Maintainers usually reply within 1 day
-
backlog refactor
Difficulty 5/5 Over a week Newbie friendliness 8/100
callstack/agent-device#3759 ·
Maintainers usually reply within 1 day
-
backlog enhancement needs-triage
Difficulty 5/5 Over a week Newbie friendliness 8/100
callstack/agent-device#3758 ·
Maintainers usually reply within 1 day
-
enhancement ready-for-agent
Difficulty 5/5 Over a week Newbie friendliness 15/100
callstack/agent-device#3757 ·
Maintainers usually reply within 1 day
All issues in callstack/agent-device
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
anomalyco/opencode#56380 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
BUG | `MCP 服务器` | 全局层行的停用/启用与删除报 404 server row not found，编辑保存会在 profile 层复制出重复行Possibly taken @w6242652 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Chocobozzz/PeerTube#7832 ·
Maintainers usually reply within 3 days
-
Pay to use?Open
Difficulty 1/5 Under an hour Newbie friendliness 66/100
darkreader/darkreader#16108 · 1 comment ·
Maintainers usually reply within 2 days