chore: patching solution and updating react-native-community v17 to v17.0.1

[tommasini]

Description

Changelog

CHANGELOG entry:

Related issues

Fixes:

Manual testing steps

Feature: my feature name

  Scenario: user [verb for user action]
    Given [describe expected initial app state]

    When user [verb for user action]
    Then [describe expected outcome]

Screenshots/Recordings

Before

After

Pre-merge author checklist

• I’ve followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• I’ve included tests if applicable
• I’ve documented my code using JSDoc format if applicable
• I’ve applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

---

Note

Pins and patches @react-native-community/cli-server-api to 15.0.1 with URL validation in openURLMiddleware, updating configs and lockfile accordingly.

• Tooling:
  • Patched RN CLI Server API: Adds Yarn patch @react-native-community/[email protected] modifying build/openURLMiddleware.js to:
    • Parse url and validate protocol (http/https) and format; return 400 on invalid inputs.
    • Minor string/formatting tweaks and multi-line middleware chaining.
• Dependencies:
  • Pin @react-native-community/cli-server-api from ^17.0.0 to patched 15.0.1 in dependencies and resolutions; adjust transitive dependencies in yarn.lock.
• Config:
  • Update .yarnrc.yml advisory note and normalize npmPreapprovedPackages entries.

^{Written by Cursor Bugbot for commit 707506d. This will update automatically on new commits. Configure here.}

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[cursor]

Bug: JSON Parse Outside Try-Catch Causes Crash

The JSON.parse(req.rawBody) call on line 32 is outside the try-catch block that starts on line 37. If req.rawBody contains invalid JSON, it will throw an unhandled exception that crashes the middleware instead of returning a proper 400 error response. The try-catch only catches errors from new URL(url), not from JSON parsing.

 

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud