我有问题构建一个应用程序，因为node-sass不断失败的错误。
binding /Users/warren/Sites/random-docs/my-cms/node_modules/node-sass/vendor/darwin-x64-11/binding.node出错 Node Sass无法找到当前环境的绑定:OS X 64位的Node 0.10.x
我试过跑步
npm rebuild node-sass
说
二进制很好;退出。
当运行node -v时，我得到v6.2.2
这与sass错误说的“Node 0.10.x”不同。我不明白为什么它会得到错误的版本。我也尝试删除node_modules文件夹并运行npm update或npm install，这两者都没有解决问题。什么好主意吗?
当前回答
node-sass runs an install script to download the required binary. If there are no environment variables, .npmrc variables or process arguments set then the binary is determined by using the current process platform, architecture and Node ABI version. Therefore, if you run node install in one application and then try to run node-sass in an application with a different platform/architecture/ABI, the binary won't have been downloaded. The solution is to manually download the binary or to fix the binary version using an environment variable (SASS_BINARY_NAME) or a .npmrc variable (sass_binary_name)
你可以在node-sass\lib\extensions.js中的getBinaryPath函数中看到这个逻辑
其他回答
对于Visual Studio 2015/2017，右键单击您的包。单击“还原包”。
这将确保Visual Studio工具外部工具中的npm运行，并且绑定将基于此重新构建。
这通常是因为运行npm install后环境发生了变化。 运行npm rebuild node-sass为当前环境构建绑定。
对我来说，当我运行npm安装时，它审计了已安装的包，并显示“发现1个高严重漏洞”，并通过运行
npm audit fix
成功了。如果能帮助到别人就发布。
更新:共享错误日志:
ERROR in ./src/styles.scss (./node_modules/@angular-devkit/build-angular/src/angular-cli-files/plugins/raw-css-loader.js!./node_modules/postcss-loader/src??embedded!./node_modules/sass-loader/lib/loader.js??ref--14-3!./src/styles.scss)
Module build failed (from ./node_modules/sass-loader/lib/loader.js):
Error: Missing binding ..\node_modules\node-sass\vendor\win32-x64-57\binding.node
Node Sass could not find a binding for your current environment: Windows 64-bit with Node.js 8.x
Found bindings for the following environments:
- Windows 64-bit with Node.js 10.x
This usually happens because your environment has changed since running `npm install`.
....
它确实要求我这么做
Run `npm rebuild node-sass` to download the binding for your current environment.
我只是运行npm rebuild而不是npm rebuild node-sass，问题就消失了。但我不知道背后的魔力是什么。
如果你在mac上安装Xcode。
