fix: change private field from string to boolean#582
Open
everettbu wants to merge 1 commit into
Open
Conversation
According to npm specification, private field must be boolean not string.
Greptile SummaryFixes the
Confidence Score: 5/5
Important Files Changed
Last reviewed commit: 94b1253 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Mirror of facebook/react#35863
Original author: pickmemory
Summary
This PR fixes the malformed
privatefield inpackages/react-devtools-fusebox/package.json.Bug
The
privatefield was set to string"true"instead of booleantrue, which causes failures in package scanning tools that validate package metadata.Fix
Changed
"private": "true"to"private": trueRelated