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

Getting lots of errors when trying to install pleeease #77

Open
newjie opened this issue Jul 15, 2016 · 3 comments
Open

Getting lots of errors when trying to install pleeease #77

newjie opened this issue Jul 15, 2016 · 3 comments

Comments

@newjie
Copy link

newjie commented Jul 15, 2016

npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated [email protected]: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN deprecated [email protected]: this package has been reintegrated into npm and is now out of date with respect to npm
npm WARN deprecated [email protected]: cross-spawn no longer requires a build toolchain, use it instead!
npm WARN deprecated [email protected]: lodash@<3.0.0 is no longer maintained. Upgrade to lodash@^4.0.0.
npm WARN deprecated [email protected]: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
/usr/local/bin/pleeease -> /usr/local/lib/node_modules/pleeease-cli/bin/pleeease
/usr/local/bin/pleeease-compile -> /usr/local/lib/node_modules/pleeease-cli/bin/pleeease-compile
/usr/local/bin/pleeease-watch -> /usr/local/lib/node_modules/pleeease-cli/bin/pleeease-watch

[email protected] install /usr/local/lib/node_modules/pleeease-cli/node_modules/node-sass
node scripts/install.js

sh: 1: node: not found
/usr/local/lib
└── (empty)

npm WARN optional Skipping failed optional dependency /pleeease-cli/chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: [email protected]
npm ERR! Linux 4.5.5-x86_64-linode69
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install" "-g" "pleeease-cli"
npm ERR! node v4.2.6
npm ERR! npm v3.5.2
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn

npm ERR! [email protected] install: node scripts/install.js
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the [email protected] install script 'node scripts/install.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 node-sass package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node scripts/install.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs node-sass
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls node-sass
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR! /home/z/public_html/templates/npm-debug.log
npm ERR! code 1

@iamvdo
Copy link
Owner

iamvdo commented Jul 19, 2016

I've released a new version, can you test and give feedback.
Can't reproduce for now...

@jnields
Copy link

jnields commented Jul 19, 2016

I think this is an issue with node-sass, specific to the OS and the version of node.

Would it make more sense for [email protected] to be a peer dependency?

On Jul 19, 2016, at 5:31 AM, Vincent De Oliveira [email protected] wrote:

I've released a new version, can you test and give feedback.
Can't reproduce for now...


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@iamvdo
Copy link
Owner

iamvdo commented Jul 20, 2016

I didn't read well your error, but I found sh: 1: node: not found. Are you sure you have the node executable, not only the nodejs one (as it seems you're on linux) ?

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