Closed omichelsen closed 8 years ago
@omichelsen The problem appears to be from those logs specifically caused by the NPM package node-sass
. I have had similar issues, when trying to harp or harp-dependent applications, including on windows(alexgleason/harp-gui#22).
Some support may be available at github.com/sass/node-sass/blob/master/TROUBLESHOOTING.md, though if you continue to have these errors, try seeing if node-sass on its own will work.
If node-sass wont work when you try installing and running it, then you may well wish to raise an issue here.
Thanks for the suggestions, but npm install -g node-sass
works fine. It's only when installing Harp things go awry.
@sintaxi may well need a look at this, then
@isaacrg Experiencing @omichelsen's error as well! Thanks
@omichelsen If you're using homebrew, switching global node version back to v4.2.2 allowed me to install harp correctly
Harp support is tied pretty closly with node-sass. I suspect when node-sass works on npm 3/node 5 harp will get bumped too. For the time being go back to node 4 and re-install. Hopefully you are using nvm
and that is an easy task.
@silentrob Considering node-sass
installs just fine I don't see how it can be the issue.
Harp might not be using the latest node-sass version, which could be the difference.
On Fri, 6 Nov 2015 00:11 Robert Clancy (Robbo) notifications@github.com wrote:
@silentrob https://github.com/silentrob Considering node-sass installs just fine I don't see how it can be the issue.
— Reply to this email directly or view it on GitHub https://github.com/sintaxi/harp/issues/510#issuecomment-154240087.
I can confirm that heroku is running Node V5.0.0, and when I tried loading an app dependent on the latest version of harp on (0.19.0), node-sass wouldn't install. Log at: http://pastebin.com/hDByf4yQ
This will be fixed in the next release of Harp. If you need to get around it in the meantime, I’ve updated Terraform, Harp’s preprocessing engine, with the latest release of Node-sass. So, you can install that manually in the meantime if you’d like. In your project directory, you can run:
npm install --save-dev harp terraform@0.13.1
Or use npm shinkwrap
and set your own versions. We’ll have a new release out soon with this updated properly, though. Thanks for your patience! #502
Thanks!
On Fri, 6 Nov 2015 23:03 Kenneth Ormandy notifications@github.com wrote:
This will be fixed in the next release of Harp. If you need to get around it in the meantime, I’ve updated Terraform, Harp’s preprocessing engine, with the latest release of Node-sass. So, you can install that manually in the meantime if you’d like. In your project directory, you can run:
npm install --save-dev harp terraform@0.13.1
Or use npm shinkwrap https://docs.npmjs.com/cli/shrinkwrap and set your own versions. We’ll have a new release out soon with this updated properly, though. Thanks for your patience! #502 https://github.com/sintaxi/harp/pull/502
— Reply to this email directly or view it on GitHub https://github.com/sintaxi/harp/issues/510#issuecomment-154570463.
Yup, broken here too. C++ errors arise during the build, reflecting the major native API changes, most of them being breaking ones.
Harp should be updated to reflect these changes too, imho. :)
@fustkilas Try ./node_modules/.bin/harp
I ended up using https://github.com/tj/n and node 4.0.0, awaiting latest harp.
Deleted all node and npm traces from my system, reinstalled Node/npm 6.5.0/3.10.3 with Homebrew, then npm install -g harp@next
Works perfectly!
Here I did not have to uninstall node/npm, only installed using harp@next
My harp installation stopped working after upgrade to Node 5 with the following message:
The
rebuild
command did nothing, so I tried reinstalling Harp, which led to this epic fail:No variation of
sudo
or simliar will make it work. It's obviously caused by something innode-sass
(again), but do you have any insights into an upcoming fix?