New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fsevents @1.2.7 | @1.2.8 does not build with Node 12 #27389 #272
Comments
This will be fixed in #274 (hopefully shortly) |
Just released v1.2.9 which is Node v12 compatible. Prebuilt binaries being built as we speak. |
This is also happening on 2.0.6 @pipobscure should i open a new issue ? |
It is absolutely impossible that thus could happen with 2.0.6 since this is a compile error and you never compile 2.0.6 Are you sure you have the right issue? Can you create a new issue and describe exactly what the problem is? |
How can I install the new version through yarn? It still tries to install 1.2.4 for me? |
@h0jeZvgoxFepBQ2C you can, for example:
Probably there are more ways |
Some of the packages we rely on (onchange -> chokidar -> fsevents for example) rely on fsevents. fsevents prior to 1.2.9 isn't Node 12 compatible. See fsevents/fsevents#272 (comment)
Some of the packages we rely on (onchange -> chokidar -> fsevents for example) rely on fsevents. fsevents prior to 1.2.9 isn't Node 12 compatible. See fsevents/fsevents#272 (comment)
Some of the packages we rely on (onchange -> chokidar -> fsevents for example) rely on fsevents. fsevents prior to 1.2.9 isn't Node 12 compatible. See fsevents/fsevents#272 (comment)
* Upgrade to node-sass@^4.12.0, add Node 12 support See sass/node-sass#2632 (comment) * Ensure to install fsevents 1.2.9 or higher Some of the packages we rely on (onchange -> chokidar -> fsevents for example) rely on fsevents. fsevents prior to 1.2.9 isn't Node 12 compatible. See fsevents/fsevents#272 (comment) * Remove resolution fields, keep yarn.lock changes This ensures we install fsevents@1.2.9, without making fsevents a required dependency. See #1219 (comment)
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
* Upgrade to node-sass@^4.12.0, add Node 12 support See sass/node-sass#2632 (comment) * Ensure to install fsevents 1.2.9 or higher Some of the packages we rely on (onchange -> chokidar -> fsevents for example) rely on fsevents. fsevents prior to 1.2.9 isn't Node 12 compatible. See fsevents/fsevents#272 (comment) * Remove resolution fields, keep yarn.lock changes This ensures we install fsevents@1.2.9, without making fsevents a required dependency. See react-static/react-static#1219 (comment)
To Reproduce:
npm i fsevents@1.2.7
or
npm i fsevents@1.2.8
The text was updated successfully, but these errors were encountered: