Closed gigo6000 closed 1 month ago
You must using node 8.x somewhere in the process, that's what the "57" number stands for.
Yes, we actually use node v8.11.2
not sure where the other version came from. But anyway we fixed it upgrading gulp-sass
to 4.0.0
in case anyone else has this issue.
Our build is failing because of this error:
We have a legacy app on
prod
running this old version and we're in the process of migrating to the latest version ofnode
andAngular
but in the meantime we need to keep this one running.Was this release of node-sassIt looks like the release is there but not the asset binary. Any help is appreciate it. Thank you!v3.13.1
deleted from the repo ?npm -v
): 2.15.11node -v
): v8.11.2node -p process.versions
): { http_parser: '2.8.0', node: '4.9.1', v8: '4.5.103.53', uv: '1.9.1', zlib: '1.2.11', ares: '1.10.1-DEV', icu: '56.1', modules: '46', openssl: '1.0.2o' }node -p process.platform
): linuxnode -p process.arch
): x64node -p "require('node-sass').info"
):node-sass 3.13.1 (Wrapper) [JavaScript] libsass 3.3.6 (Sass Compiler) [C/C++]npm ls node-sass
): └─┬ gulp-sass@2.3.2 └── node-sass@3.13.1