"yarn add node-sass" takes long time to finished or never finshed

[Brew-Brew]

Bug description

Command

yarn add node-sass

What is the current behavior?

What is the expected behavior?

Steps to Reproduce

1. yarn add node-sass
2. "yarn add node-sass" takes long time or never finshed with message "building fresh packages node-sass"

Environment

• Node Version: v12.16.1
• Yarn v1 Version: 1.22.4
• OS and version: mac 10.15.2

[saper]

I could not reproduce this with my FreeBSD 11.3 amd64 system, using node v13.10.1

Using the following compiler:

> clang -v
FreeBSD clang version 8.0.1 (tags/RELEASE_801/final 366581) (based on LLVM 8.0.1)
Target: x86_64-unknown-freebsd11.3
Thread model: posix
InstalledDir: /usr/bin

Here is a full output. Yarn was installed from FreeBSD binary packages.

radziecki> yarn init
yarn init v1.22.4
question name (testproject): 
question version (1.0.0): 
question description: 
question entry point (index.js): 
question repository url: 
question author: 
question license (MIT): 
question private: 
success Saved package.json
Done in 4.82s.
radziecki> ls -al
total 237
drwxr-xr-x   2 saper    staff           3 maj 17 23:25 .
drwxr-xr-x 292 saper    staff         891 maj 17 23:24 ..
-rw-r--r--   1 saper    staff          92 maj 17 23:25 package.json
radziecki> yarn add node-sass
yarn add v1.22.4
info No lockfile found.
[1/4] Resolving packages...
warning node-sass > request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
warning node-sass > node-gyp > request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
success Saved lockfile.
success Saved 156 new dependencies.
info Direct dependencies
└─ node-sass@4.14.1
info All dependencies
├─ abbrev@1.1.1
├─ ajv@6.12.2
├─ amdefine@1.0.1
├─ ansi-styles@2.2.1
├─ aproba@1.2.0
├─ are-we-there-yet@1.1.5
├─ array-find-index@1.0.2
├─ asn1@0.2.4
├─ async-foreach@0.1.3
├─ asynckit@0.4.0
├─ aws-sign2@0.7.0
├─ aws4@1.9.1
├─ balanced-match@1.0.0
├─ bcrypt-pbkdf@1.0.2
├─ block-stream@0.0.9
├─ brace-expansion@1.1.11
├─ camelcase-keys@2.1.0
├─ camelcase@2.1.1
├─ caseless@0.12.0
├─ chalk@1.1.3
├─ cliui@5.0.0
├─ code-point-at@1.1.0
├─ color-convert@1.9.3
├─ color-name@1.1.3
├─ combined-stream@1.0.8
├─ concat-map@0.0.1
├─ console-control-strings@1.1.0
├─ core-util-is@1.0.2
├─ cross-spawn@3.0.1
├─ currently-unhandled@0.4.1
├─ dashdash@1.14.1
├─ decamelize@1.2.0
├─ delayed-stream@1.0.0
├─ delegates@1.0.0
├─ ecc-jsbn@0.1.2
├─ emoji-regex@7.0.3
├─ error-ex@1.3.2
├─ escape-string-regexp@1.0.5
├─ extend@3.0.2
├─ extsprintf@1.3.0
├─ fast-deep-equal@3.1.1
├─ fast-json-stable-stringify@2.1.0
├─ find-up@1.1.2
├─ forever-agent@0.6.1
├─ form-data@2.3.3
├─ fs.realpath@1.0.0
├─ fstream@1.0.12
├─ gauge@2.7.4
├─ gaze@1.1.3
├─ get-caller-file@2.0.5
├─ getpass@0.1.7
├─ glob@7.1.6
├─ globule@1.3.1
├─ har-schema@2.0.0
├─ har-validator@5.1.3
├─ has-ansi@2.0.0
├─ has-unicode@2.0.1
├─ hosted-git-info@2.8.8
├─ http-signature@1.2.0
├─ in-publish@2.0.1
├─ indent-string@2.1.0
├─ inflight@1.0.6
├─ is-arrayish@0.2.1
├─ is-finite@1.1.0
├─ is-typedarray@1.0.0
├─ is-utf8@0.2.1
├─ isarray@1.0.0
├─ isexe@2.0.0
├─ isstream@0.1.2
├─ js-base64@2.5.2
├─ json-schema-traverse@0.4.1
├─ json-schema@0.2.3
├─ json-stringify-safe@5.0.1
├─ jsprim@1.4.1
├─ load-json-file@1.1.0
├─ locate-path@3.0.0
├─ lodash@4.17.15
├─ loud-rejection@1.6.0
├─ lru-cache@4.1.5
├─ map-obj@1.0.1
├─ meow@3.7.0
├─ mime-db@1.44.0
├─ mime-types@2.1.27
├─ minimatch@3.0.4
├─ minimist@1.2.5
├─ mkdirp@0.5.5
├─ nan@2.14.1
├─ node-gyp@3.8.0
├─ node-sass@4.14.1
├─ nopt@3.0.6
├─ normalize-package-data@2.5.0
├─ npmlog@4.1.2
├─ number-is-nan@1.0.1
├─ oauth-sign@0.9.0
├─ object-assign@4.1.1
├─ os-homedir@1.0.2
├─ os-tmpdir@1.0.2
├─ osenv@0.1.5
├─ p-limit@2.3.0
├─ p-locate@3.0.0
├─ p-try@2.2.0
├─ parse-json@2.2.0
├─ path-exists@2.1.0
├─ path-is-absolute@1.0.1
├─ path-parse@1.0.6
├─ path-type@1.1.0
├─ performance-now@2.1.0
├─ pinkie@2.0.4
├─ process-nextick-args@2.0.1
├─ pseudomap@1.0.2
├─ psl@1.8.0
├─ punycode@2.1.1
├─ qs@6.5.2
├─ read-pkg-up@1.0.1
├─ read-pkg@1.1.0
├─ readable-stream@2.3.7
├─ redent@1.0.0
├─ repeating@2.0.1
├─ request@2.88.2
├─ require-directory@2.1.1
├─ require-main-filename@2.0.0
├─ resolve@1.17.0
├─ safe-buffer@5.1.2
├─ safer-buffer@2.1.2
├─ sass-graph@2.2.5
├─ scss-tokenizer@0.2.3
├─ semver@5.3.0
├─ set-blocking@2.0.0
├─ source-map@0.4.4
├─ spdx-correct@3.1.0
├─ spdx-exceptions@2.3.0
├─ sshpk@1.16.1
├─ stdout-stream@1.4.1
├─ string_decoder@1.1.1
├─ strip-bom@2.0.0
├─ strip-indent@1.0.1
├─ supports-color@2.0.0
├─ tar@2.2.2
├─ tough-cookie@2.5.0
├─ trim-newlines@1.0.0
├─ true-case-path@1.0.3
├─ tunnel-agent@0.6.0
├─ tweetnacl@0.14.5
├─ uri-js@4.2.2
├─ util-deprecate@1.0.2
├─ uuid@3.4.0
├─ validate-npm-package-license@3.0.4
├─ verror@1.10.0
├─ which-module@2.0.0
├─ which@1.3.1
├─ wide-align@1.1.3
├─ wrap-ansi@5.1.0
├─ y18n@4.0.0
├─ yallist@2.1.2
├─ yargs-parser@13.1.2
└─ yargs@13.3.2
Done in 33.74s.
radziecki> ./node_modules/.bin/node-sass -v
node-sass	4.14.1	(Wrapper)	[JavaScript]
libsass  	3.5.5	(Sass Compiler)	[C/C++]

[Brew-Brew]

I think it was temporary issue.. It doesn't occur again. so, i will close this issue.

[Messhias]

@Brew-Brew it's not temporally issue, still happening. Please reopen it and take a better look at it.

Thank you.

[merceyz]

It's an external issue, nothing we can do about it.

node-sass is a native dependency and takes a while to build on your system, replace it with sass to avoid having to build node-sass, it's also deprecated and should be replaced anyways.

Warning: LibSass and Node Sass are deprecated. While they will continue to receive maintenance releases indefinitely, there are no plans to add additional features or compatibility with any new CSS or Sass features. Projects that still use it should move onto Dart Sass.
https://github.com/sass/node-sass/blob/0648b5a59df693686e745d3690fc73e768200c47/README.md#node-sass

[Messhias]

@merceyz and all which still having this issue, the only way I found now to fix this annoying issue is removing completely node-sass from my computer and installing the sass only (and you could work with latest version without issue).

You just have to beware to not use features which doesn't match with your CRA (on our case it's a ReactJS application).

Let's hope in the future the library has totally removed and replaced by sass.

Thank you.