Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#3,310 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
54/100
Tipo de issue
Refactorización
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
aws, node.js, typescript
Área
cloud, devtools

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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).

Lenguaje dominante
TypeScript
Estrellas
4.9k
Forks
328
Merge medio
11 h 49 min
PR fusionados (30 d)
585

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de callstack/agent-device

Todos los issues de callstack/agent-device

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.