fix: change private field from string to boolean in react-devtools-fusebox package.json

[everettbu]

Mirror of facebook/react#35862
Original author: darshjme-codes

---

Fixes #35793

Problem

The package.json has a malformed private field using a string value instead of a boolean:

"private": "true"  // ❌ Wrong (string)

This violates the npm package.json specification which requires the private field to be a boolean.

Impact

This causes failures in package scanning and validation tools:

• ❌ ScanCode.io pipeline failures when scanning pkg:github/facebook/react@v19.2.1
• ❌ Type validation error: '"true" value must be either True or False.'
• ❌ Non-compliance with npm specification

Related upstream issues:

• aboutcode-org/scancode.io#1986 - Pipeline failure report
• aboutcode-org/scancode-toolkit#4631 - Root cause analysis
• aboutcode-org/scancode-toolkit#4635 - Defensive workaround

While downstream tools are adding workarounds, the source data should comply with the npm specification.

Solution

Change the private field to a boolean value:

{
  "name": "react-devtools-fusebox",
  "version": "0.0.0",
- "private": "true",
+ "private": true,
  "license": "MIT",
}

Testing

• ✅ Package metadata now validates correctly in ScanCode and other scanning tools
• ✅ Compliant with npm specification
• ✅ No functional impact (string "true" and boolean true behave identically in npm, but tools rely on correct typing)

---

Note: Issue reporter (@prashantsingh1819) offered to submit a PR but hasn't yet, so I'm submitting this fix to resolve the scanning failures.

[greptile-apps]

Greptile Summary

Fixes the private field in packages/react-devtools-fusebox/package.json from a string value ("true") to the correct boolean value (true), bringing it into compliance with the npm package.json specification. While npm itself treats both identically, downstream tooling (e.g., ScanCode) enforces strict type validation and fails on the string variant.

• Minimal, single-line change with no functional impact on npm behavior
• Note: two other files in the repo have the same issue — compiler/packages/react-forgive/server/package.json and compiler/packages/react-forgive/client/package.json — and could benefit from the same fix in a follow-up

Confidence Score: 5/5

• This PR is safe to merge — it is a trivial, one-character type correction in a package.json file with zero functional impact.
• The change is a single-line fix correcting a JSON value type from string to boolean. It has no effect on runtime behavior, build processes, or dependencies. The fix is clearly correct per the npm specification.
• No files require special attention.

Important Files Changed

Filename	Overview
packages/react-devtools-fusebox/package.json	Corrects the private field from string "true" to boolean true, complying with the npm package.json specification. No issues found.

_{Last reviewed commit: ef77a63}

[greptile-apps]

_{1 file reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}

[everettbu]

Upstream PR was closed or merged. Code is synced via branch mirror.