Do you want to request a feature or report a bug?
bug
What is the current behavior?
yarn add node-sass
If the current behavior is a bug, please provide the steps to reproduce.
yarn add node-sass
Please mention your node.js, yarn and operating system version.
node v9.3.0
npm v5.6.0
yarn v1.3.2
macOS 10.13.1
I tried npm i node-sass
and work as expecting.
It took a while (mainly because of node-gyp) but works on my machine.
Are you sure that was not a network or compilation time problem?
Versions: node v9.3.0 | npm v5.6.0 | yarn v1.3.2 | macOS 10.13.2
yarn add node-sass
yarn add v1.3.2
[1/4] 🔍 Resolving packages…
[2/4] 🚚 Fetching packages…
[3/4] 🔗 Linking dependencies…
warning " > [email protected]" has unmet peer dependency "vue@^2.1.0".
warning "laravel-elixir-vue-2 > [email protected]" has unmet peer dependency "webpack@^2 || ^2.2.0-rc.0 || ^2.1.0-beta || ^1.12.6".
[4/4] 📃 Building fresh packages…
success Saved lockfile.
success Saved 9 new dependencies.
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
└─ [email protected]
✨ Done in 85.00s.
On some systems, depending on speed and architecture, installing node-sass can take a long time. It may be compiling from source. @lili21 How long did you wait for the command to complete?
morn then ten minutes. It works now. maybe related to node-gyp
and network.
Need more explanations.
this issue still occurs.
Same problem. On each yarn run, node-sass starting rebuild. That takes so much time.
yes, the problem did not occur on npm, yarn rebuild node-sass from scratch
verbose 174.053 Downloading binary from https://github.com/sass/node-sass/releases/download/v4.9.3/darwin-x64-64_binding.node
Cannot download "https://github.com/sass/node-sass/releases/download/v4.9.3/darwin-x64-64_binding.node":
tunneling socket could not be established, cause=getaddrinfo ENOTFOUND host host:80
Hint: If github.com is not accessible in your location
try setting a proxy via HTTP_PROXY, e.g.
export HTTP_PROXY=http://example.com:1234
[1/5] ⡀ fsevents
[-/5] ⡀ waiting...
[3/5] ⡀ node-sass
[-/5] ⡀ waiting...
[-/5] ⡀ waiting...
I had the same problem. I gave it several hours.
Afterwards I tried
npm i node-sass
yarn add node-sass
And only then
yarn install
Now it worked.
It took more than 10 mins for me!
the fuck node-sass
it always ....
...shit when you update, install ...etc !!! (i finished your phrase) this seem to be the same for all :)
So, it's not an error or a bug. I tried this on multiple machines, and worked like a charm on some while took 15-20 minutes on some. Can't do much about this.
Most helpful comment
the fuck node-sass
it always ....