Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

refactor(provider-webdriver): ship AWS Device Farm as the `@agent-device/aws-device-farm` plugin

Aperta
  • Qualcosa non va?
#3,310 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
54/100
Tipo di issue
Refactoring
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
aws, node.js, typescript
Ambito
cloud, devtools

Direzione di ricerca

Start with the existing AWS Device Farm provider and connection files in packages/provider-webdriver, plus the TestMu plugin package as the packaging template; this work is blocked on #3312 and the BrowserStack extraction. Move the named AWS files and tests into packages/provider-aws-device-farm, expose the host command runner through the plugin SDK, and update core, help, docs, and README as specified. Run the named provider-scenario tests and pnpm check:affected --run; completion also requires the plugin checker and live-session verification or a documented blocker.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

needs-triage refactor

Purpose and evidence

0.22 stops bundling hosted device providers with the default installation. AWS Device Farm already presents the plugin factory shape inside core (packages/provider-webdriver/src/aws-device-farm-provider.ts plus aws-device-farm-connection.ts, PR #3312). The one capability it needs that ProviderPluginHost does not expose is a host-command runner: the provider drives aws devicefarm ... through runHostCommand, which core currently supplies in src/provider-webdriver.ts.

Required behavior and boundary

  • Extend the experimental plugin SDK: ProviderPluginHost gains runHostCommand(command, args): Promise<{ stdout }> backed by runCmd with the bounds core uses today (10 MiB buffer, 30 s). Keep the SDK declaration small; the packed declaration-size guard from #3121 stays green.
  • New workspace package packages/provider-aws-device-farm publishing @agent-device/aws-device-farm, built and released like TestMu. The default export returns { webDriver, connection }; the manifest declares provider: "aws-device-farm" and the connection capabilities from CLOUD_WEBDRIVER_PROVIDER_DECLARATIONS (no credentialVariables: the AWS CLI credential chain has no environment fingerprint, and the fingerprint tests pin that).
  • Move aws-device-farm.ts, aws-device-farm-artifacts.ts, aws-device-farm-provider.ts, aws-device-farm-connection.ts, aws-device-farm-connection-verification.ts and their tests out of provider-webdriver. The requires --aws-project-arn <arn> or AWS_DEVICE_FARM_PROJECT_ARN messages and the flag-then-AGENT_DEVICE_*-then-AWS_* selector order stay as they are.
  • Core drops aws-device-farm from BUNDLED_CLOUD_WEBDRIVER_PROVIDERS and RESERVED_PLUGIN_PROVIDERS; connectionProviderCapabilities and the requiresAppAttachment reconnect hint in connection-presentation.ts keep working from the manifest.
  • Help, website/docs/docs/aws-device-farm.md, device-clouds.md, plugins.md, and the README move the provider to the plugin install flow.
agent-device plugins add @agent-device/aws-device-farm
agent-device connect aws-device-farm --platform android --aws-project-arn <arn> --aws-device-arn <arn> --aws-app-arn <arn>

Completion and validation

  • node scripts/check-provider-plugin.mjs packages/provider-aws-device-farm passes with a fixture aws on PATH.
  • The AWS provider-scenario tests (cloud-webdriver-provider-adapters, cloud-webdriver-provider-regressions, stale-provider-runtime-admission) build the runtime from the plugin factory with the fake host command.
  • pnpm check:affected --run passes; Size report shows the default install shrinking.
  • One live Device Farm remote-access session with the packed plugin, recorded in the PR, or the exact blocker named.

Dependencies and readiness

Blocked by: #3312 landing on main; do the BrowserStack extraction first so the packaging template is proven twice before the SDK change here.

Effort: M. Risk: medium (SDK surface grows by one method; AWS live verification needs an account).

Lingua principale
TypeScript
Stelle
4.9k
Fork
328
Merge medio
11h 51m
PR unite (30g)
535

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di callstack/agent-device

Tutte le issue di callstack/agent-device

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.