-
Notifications
You must be signed in to change notification settings - Fork 85
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
build fail #64
Comments
I also have something similar:
I fixed it by reistalling python (deasync dependency) and reinstalling node_modules. |
It seems the deasync depends on lower version Python. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: [email protected]
npm WARN [email protected] requires a peer of react@^15.3.2 but none was installed.
npm ERR! Linux 3.10.0-327.36.1.el7.x86_64
npm ERR! argv "/workstation/bin/node/node-v6.6.0-linux-x64/bin/node" "/workstation/bin/no" "i"
npm ERR! node v6.6.0
npm ERR! npm v3.10.3
npm ERR! code ELIFECYCLE
npm ERR! [email protected] install: node ./build.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script 'node ./build.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the deasync package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node ./build.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs deasync
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls deasync
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
@node-etcd
The text was updated successfully, but these errors were encountered: