Skip to content
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

npm install failed with Node v5.7 #77

Closed
peerasak-u opened this issue Mar 6, 2016 · 5 comments
Closed

npm install failed with Node v5.7 #77

peerasak-u opened this issue Mar 6, 2016 · 5 comments
Assignees

Comments

@peerasak-u
Copy link

I've install Parse Server on Digital Ocean and it's run smoothly but when install parse dashboard I got this error

npm WARN deprecated npmconf@2.1.2: this package has been reintegrated into npm and is now out of date with respect to npm
npm WARN deprecated lodash@1.0.2: lodash@<3.0.0 is no longer maintained. Upgrade to lodash@^4.0.0.
npm WARN deprecated graceful-fs@1.2.3: graceful-fs version 3 and before will fail on newer node releases. Please update to graceful-fs@^4.0.0 as soon as possible.

Server details

Ubuntu 14.04 64bit
NodeJS v. 5.7.1
npm v. 3.6.0
@peterdotjs
Copy link
Contributor

Related to an older version of sass-loader. I'll add a PR to update the version.

@peterdotjs peterdotjs changed the title npm install failed npm install failed with newer version of Node Mar 6, 2016
@peterdotjs
Copy link
Contributor

@clonezer could you pull the latest and test it out?

@peerasak-u
Copy link
Author

Thank you @peterdotjs but I still got error
screen shot 2559-03-07 at 3 17 20 am

@peterdotjs
Copy link
Contributor

@clonezer looking closer there are several node_modules further down their dependency tree which use an older version of graceful-fs. A workaround is to use node version ~4.3 until we figure out how if possible to resolve this.

@peterdotjs peterdotjs changed the title npm install failed with newer version of Node npm install failed with Node v5.7 Mar 7, 2016
@drew-gross drew-gross self-assigned this Mar 15, 2016
@drew-gross
Copy link
Contributor

We've overhauled the installation process. Check the readme for details. That should fix this issue.

douglasmuraoka pushed a commit that referenced this issue Nov 29, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants