Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Summary: This yarn.lock file was regenerated by deleting the existing yarn.lock file and rerunning `yarn install`. The current `yarn.lock` file is fairly out of date and is affecting the CI servers. More specifically, fsevents@1.2.7, [referenced in yarn.lock here](https://github.com/facebook/react-native/blob/46be292f671c70aac4ecc178c96e3a2a6a3d16da/yarn.lock#L3215), [fails to compile](fsevents/fsevents#272) on node 12 or later. This causes the [yarn install step on CI to error](https://app.circleci.com/pipelines/github/facebook/react-native/7065/workflows/de2bebff-33a5-4d2e-bc73-f7f380641452/jobs/176266/parallel-runs/0/steps/0-104). This PR is being made as 1 step in getting [the RNTester detox tests running again](#30312). We can alternatively manually update the `yarn.lock` file with [the minimum needed fsevent changes](https://github.com/facebook/react-native/compare/master...MLH-Fellowship:update-yarn-lock-fsevents?expand=1#diff-51e4f558fae534656963876761c95b83b6ef5da5103c4adef6768219ed76c2deL3215-L3221) if this PR changes too much. ## Changelog <!-- Help reviewers and the release process by writing your own changelog entry. For an example, see: https://github.com/facebook/react-native/wiki/Changelog --> [Internal] [Changed] - Bump fsevents from 1.2.7 to 1.2.13. Pull Request resolved: #30361 Test Plan: Verify yarn install step on CI is fixed. Reviewed By: hramos Differential Revision: D24910611 Pulled By: cpojer fbshipit-source-id: 45a2f25a14d368d2f464e489924b1a2befbdf784
- Loading branch information