chore(react-native): fix nightly

[Coly010]

Current Behavior

The React Native e2e tests contain variable naming conflicts and inconsistent error handling in the process cleanup sections:

• Variables named process shadow the global Node.js process object
• Inconsistent error handling patterns in process cleanup logic
• Some cleanup operations attempt to kill processes that may not exist

Expected Behavior

The React Native e2e tests should have:

• Clear variable names that don't shadow global objects
• Consistent error handling patterns throughout all test cleanup sections
• Robust process cleanup that handles cases where processes may not be running

Changes Made

1. Variable Naming: Renamed process variables to childProcess to avoid shadowing the global Node.js process object
2. Error Handling: Added consistent try-catch blocks around all process cleanup operations
3. Process Cleanup: Simplified cleanup logic by passing undefined for process ID when the process reference is not available, allowing killProcessAndPorts to handle port cleanup appropriately

This fixes issues that could occur in nightly builds where process cleanup wasn't being handled consistently, potentially leading to hanging processes or ports.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Updated (UTC)
nx-dev	Ready	Preview	Aug 26, 2025 6:08pm

[nx-cloud]

View your CI Pipeline Execution ↗ for commit 27bd51f

Command	Status	Duration	Result
nx run e2e-nx:e2e-local	❌ Failed	45m 24s	View ↗
nx run e2e-angular:e2e-local	❌ Failed	47m 33s	View ↗
nx run e2e-next:e2e-local	❌ Failed	40m 50s	View ↗
nx run e2e-workspace-create:e2e-local	❌ Failed	38m 6s	View ↗
nx run e2e-js:e2e-local	❌ Failed	28m 10s	View ↗
nx run e2e-release:e2e-local	❌ Failed	32m	View ↗
nx run e2e-plugin:e2e-local	❌ Failed	17m 38s	View ↗
nx run e2e-rollup:e2e-local	❌ Failed	6m 55s	View ↗
Additional runs (21)	❌ Failed	...	View ↗

---

☁️ Nx Cloud last updated this comment at 2025-08-26 19:33:41 UTC

[FrozenPandaz]

@claude Could you write a PR description for this PR please?

[claude]

Claude finished @FrozenPandaz's task —— View job

---

I'll write a PR description for this React Native nightly fix.

Todo List

• Read the modified file to understand what changes were made
• Analyze the changes and write appropriate PR description
• Format according to the PR template requirements

PR Description

Current Behavior

The React Native e2e tests contain variable naming conflicts and inconsistent error handling in the process cleanup sections:

• Variables named process shadow the global Node.js process object
• Inconsistent error handling patterns in process cleanup logic
• Some cleanup operations attempt to kill processes that may not exist

Expected Behavior

The React Native e2e tests should have:

• Clear variable names that don't shadow global objects
• Consistent error handling patterns throughout all test cleanup sections
• Robust process cleanup that handles cases where processes may not be running

Changes Made

1. Variable Naming: Renamed process variables to childProcess to avoid shadowing the global Node.js process object
2. Error Handling: Added consistent try-catch blocks around all process cleanup operations
3. Process Cleanup: Simplified cleanup logic by passing undefined for process ID when the process reference is not available, allowing killProcessAndPorts to handle port cleanup appropriately

This fixes issues that could occur in nightly builds where process cleanup wasn't being handled consistently, potentially leading to hanging processes or ports.

---

[github-actions]

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.