Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

271
Views
npm install node-sass@3.7.0 genera problemas de análisis de bucle Wrange

Estoy intentando instalar node-sass v3.7.0 ejecutando npm install node-sass@3.7.0 . La instalación parece estar funcionando al principio, y luego recibo este volcado repetidamente:

 2 warnings generated. ./Release/.deps/Release/obj.target/libsass/src/libsass/src/sass_util.odraw Stats { dev: 16777220, mode: 33188, nlink: 1, uid: 502, gid: 20, rdev: 0, blksize: 4096, ino: 30471085, size: 1472, blocks: 8, atimeMs: 1616683090000, mtimeMs: 1616683090000, ctimeMs: 1616683090200.791, birthtimeMs: 1616683090000, atime: 2021-03-25T14:38:10.000Z, mtime: 2021-03-25T14:38:10.000Z, ctime: 2021-03-25T14:38:10.201Z, birthtime: 2021-03-25T14:38:10.000Z } c++ '-DNODE_GYP_MODULE_NAME=libsass' '-DUSING_UV_SHARED=1' '-DUSING_V8_SHARED=1' '-DV8_DEPRECATION_WARNINGS=1' '-D_DARWIN_USE_64_BIT_INODE=1' '-D_LARGEFILE_SOURCE' '-D_FILE_OFFSET_BITS=64' '-DLIBSASS_VERSION="3.3.6"' -I/Users/wvn179/.node-gyp/8.15.0/include/node -I/Users/wvn179/.node-gyp/8.15.0/src -I/Users/wvn179/.node-gyp/8.15.0/deps/openssl/config -I/Users/wvn179/.node-gyp/8.15.0/deps/openssl/openssl/include -I/Users/wvn179/.node-gyp/8.15.0/deps/uv/include -I/Users/wvn179/.node-gyp/8.15.0/deps/zlib -I/Users/wvn179/.node-gyp/8.15.0/deps/v8/include -I../src/libsass/include -Os -gdwarf-2 -mmacosx-version-min=10.7 -arch x86_64 -Wall -Wendif-labels -W -Wno-unused-parameter -std=c++11 -stdlib=libc++ -fno-threadsafe-statics -fno-strict-aliasing -MMD -MF ./Release/.deps/Release/obj.target/libsass/src/libsass/src/sass_values.odraw -c -o Release/obj.target/libsass/src/libsass/src/sass_values.o ../src/libsass/src/sass_values.cpp In file included from ../src/libsass/src/sass_values.cpp:5: In file included from ../src/libsass/src/eval.hpp:4: ../src/libsass/src/ast.hpp:1361:25: warning: loop variable 'numerator' of type 'const std::__1::basic_string<char>' creates a copy from type 'const std::__1::basic_string<char>' [-Wrange-loop-analysis] for (const auto numerator : numerator_units()) ^ ../src/libsass/src/ast.hpp:1361:14: note: use reference type 'const std::__1::basic_string<char> &' to prevent copying for (const auto numerator : numerator_units()) ^~~~~~~~~~~~~~~~~~~~~~ & ../src/libsass/src/ast.hpp:1363:25: warning: loop variable 'denominator' of type 'const std::__1::basic_string<char>' creates a copy from type 'const std::__1::basic_string<char>' [-Wrange-loop-analysis] for (const auto denominator : denominator_units()) ^ ../src/libsass/src/ast.hpp:1363:14: note: use reference type 'const std::__1::basic_string<char> &' to prevent copying for (const auto denominator : denominator_units()) ^~~~~~~~~~~~~~~~~~~~~~~~ &

Recibo este volcado de arriba de forma consecutiva muchas veces. Al final, se devuelve este mensaje:

 + node-sass@3.7.0 added 21 packages from 43 contributors and audited 2105 packages in 121.004s`

Parece que se instaló. Pero cuando trato de usar mi aplicación, obtengo errores de node-sass y npm list -g node-sass indica que el paquete no está instalado. Vuelve:

 npm info it worked if it ends with ok npm info using npm@6.4.1 npm info using node@v8.15.0 /Users/wvn179/.nvm/versions/node/v8.15.0/lib └── (empty)

¿Qué es este problema? ¿Cómo puedo instalar node-sass con éxito?

over 4 years ago · Santiago Trujillo
3 answers
Answer question

0

node-sass está algo obsoleto, le aconsejaría que use sass / sass-loader en su lugar

 npm install sass sass-loader
over 4 years ago · Santiago Trujillo Report

0

node-sass 3.7 es muy antiguo y la última versión de Node que admite es 7 https://github.com/sass/node-sass/releases/tag/v3.7.0 , que también está al final de su vida útil.

over 4 years ago · Santiago Trujillo Report

0

Tuve un problema similar que resolví al degradar el nodo usando el administrador de versiones del nodo.

https://gist.github.com/chranderson/b0a02781c232f170db634b40c97ff455

over 4 years ago · Santiago Trujillo Report
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!