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

Support Windows hosts

Aperta
  • Qualcosa non va?
#247 0 commenti 1 reazione 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
15/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
android, node.js, react-native, typescript
Ambito
devtools, testing

Direzione di ricerca

Start with the linked open issues #183, #191, #222, #216, #218, #219, #225, and #217; each describes a Windows-specific failure to investigate. Work spans the CLI, Jest runner, device lock, and Android, Vega, and Web platforms. Done means those platforms run end to end on Windows 11, the pinned Jest preset resolves, path, lock, and process handling work like POSIX, and the unit suite passes on Windows CI.

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

Descrizione

enhancement

Harness runs on macOS and Linux today. This issue tracks the work to make Harness run on Windows hosts: the CLI, the Jest runner, the device lock, and the Android, Vega, and Web platforms.

Each linked issue reports a Windows-specific failure, or one that was observed on a Windows host. Closed items are already fixed and are listed for reference.

Open

  • #183: Windows Android SDK path not found
  • #191: Android platform fails on Windows hosts (the umbrella for Android; #183 and #201 are its first two failures)
  • #222: On Windows, Jest cannot find the react-native-harness preset
  • #216: On a Windows host, a test's file name reaches the device with backslashes
  • #218: On Windows, the device lock fails while another run deletes a lock file
  • #219: platform-vega's Metro enhancer test fails on Windows
  • #225: The pre-push hook builds the same packages twice at once (two tsc --build runs collide on Windows)
  • #217: Timeout diagnostics lose the promise a hung test awaits once it is garbage-collected (flaked on Windows CI)
  • #259: On Windows, sdkmanager.bat and avdmanager.bat fail on any argument
  • #260: A user's ANDROID_AVD_HOME is overwritten with ~/.android/avd
  • #261: platform-ios's crash diagnostics test fails on Windows because it expects forward slashes

Closed

  • #201: Android runner can't start on a Windows host: SDK binaries are looked up without .exe or .bat
  • #232: The iOS package's tests never run (Windows also failed to load two files that resolve package.json through import.meta.url)

Done when

  • The Android, Vega, and Web platforms run end to end on a Windows 11 host.
  • The Jest preset resolves on Windows with the Jest version the CLI pins.
  • Path, lock, and process handling behave the same on Windows and POSIX.
  • The unit test suite passes on a Windows CI job.
Lingua principale
TypeScript
Stelle
333
Fork
20
Merge medio
14h
PR unite (30g)
30

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 callstackincubator/react-native-harness

Tutte le issue di callstackincubator/react-native-harness

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.