-
Notifications
You must be signed in to change notification settings - Fork 380
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
Failed at the [email protected] postinstall script. #652
Comments
Any update on this? Did you get it resolved? |
Nope :| |
The error message states this is a permission issue. There's nothing to be
done in gulp-sass.
Unable to save binary
/Users/nikbelikov/Documents/20th-century/node_modules/node-sass/vendor/darwin-x64-57
: { Error: EACCES: permission denied, mkdir
'/Users/nikbelikov/Documents/20th-century/node_modules/node-sass/vendor'
…On 30 Jan. 2018 5:44 pm, "Nikolay" ***@***.***> wrote:
Nope :|
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#652 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAjZWPuofDQjPVOCluXswQB35tL6meTGks5tPrplgaJpZM4Rs0uV>
.
|
@krayushfk I use this flag
|
@xzyfer: Little help needed here man! |
@nikbelikov: Thanks for the reply but that didn't work as well
|
This is a different issue. Please open an issue with node-sass with the
sass code that produced the default.
The original issue was a permission issue. Not all installation issues are
the same issue.
…On 2 Feb. 2018 5:27 pm, "Ayush Walia" ***@***.***> wrote:
@nikbelikov <https://github.com/nikbelikov>: Thanks for the reply but
that didn't work as well
Binary found at /var/lib/jenkins/jobs/capacity-planner-ui/workspace/tmp/src/github.com/Flipkart/capacity-planner-ui/node_modules/node-sass/vendor/linux-x64-57/binding.node
Testing binary
Segmentation fault
npm ERR! code ELIFECYCLE
npm ERR! errno 139
npm ERR! ***@***.*** postinstall: `node scripts/build.js`
npm ERR! Exit status 139
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#652 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAjZWKRs1N79k6kdkkaSFx-nCBz1Nklrks5tQqq7gaJpZM4Rs0uV>
.
|
getting this: Binary has a problem: [Error: .../node_modules/node-sass/vendor/linux-x64-46/binding.node: ELF file OS ABI invalid] 2018-02-06 17:22:55 gobuilds.Compile : npm ERR! [email protected] postinstall: |
@kodemasta see sass/node-sass#2159 for discussion on this issue |
@nikbelikov In my case, also I had to delete the package-lock.json and work normally. |
npm update node-sass@late will do everything you need. |
I also had to delete the package-lock.json and it's work well. Thanks |
Had the same issue a few seconds ago. Deleting package-lock.json helped me! Thanks a lot, people! |
@nikbelikov Thanks. It works for me! $ sudo npm install node-sass --save-dev --unsafe-perm=true |
@kwoncheol You my man.It works with the following command guys. |
Thanks guys and @akshayseth, removing |
Also: If you're using yarn remove |
Reason: the node-sass folder you downloaded when npm install is empty In 'C:\Users\Administrator\AppData\Roaming\npm-cache\node-sass\4.7.2 In "C:\Users\Administrator\AppData\Roaming\npm-cache\node-sass\4.7.2\ '", there will be a file win32-x64-57_binding , Copy this file under 4.7.2 and then re-install npm install |
Deleting package.json and run again |
@nikbelikov Thank you. |
never run npm command with sudo "to know your username do 'whoami' then do npm install whatever you want to |
Thank-you so much! It solved my problem. |
The text was updated successfully, but these errors were encountered: