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

node-sass stops install #556

Closed
dcsan opened this issue Apr 18, 2016 · 40 comments
Closed

node-sass stops install #556

dcsan opened this issue Apr 18, 2016 · 40 comments

Comments

@dcsan
Copy link

dcsan commented Apr 18, 2016

have a new DO droplet and installed nvm
node 5.9.1

installer failed as follows

npm install -g harp
npm WARN deprecated graceful-fs@3.0.8: graceful-fs version 3 and before will fail on newer node releases. Please update to graceful-fs@^4.0.0 as soon as possible.
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.
/root/.nvm/v5.9.1/bin/harp -> /root/.nvm/v5.9.1/lib/node_modules/harp/bin/harp

> node-sass@3.4.2 install /root/.nvm/v5.9.1/lib/node_modules/harp/node_modules/node-sass
> node scripts/install.js

sh: 1: node: Permission denied
/root/.nvm/v5.9.1/lib
└── (empty)

npm ERR! Linux 3.13.0-37-generic
npm ERR! argv "/root/.nvm/v5.9.1/bin/node" "/root/.nvm/v5.9.1/bin/npm" "install" "-g" "harp"
npm ERR! node v5.9.1
npm ERR! npm  v3.7.3
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn

npm ERR! node-sass@3.4.2 install: `node scripts/install.js`
npm ERR! spawn ENOENT
npm ERR! 
npm ERR! Failed at the node-sass@3.4.2 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!     /root/www/rikai.co/npm-debug.log
npm ERR! code 1

$ harp
No command 'harp' found, did you mean:

@swartzrock
Copy link

Seeing the same error trying to install on OS X El Capitan with the latest NPM from Homebrew:

npm ERR! Darwin 15.4.0
npm ERR! argv "/usr/local/Cellar/node/6.0.0/bin/node" "/usr/local/bin/npm" "install" "-g" "harp"
npm ERR! node v6.0.0
npm ERR! npm v3.8.6
npm ERR! code ELIFECYCLE
npm ERR! node-sass@3.4.2 postinstall: node scripts/build.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the node-sass@3.4.2 postinstall script 'node scripts/build.js'.

@fakenickels
Copy link

The same here

gyp WARN download NVM_NODEJS_ORG_MIRROR is deprecated and will be removed in node-gyp v4, please use NODEJS_ORG_MIRROR                      [49/2853]
gyp verb build type Release
gyp verb architecture x64
gyp verb node dev dir /home/gabriel/.node-gyp/6.1.0
gyp verb `which` succeeded for `make` /usr/bin/make
gyp info spawn make
gyp info spawn args [ 'V=1', 'BUILDTYPE=Release', '-C', 'build' ]
make: Entering directory '/home/gabriel/.nvm/versions/node/v6.1.0/lib/node_modules/harp/node_modules/node-sass/build'
  g++ '-DNODE_GYP_MODULE_NAME=binding' '-D_LARGEFILE_SOURCE' '-D_FILE_OFFSET_BITS=64' '-DBUILDING_NODE_EXTENSION' -I/home/gabriel/.node-gyp/6.1.0/inc
lude/node -I/home/gabriel/.node-gyp/6.1.0/src -I/home/gabriel/.node-gyp/6.1.0/deps/uv/include -I/home/gabriel/.node-gyp/6.1.0/deps/v8/include -I../..
/nan  -fPIC -pthread -Wall -Wextra -Wno-unused-parameter -m64 -O3 -fno-omit-frame-pointer -fno-rtti -fno-exceptions -std=gnu++0x -std=c++0x -MMD -MF 
./Release/.deps/Release/obj.target/binding/src/binding.o.d.raw   -c -o Release/obj.target/binding/src/binding.o ../src/binding.cpp
In file included from ../src/binding.cpp:3:0:
../src/sass_context_wrapper.h:8:26: fatal error: sass/context.h: No such file or directory
compilation terminated.
binding.target.mk:103: recipe for target 'Release/obj.target/binding/src/binding.o' failed
make: *** [Release/obj.target/binding/src/binding.o] Error 1
make: Leaving directory '/home/gabriel/.nvm/versions/node/v6.1.0/lib/node_modules/harp/node_modules/node-sass/build'
gyp ERR! build error 
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/home/gabriel/.nvm/versions/node/v6.1.0/lib/node_modules/harp/node_modules/node-gyp/lib/build.js:276:23)
gyp ERR! stack     at emitTwo (events.js:106:13)
gyp ERR! stack     at ChildProcess.emit (events.js:191:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:204:12)
gyp ERR! System Linux 4.4.0-21-generic
gyp ERR! command "/home/gabriel/.nvm/versions/node/v6.1.0/bin/node" "/home/gabriel/.nvm/versions/node/v6.1.0/lib/node_modules/harp/node_modules/node-
gyp/bin/node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
gyp ERR! cwd /home/gabriel/.nvm/versions/node/v6.1.0/lib/node_modules/harp/node_modules/node-sass
gyp ERR! node -v v6.1.0
gyp ERR! node-gyp -v v3.3.1
gyp ERR! not ok 
Build failed
/home/gabriel/.nvm/versions/node/v6.1.0/lib
└── (empty)

@fakenickels
Copy link

As I tested here, it worked just great in node 5.4.1 and npm 3.8.6

@timkinnane
Copy link

+1. node v6.1.0, npm v3.8.9. Guess I'll downgrade npm for now, as per @grsabreu's comment.

@timkinnane
Copy link

timkinnane commented May 9, 2016

Tried with both npm v3.8.7 and v3.8.6 and got the same error. Also tried with and without node-sass pre-installed globally. Finally got it going again by going back to node 5 (v5.11.1) and npm v3.8.6.

@xzyfer
Copy link

xzyfer commented May 11, 2016

There are multiple issue here, all of which have been covered many times on the node-sass tracker.

@dcsan npm scripts won't run lifecycle scripts as root. You need to add the --unsafe-perm

npm install --unsafe-perm

@swartzrock @grsabreu node-sass added Node 6 support in v3.7.0. The version you're using, v3.4.2, is very old and no long supported. Use that latest node-sass and you'll be fine.

xzyfer added a commit to xzyfer/terraform that referenced this issue May 11, 2016

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
The current locked version, v3.4.2, is very old and no longer supported. 
It also does not support Node 6. 
This causing many people issues including harp users.

sintaxi/harp#556
@xzyfer
Copy link

xzyfer commented May 11, 2016

I have PR terraform, which harp uses, to update node-sass - sintaxi/terraform#130

@kozie
Copy link

kozie commented May 19, 2016

So, the fix has been merged into the master branch of Terraform but no new releases of both Terraform and HarpJS have been published yet.
Will there be a release to fix the Node 6.x issues or do we have to wait for a bigger update with the new changes?

no hard feelings.. i do like what you are doing and love HarpJS but i'm regretting i still haven't downgraded my NodeJS. I simply didn't do that because i didn't expect the fix to take this long.

Thanks in advance

@sintaxi
Copy link
Owner

sintaxi commented May 19, 2016

Ok I tagged and released Terraform v1.1.0 but Im getting failing tests when its merged into harp. Can any one take a look for me? I have things in branch https://github.com/sintaxi/harp/tree/v0.21.0-pre

@kozie
Copy link

kozie commented May 19, 2016

Ok, thanks for the quick actions. I'll try and take a look asap.

On Thu, May 19, 2016, 1:22 PM Brock Whitten notifications@github.com
wrote:

Ok I tagged and released Terraform v1.1.0 but Im getting failing tests
when its merged into harp. Can any one take a look for me? I have things in
branch https://github.com/sintaxi/harp/tree/v0.21.0-pre


You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#556 (comment)

@xzyfer
Copy link

xzyfer commented May 19, 2016

@sintaxi is there a travis ci build I can see the failure on?

@jvandemo
Copy link
Collaborator

@sintaxi — I have v0.21.0-pre running locally and tests (npm test) run fine:

90 passing (9s)

What errors are you seeing?

I don't see any Travis integration so I'm assuming you run tests locally.

Thanks!

@xzyfer
Copy link

xzyfer commented May 19, 2016

It looks like a lot has change between terraform v0.13.2 and v1.1.0. The node-sass change may be unrelated to the failures you're seeing.

@MortalCatalyst
Copy link

MortalCatalyst commented May 29, 2016

its node-sass 467 that has been open years causing this, current unable to install, is there a way to use sass from rubygems to get around the node-sass issues sass/node-sass#467

`npm ERR! Linux 4.4.9-300.fc23.x86_64
npm ERR! argv "/home/sayth/n/bin/node" "/home/sayth/n/bin/npm" "install" "-g" "harp"
npm ERR! node v6.2.0
npm ERR! npm v3.8.9
npm ERR! code ELIFECYCLE

npm ERR! node-sass@3.4.2 postinstall: node scripts/build.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the node-sass@3.4.2 postinstall script 'node scripts/build.js`

@MortalCatalyst
Copy link

I can get a compile if I use 4.4.5 only at the moment

@negritosuave
Copy link

negritosuave commented Jun 3, 2016

Having this same issue. npm v3.9.3 and node v6.2.1 (and node-sass 3.7.0) with zsh. Recently updated node but everything was fine before. I could install and update packages so I figured it must be Harp. Came looking and found this. I was really looking forward to trying/using Harp. Hoping for a fix soon.

Edited.

@stonecauldron
Copy link

Have the same problem on npm v3.9.3 and node v6.2.1 on a fresh os installation.

In my case the error seems to come from the fact that the release of node-sass is not found on github:

Cannot download "https://github.com/sass/node-sass/releases/download/v3.4.2/linux-x64-48_binding.node":

HTTP error 404 Not Found

The url used does not point to any release in the node-sass git repo.

@xzyfer
Copy link

xzyfer commented Jun 3, 2016

You need at least node-sass@3.7.0 for Node 6 support.
On 3 Jun 2016 11:35 PM, "stonecauldron" notifications@github.com wrote:

Have the same problem on npm v3.9.3 and node v6.2.1 on a fresh os
installation.

In my case the error seems to come from the fact that the release of
node-sass is not found on github:

Cannot download "https://github.com/sass/node-sass/releases/download/v3.4.2/linux-x64-48_binding.node":

HTTP error 404 Not Found

The url used does not point to any release in the node-sass git repo.


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#556 (comment), or mute
the thread
https://github.com/notifications/unsubscribe/AAjZWBmCTN7zqlXZo2nT3wF-cDRxRgwJks5qIC2XgaJpZM4IJcVF
.

@negritosuave
Copy link

Yes I read that before. I updated node-sass before I tried to install Harp. Still the same issue.

@DTrejo
Copy link

DTrejo commented Jun 4, 2016

Skip to the end of this comment if it's too long for you.

@sintaxi I just ran tests for the branch you pushed, v0.21.0-pre. I hope I didn't go overboard here.
@jvandemo you can see some errors:

It's true, I am running an old OSX, so maybe you should ignore me.

PS Thank you all for harp, I ❤️ it :)


PPS Another bug I just had, when ran this branch (despite the tests failing):
image After searching, I find this bug in clean-css, which has a similar error message, but is fixed in 3.4.13 of clean-css. clean-css/clean-css#774.

~/Dropbox/dev/forks/harp(v0.21.0-pre)§ npm ls clean-css
harp@0.21.0 /Users/dtrejo/Dropbox/dev/forks/harp
└─┬ terraform@1.1.0
  └─┬ jade@1.11.0
    └── clean-css@3.4.16

So there must be something else going on here, not sure what it is yet. This error may stem from nodejs/node#5348, because harp hasn't been run on node 6 very much, it's possible some module is passing in an empty string somewhere. Maybe.

Update: looks like the error is in stylus, found it by running /node_modules/harp/node_modules/stylus/bin/stylus public/stylesheets/index.styl with this branch of harp npm linked in.

path.js:7
    throw new TypeError('Path must be a string. Received ' + inspect(path));
    ^

TypeError: Path must be a string. Received undefined
    at assertPath (path.js:7:11)
    at extname (path.js:1433:5)
    at createPath (/Users/dtrejo/Dropbox/dev/forks/harp/node_modules/stylus/bin/stylus:693:29)
    at writeFile (/Users/dtrejo/Dropbox/dev/forks/harp/node_modules/stylus/bin/stylus:706:14)
    at Array.<anonymous> (/Users/dtrejo/Dropbox/dev/forks/harp/node_modules/stylus/bin/stylus:665:13)
    at Renderer.render (/Users/dtrejo/Dropbox/dev/forks/harp/node_modules/stylus/lib/renderer.js:114:27)
    at /Users/dtrejo/Dropbox/dev/forks/harp/node_modules/stylus/bin/stylus:656:15
    at tryToString (fs.js:449:3)
    at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:436:12)

Fixed the error by adding this to stylus (diff is against https://github.com/stylus/stylus/blob/0.53.0/bin/stylus#L692, which is what this branch uses):

diff --git 1/./node_modules/harp/node_modules/stylus/bin/stylus 2/stylus.js
old mode 100755
new mode 100644
index d3b946b..aa05383
--- 1/./node_modules/harp/node_modules/stylus/bin/stylus
+++ 2/stylus.js
@@ -689,7 +689,6 @@ function compileFile(file) {
  */

 function createPath(file, sourceMap) {
-  dest = dest || '.';
   var out;
   if (files.length === 1 && extname(dest) === '.css') {
     return [dest, sourceMap ? '.map' : ''].join('');
@@ -808,4 +807,4 @@ function importFiles(style) {
   imports.forEach(function(file) {
     style.import(file);
   });
-}
+}
\ No newline at end of file

Update: it looks like this is fixed in the latest version of stylus, 0.54.5. So we will need to update terraform to use this version of stylus.

TLDR; the only two updates that matter:

Update: I opened a PR on terraform to fix an old version of stylus that had typeerrors caused by passing empty strings to path.resolve: sintaxi/terraform#131. I guess terraform will need a new release, and also it will need to be updated in harp's package.json.

Update: it looks like the two failing tests are caused by harp compiling the .json files with variables into html files. See output2.txt in https://gist.github.com/DTrejo/965ce5c714f498cde446e696276ba79d#file-output2-txt for the stack traces. Annoyingly, I had to add run tests with npm test -- -g basic in order to get mocha to print the stack traces. I'm not going to try and fix these. Screenshot:

image

Update: it looks like harp's minification is also having problems. This stems from harp-minify's use of uglify-js. It seems like it is overzealous with removing global functions that aren't referenced in the same file.

PPPS Wow does it suck to update software. I'm so glad I don't have anything in production that I needed to migrate to node 6.

@negritosuave
Copy link

I really want to try harp and I use homebrew (as well as zsh). So I looked up a different version with brew and downgraded to node 5. Harp installed and everything appears to be working. Guess I'll stick with node 5 until whatever is going on has been resolved.

Glad that it works at least. I may downgrade to LTS just to be safe but that's down the line. Good luck!

@arxpoetica
Copy link

Bump. This really needs to be fixed.

@dcsan
Copy link
Author

dcsan commented Aug 1, 2016

someone on our team made a hackaround script to overwrite terraform. fragile but it seemed to work

Oh, and one more thing - you can probably use terraform Git repo directly without saving it locally (but this will slow down later reinstalls and can possibly break in the future)

#!/bin/sh
sudo npm uninstall --global harp
mkdir ~/fixes
cd ~/fixes
git clone git@github.com:sintaxi/harp.git
git clone git@github.com:sintaxi/terraform.git
cd terraform
npm install
cd ../harp
npm uninstall --save terraform
npm install --save ~/fixes/terraform
cd ..
sudo npm install --global ~/fixes/harp

@gringolalia
Copy link

I downgraded to node version 4.0.0 with nvm and nvm use and then harp installed just fine, and my harp init harpo command initiated the project.

Just that now harp server harpo throws an error ... address in use, probably just need to reboot ...

@teonik
Copy link

teonik commented Oct 26, 2016

Installing using node v7.0.0 and npm v4.0.0 fails when compiling node-sass.I followed dcsan's procedure and it works great.I also replaced node-sass version to the latest (3.10.1 at the time of writing) in terraform's package.json and no problems so far.

@dcsan
Copy link
Author

dcsan commented Oct 26, 2016

I was looking for an SSG for another project and then had all the flashbacks of fighting of this issue... is there any resolution in sight? otherwise unfortunately cannot really use harpjs.

@CrisLi
Copy link

CrisLi commented Mar 28, 2017

Is there any way to disable sass feature since we only need the markdown feature?

I mean not install node-sass dependence and start up harp server without sass support.

@dcsan
Copy link
Author

dcsan commented Mar 28, 2017

I guess one option might be to have a docker image for harp you could run as a container... seems a shame that a SSG tool is "rendered" haha unusable by a CSS lib 😱

@DTrejo
Copy link

DTrejo commented Mar 28, 2017

Another idea: make a version of terraform which only loads compilers/sass/etc for the languages that harp sees in the filesystem (meaning if you don't use sass, it won't load sass).

  • Problem: if you add a new file, it needs to require the compiler for it
  • Problem: not a good idea to require while running

Idea: Maybe moving to a js version of sass will solve all these problems https://github.com/medialize/sass.js

  • Problem: slower; meant to be used in browser.

@sintaxi
Copy link
Owner

sintaxi commented Mar 29, 2017

@DTrejo totally Im on board with switching to that lib or just not shipping with sass built in. Do you happen to know how mature sass.js is?

@DTrejo
Copy link

DTrejo commented Mar 29, 2017

I don't know, but here are some screenshots which may help you make a decision:

image

image

image
electron-compilers: 60 releases, 20 dependants; qwebs 141 releases, 10 dependants

image

image

image

image

Hmm... seems pretty well used

@arxpoetica
Copy link

@paulirish has one commit, so... 😆

@pickworth
Copy link

facing the same issue as OP on ubuntu 16.10, node 7.7.4 via nvm, latest node-sass still gets the permission denied problem. The same build works fine on Windows build agent, just not Linux

@dylan-baskind
Copy link

Would love to see this resolved - its brought our marketing site deployment to a grinding halt :( - and we're not using SASS anyhow.

@DTrejo
Copy link

DTrejo commented Apr 4, 2017 via email

@strpipe
Copy link

strpipe commented May 9, 2017

Oh this is a shame. I ran into this right now. Hope this will be resolved :3

@AdamBrodzinski
Copy link

Still broke. @dcsan 's fix worked like a charm though! 🍻

Node - v9.6.1
npm - v5.6.0

@topsailcashew-zz
Copy link

It's 2019 and still no fix for this? I'm running Ubuntu 16.04, Node v10.15, npm v6.7.0. Node sass still stops my installation.

root@bryantnate://# npm install -g harp
npm WARN deprecated connect@2.30.2: connect 2.x series is deprecated
npm WARN deprecated graceful-fs@3.0.11: please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js
npm WARN deprecated coffee-script@1.12.7: CoffeeScript on NPM has moved to "coffeescript" (no hyphen)
npm WARN deprecated browserslist@2.11.3: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
npm WARN deprecated classifier@0.1.0: Package no longer supported. Contact support@npmjs.com for more info.
/usr/local/lib/nodejs/node-v10.15.0/bin/harp -> /usr/local/lib/nodejs/node-v10.15.0/lib/node_modules/harp/bin/harp

> node-sass@4.9.3 install /usr/local/lib/nodejs/node-v10.15.0/lib/node_modules/harp/node_modules/node-sass
> node scripts/install.js

Unable to save binary /usr/local/lib/nodejs/node-v10.15.0/lib/node_modules/harp/node_modules/node-sass/vendor/linux-x64-64 : { Error: EACCES: permission denied, mkdir '/usr/local/lib/nodejs/node-v10.15.0/lib/node_modules/harp/node_modules/node-sass/vendor'
    at Object.mkdirSync (fs.js:753:3)
    at sync (/usr/local/lib/nodejs/node-v10.15.0/lib/node_modules/harp/node_modules/mkdirp/index.js:71:13)
    at Function.sync (/usr/local/lib/nodejs/node-v10.15.0/lib/node_modules/harp/node_modules/mkdirp/index.js:77:24)
    at checkAndDownloadBinary (/usr/local/lib/nodejs/node-v10.15.0/lib/node_modules/harp/node_modules/node-sass/scripts/install.js:114:11)
    at Object.<anonymous> (/usr/local/lib/nodejs/node-v10.15.0/lib/node_modules/harp/node_modules/node-sass/scripts/install.js:157:1)
    at Module._compile (internal/modules/cjs/loader.js:689:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
    at Module.load (internal/modules/cjs/loader.js:599:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
    at Function.Module._load (internal/modules/cjs/loader.js:530:3)
  errno: -13,
  syscall: 'mkdir',
  code: 'EACCES',
  path:
   '/usr/local/lib/nodejs/node-v10.15.0/lib/node_modules/harp/node_modules/node-sass/vendor' }

> node-sass@4.9.3 postinstall /usr/local/lib/nodejs/node-v10.15.0/lib/node_modules/harp/node_modules/node-sass
> node scripts/build.js

Building: /usr/local/lib/nodejs/node-v10.15.0/bin/node /usr/local/lib/nodejs/node-v10.15.0/lib/node_modules/harp/node_modules/node-gyp/bin/node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library=
gyp info it worked if it ends with ok
gyp verb cli [ '/usr/local/lib/nodejs/node-v10.15.0/bin/node',
gyp verb cli   '/usr/local/lib/nodejs/node-v10.15.0/lib/node_modules/harp/node_modules/node-gyp/bin/node-gyp.js',
gyp verb cli   'rebuild',
gyp verb cli   '--verbose',
gyp verb cli   '--libsass_ext=',
gyp verb cli   '--libsass_cflags=',
gyp verb cli   '--libsass_ldflags=',
gyp verb cli   '--libsass_library=' ]
gyp info using node-gyp@3.8.0
gyp info using node@10.15.0 | linux | x64
gyp verb command rebuild []
gyp verb command clean []
gyp verb clean removing "build" directory
gyp verb command configure []
gyp verb check python checking for Python executable "python2" in the PATH
gyp verb `which` succeeded python2 /usr/bin/python2
gyp verb check python version `/usr/bin/python2 -c "import sys; print "2.7.12
gyp verb check python version .%s.%s" % sys.version_info[:3];"` returned: %j
gyp verb get node dir no --target version specified, falling back to host node version: 10.15.0
gyp verb command install [ '10.15.0' ]
gyp verb install input version string "10.15.0"
gyp verb install installing version: 10.15.0
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp WARN EACCES user "root" does not have permission to access the dev dir "/root/.node-gyp/10.15.0"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/usr/local/lib/nodejs/node-v10.15.0/lib/node_modules/harp/node_modules/node-sass/.node-gyp"
gyp verb tmpdir == cwd automatically will remove dev files after to save disk space
gyp verb command install [ '--node_gyp_internal_noretry', '10.15.0' ]
gyp verb install input version string "10.15.0"
gyp verb install installing version: 10.15.0
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version not already installed, continuing with install 10.15.0
gyp verb ensuring nodedir is created /usr/local/lib/nodejs/node-v10.15.0/lib/node_modules/harp/node_modules/node-sass/.node-gyp/10.15.0
gyp WARN install got an error, rolling back install
gyp verb command remove [ '10.15.0' ]
gyp verb remove using node-gyp dir: /usr/local/lib/nodejs/node-v10.15.0/lib/node_modules/harp/node_modules/node-sass/.node-gyp
gyp verb remove removing target version: 10.15.0
gyp verb remove removing development files for version: 10.15.0
gyp WARN install got an error, rolling back install
gyp verb command remove [ '10.15.0' ]
gyp verb remove using node-gyp dir: /usr/local/lib/nodejs/node-v10.15.0/lib/node_modules/harp/node_modules/node-sass/.node-gyp
gyp verb remove removing target version: 10.15.0
gyp verb remove removing development files for version: 10.15.0
gyp ERR! configure error 
gyp ERR! stack Error: EACCES: permission denied, mkdir '/usr/local/lib/nodejs/node-v10.15.0/lib/node_modules/harp/node_modules/node-sass/.node-gyp'
gyp ERR! System Linux 4.15.0-43-generic
gyp ERR! command "/usr/local/lib/nodejs/node-v10.15.0/bin/node" "/usr/local/lib/nodejs/node-v10.15.0/lib/node_modules/harp/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
gyp ERR! cwd /usr/local/lib/nodejs/node-v10.15.0/lib/node_modules/harp/node_modules/node-sass
gyp ERR! node -v v10.15.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok 
Build failed with error code: 1
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.7 (node_modules/harp/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.7: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! node-sass@4.9.3 postinstall: `node scripts/build.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the node-sass@4.9.3 postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2019-01-28T08_25_17_201Z-debug.log

It's been bugging me for weeks now. All the solution from node-sass didn't work for me.

@topsailcashew-zz
Copy link

Tried the solution by @dcsan , but I couldn't clone the github repos...

root@bryantnate:~/fixes# git clone git@github.com:sintaxi/harp.git
Cloning into 'harp'...
Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
root@bryantnate:~/fixes# git clone git@github.com:sintaxi/terraform.git
Cloning into 'terraform'...
Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

@sintaxi
Copy link
Owner

sintaxi commented Oct 25, 2019

Fixed.

@sintaxi sintaxi closed this as completed Oct 25, 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