npm ERR! Failed at the node-sass@3.13.1 postinstall script 'node scripts/build.js'.

Deal with npm is a big headache.
I have npm 3.53 and node 8.0.0-pre
Today I has been fighting with run npm install and I had this error:

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.1.1: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN You are using a pre-release version of node and things may not work as expected
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: iltorb@1.0.13 (node_modules/iltorb):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: iltorb@1.0.13 install: `node-gyp rebuild`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! node-sass@3.13.1 postinstall: `node scripts/build.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the node-sass@3.13.1 postinstall script 'node scripts/build.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/build.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! A complete log of this run can be found in:
npm ERR!     /home/nboettcher/.npm/_logs/2017-03-21T17_22_55_979Z-debug.log

To avoid it just use global mode:

sudo npm install -g npm@3.5.3

Enjoy it!

Comments

  1. P-AMay 15, 2018 at 12:12 PM

    Dont' do this FOLKS, that will break your sh8t.

    It just broke mine, better uninstall/ reinstall node

    Bandit!

    ReplyDelete

Post a Comment

Popular posts from this blog

How to fix Android when developer options are not available for this user

Image
I have an Android One with Oreo version and suddenly my Android rebooted and after that it started to behave strangely: 1) Notification section doesn't work. I can't see notifications from my apps and the arrow and the screw icon to settings access don't work. 2) As I can't access to the notification area, I can't enable Use USB to Transfer Files to access to my phone memory. 3) I can't access to developer mode (I before active it with a lot of taps over Build number). Clicking on developer options just shows developer options are not available to this user. 4) I can't update or install the apps on google play. They freeze on Download pending... message 5) Home and Switch buttons don't work. They light up and vibrate when I tap them but they do nothing. This issue is apparently related to a deconfiguration of user accounts. To fix it, you need re-setup the users. As you can't access to the user manager (you are in guest mode ...
Read more

Contiki 3.0 on XM1000

Image
In other post, I installer contiki 3.x on xm1000. Now, we going to install contiki 3.0 (the lastest version). First, you need to dowload the lastest code from github: git clone https://github.com/contiki-os/contiki.git Now we need to add xm1000 compatibility to our contiki. Thanks to DMI   for the xm1000 patch. Without it, you will see the following error: make: *** No rule to make target 'obj_xm1000/cc2420.o', needed by 'contiki-xm1000.a'.  Stop. I upgrade his patch with an app to access to the xm1000 sensors. Download it from https://drive.google.com/file/d/0B7NXiwmWq7jCb3ROSFZZSWliMnc/view?usp=sharing Now, extract it into contiki folder: tar xzvf xm1000.tar.gz cd xm1000 cp -R * $YOUR_CONTIKI_PATH Go to the apps folder and execute an script that I create to automate the process: cd $YOUR_CONTIKI_PATH/platform/xm1000/apps/sensors ./install.sh Enjoy it!
Read more

How to fix VirtualBox error when you try to import an ova file

If you download an ova file to import it to Virtualbox, maybe you will see the following message: Failed to import appliance filename.ova. Seeking within the archive failed (VERR_TAR_UNEXPECTED_EOS). Result Code: VBOX_E_IPRT_ERROR (0x80BB0005) Component: ApplianceWrap Interface: IAppliance {8398f026-4add-4474-5bc3-2f9f2140b23e} If you do it the same throught VBoxManage you will get: # VBoxManage import filename.ova  Progress state: VBOX_E_IPRT_ERROR VBoxManage: error: Appliance import failed VBoxManage: error: Seeking within the archive failed (VERR_TAR_UNEXPECTED_EOS) VBoxManage: error: Details: code VBOX_E_IPRT_ERROR (0x80bb0005), component ApplianceWrap, interface IAppliance VBoxManage: error: Context: "RTEXITCODE handleImportAppliance(HandlerArg*)" at line 877 of file VBoxManageAppliance.cpp To fix it, you must extract ova content and compress again as follows: tar xvf filename.ova tar cvf newfilename.ova filename.ovf filename.vmdk Also, you can i...
Read more