Windows 10 This was a fun one for me... In order to resolve it I had to do all of the following.. 1.) Apparently node-sass isn't supported by some of the more recent versions of Node.js so I had to Uninstall Node-v 12.14.1, and delete the nodejs directory in C:/Program Files. 2.) Reinstall a earlier version of Node (for me 10.16.2 worked). NOTE: I had initially downloaded the x86 version so if your System is x64 download the x64 verison... 3.) From here I had to delete my entire project and re-clone it. After this things ran fine.

对我来说，当我运行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.

我也有同样的问题

gulpfile中有一个错误: E:\allapp\badshaindiancuisine\node_module\node-sass\vendor\win32-x64-46\binding.node Node Sass无法找到当前环境的绑定:带有Node.js 4.x的64位Windows 为以下环境找到绑定: - OS X 64位，Node.js 4.x

如何解决这个问题

通过进入项目文件夹，然后执行命令:

npm rebuild node-sass

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函数中看到这个逻辑

我在Linux Mint中做了所有这些:

删除node_modules 运行npm install 运行npm rebuild node-sass

但是它并没有修复这个问题，仍然得到关于node-sass的错误。

我尝试再次运行命令重建node-sass与sudo即sudo npm重建node-sass，它终于工作了!

我已经尝试了所有我能找到的方法。

我注意到那个文件夹有一些奇怪的行为。当我试图从VS终端“cd”到“node_sass”文件夹时，它告诉“文件夹未找到”，但在Finder中看到。

chmod从VS终端找不到文件夹，即使有'sudo'命令。

我已经从本地MacOs终端chmod-ed，刚刚与节点重建。