Skip to content
This repository was archived by the owner on Feb 18, 2021. It is now read-only.

Failing to npm install on ubuntu nodejs v0.10.29 (postcss and csso?) #99

Open
arthurzenika opened this issue Jan 6, 2016 · 2 comments

Comments

@arthurzenika
Copy link
Contributor

$ npm install 
npm WARN engine postcss@5.0.14: wanted: {"node":">=0.12"} (current: {"node":"0.10.29","npm":"1.4.21"})

> history@1.13.0 postinstall /home/arthur/local/saltpad/node_modules/history
> node ./npm-scripts/postinstall.js


> react-router@1.0.1 postinstall /home/arthur/local/saltpad/node_modules/react-router
> node ./npm-scripts/postinstall.js

npm WARN optional dep failed, continuing fsevents@1.0.6
npm WARN optional dep failed, continuing fsevents@1.0.6
npm WARN engine csso@1.4.4: wanted: {"node":">=0.12.0"} (current: {"node":"0.10.29","npm":"1.4.21"})
npm ERR! peerinvalid The package react does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer react-dom@0.14.2 wants react@^0.14.2
npm ERR! peerinvalid Peer redbox-react@1.2.0 wants react@>=0.13.2 || ^0.14.0-rc1
npm ERR! peerinvalid Peer react-bootstrap-table@1.2.5 wants react@^0.14.0
npm ERR! peerinvalid Peer react-select@1.0.0-beta6 wants react@^0.14.0
npm ERR! peerinvalid Peer react-addons-linked-state-mixin@0.14.5 wants react@^0.14.5

npm ERR! System Linux 3.19.0-42-generic
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install"
npm ERR! cwd /home/arthur/local/saltpad
npm ERR! node -v v0.10.29
npm ERR! npm -v 1.4.21
npm ERR! code EPEERINVALID
npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR!     /home/arthur/local/saltpad/npm-debug.log
npm ERR! not ok code 0

reading https://futurestud.io/blog/how-to-fix-npm-package-does-not-satisfy-its-siblings-peerdependencies-requirements

does this mean that I need "node":">=0.12" to get saltpad to compile ? Can we get this to work for 0.10* so that debian/ubuntu users can stick to the packaged version of nodejs ?

@Lothiraldan
Copy link
Owner

I reproduce the problem locally, I don't think it's related to node version, but some dependencies may need to be updated.

Lothiraldan pushed a commit that referenced this issue Jan 6, 2016
@Lothiraldan
Copy link
Owner

I just pushed a fix, could you give it a try?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants