Yarn attempts to rebuild fsevents even on incompatible operating systems #2051
Comments
|
Having the same issue... makes the output look like there was an issue when running 'yarn install' and eats some extra seconds. |
|
this problem should be solved with #1997 |
|
Yes, confirmed fixed in latest nightly build: |
|
Doesn't seem to be fixed for linux. |
|
I am getting this error on a windows 7 machine and IT IS blocking me since I can't get any packages to install when it hits. |
|
Still seeing this issue with yarn 1.9.4 on Azure DevOps (formerly VSTS) |
|
Same issue on 1.9.4 with: "resolutions": {
"**/fsevents": ">=1.2.4"
} |
|
It seems that this issue is back. |
|
Update: I am happy to report that, after upgrading from 1.10.1 to 1.12.1, this problem has stopped. We have got the "Already up-to-date" message back, and short install times. Thank you!
My environment: yarn version 1.10.1
My package.json: (I tried but failed to narrow down the minimal deps needed to trigger this problem) |
|
Getting this issue with 1.10.1 too on linux |
|
People getting this problem, you might try upgrading from 1.10.1 to 1.12.1. That has fixed it for us. |
|
Getting this issue with 1.12.3, the install aborts with an error: Used to be a warning and the module used to be ignored. This is with running |
|
Are you sure fsevents is listed as an optional dependency? If it's not
optional, it'll fail on Linux, which is expected.
Sent from my phone.
…On Sun, Dec 30, 2018, 3:12 PM Adam Reis ***@***.*** wrote:
Getting this issue with 1.12.3, the install aborts with an error:
error ***@***.***: The platform "linux" is incompatible with this module.
error Found incompatible module
Used to be a warning and the module used to be ignored.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#2051 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAFnHb-blfOUg-LYdjrhDhh2wdpL6DTQks5u-UhygaJpZM4K9Tb7>
.
|
|
It is a nested optional dependency, but I discovered that the problem was due to the following added lines in This was needed to make it work with Node 10, but apparently manually adding the resolution forces yarn to try and install the package, even if it's an optional dependency. |
|
Also saw this error. Updating node from 6 to 8 fixed it for us. https://travis-ci.org/ember-infinity/ember-infinity/jobs/478166551 |
|
I also encountered this again, we had fsevents in resolutions because of some prior issue, but that wasn't necessary anymore. However, I still think yarn shouldn't fail on an optional package, even if it's specified in the resolutions. Those resolutions should only be used if the package is actually installed (which it shouldn't on linux). |
|
Yarn still got this
I had to use npm force install for this. |
|
But did it worked afterwards? In my case not. |
|
Still seeing it in 1.15.2, this is in a fresh node:8 container |
|
Windows 10 Build 16299 system output: λ yarn install
yarn install v1.17.3
[1/4] Resolving packages...
[2/4] Fetching packages...
info fsevents@1.2.9: The platform "win32" is incompatible with this module.
info "fsevents@1.2.9" is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
[4/4] Building fresh packages...
Done in 61.98s.My package.json: {
"name": "Test",
"version": "0.1.0",
"private": true,
"scripts": {
"serve": "vue-cli-service serve",
"build": "vue-cli-service build",
"lint": "vue-cli-service lint"
},
"dependencies": {
"core-js": "^2.6.5",
"vue": "^2.6.10",
"vue-router": "^3.0.6"
},
"devDependencies": {
"@vue/cli-plugin-babel": "^3.7.0",
"@vue/cli-plugin-eslint": "^3.7.0",
"@vue/cli-service": "^3.7.0",
"@vue/eslint-config-standard": "^4.0.0",
"babel-eslint": "^10.0.1",
"eslint": "^5.16.0",
"eslint-plugin-vue": "^5.0.0",
"tailwindcss": "1.1",
"vue-template-compiler": "^2.6.10"
}
} |
|
Try this
|
Thanks, this worked in my case too. |
Should that^^ stop the incessant, every-time-yarn-execs noise, as well? If not, any hints as to what can/does? |
|
I am still facing this issue with v1.22.4
|
|
I believe it somehow effects my surge deployment process. I'm creating a workflow in github actions but it fails. yarn remove v1.22.4 |
|
@adisher It's just a warning and shouldn't actually break anything. |
What are the side effects of this call? |
heh, it looks like fsevents 2.1.3 has some macOS-specific code in it.
which cannot be built on the linux deployment target. fair enough
% yarn run build
yarns calls this out at build time on heroku, complaining the module
is not compatible with 'linux' platform
Issue is discussed here:
yarnpkg/yarn#2051
for now, i'll just relax on my resolution of 1.x --to--> 2.x upgrade
at the expense of seeing the following warning at yarn install time:
% yarn install
warning react-scripts > webpack-dev-server > chokidar > fsevents@1.2.13:
fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
|
@papadi Well, this is the yarn documentation for
So I assume that somewhere in the install chain there is some script that tries to install fsevents. But turning this off for ever seems a bit more than required. You could just try running |
|
I need to switch to a specific node version and it worked. :) |
And what version of |
It's work !!! |
|
I have executed the
I'm not sure what exactly is the "optional dependency" and what consequences the fact that it's not being installed may have. Should I just ignore it? I have tried to use the option |
|
@ferenczy , Option A) - Simply ignore as it is optional dependency(most of the time) OR Option B) - Switch to other supported OS, if you are comfortable working in non-windows OS enviornment. |
|
For some reason,
This is fixed in yarn v2 #7590 🎉 For those of who are still using yarn v1..... instead of pinning |
|
After 1000+ days, the saga still continues.. |
|
BTW, as far as I recall, @locofocos |
Do you want to request a feature or report a bug?
Bug
What is the current behavior?
fseventsis only relevant on Mac OS, it does not compile on Linux or Windows. Yarn appears to try and compile it even on incompatible operating system. This is a waste of time as it's always going to fail.If the current behavior is a bug, please provide the steps to reproduce.
This is the
package.jsonfrom one of my sites:{ "name": "sitename", "version": "0.0.0", "description": "", "main": "index.js", "devDependencies": { "assets-webpack-plugin": "~3.0.0", "babel-core": "~5.8.25", "babel-loader": "~5.3.2", "exports-loader": "~0.6.2", "expose-loader": "~0.7.0", "imports-loader": "~0.6.4", "webpack": "~1.12.2" }, "repository": { "type": "git", "url": "daniel@host.dan.cx:/var/local/git/sitename" }, "author": "Daniel Lo Nigro <daniel@dan.cx> (http://dan.cx/)", "scripts": { "build-dev": "NODE_ENV=development webpack -d", "build-prod": "NODE_ENV=production webpack -p", "watch": "NODE_ENV=development webpack --progress --colors --watch -d", "update-babel-helpers": "babel-external-helpers -l get,inherits,create-class,class-call-check,extends,interop-require-default > ./public/assets/js/babel-external-helpers.js" }, "dependencies": { "array.prototype.find": "~1.0.0", "babel-runtime": "~5.8.25", "classnames": "^2.1.5", "fbemitter": "^2.0.0", "flux": "~2.1.1", "react": "~0.14.0", "react-onclickoutside": "git://github.com/Daniel15/react-onclickoutside.git" } }Running
yarngives me this as part of the output:However, in the "Building fresh packages..." stage of installation, it still attempts to build the dependency, which obviously fails as it should only be built on Mac OS.
The installation still succeeds so this is not a blocker, it's just very odd behaviour.
The second time I run
yarn, it shows that everything is up-to-date:However, when I add another dependency, it tries to build fsevents again.
What is the expected behavior?
Yarn should not attempt to build a native dependency if it's incompatible with the current OS
npm handles this correctly:
Please mention your node.js, yarn and operating system version.
Yarn 0.17.8
Windows 10
Node.js 6.9.1
The text was updated successfully, but these errors were encountered: