Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Support Windows hosts

Open
  • Is something wrong?
#247 1 comment 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
android, node.js, react-native, typescript
Domain
devtools, testing

Research direction

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.

Written by the indexing model from the issue text.

Description

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.
Dominant language
TypeScript
Stars
335
Forks
23
Avg merge
1d 8h
Merged PRs (30d)
54

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from callstackincubator/react-native-harness

All issues in callstackincubator/react-native-harness

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.