E:\A Prem World\Team_Work_Tasks\Anjali\Anjali_20160524\QuizApp_20160524_01_Anj>ionic serve -l
(node:4772) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
There is an error in your gulpfile:
Error: Node Sass does not yet support your current environment: Windows 64-bit with false
For more information on which environments are supported please see:
TODO URL
at Object.<anonymous> (E:\A Prem World\Team_Work_Tasks\Anjali\Anjali_20160524\QuizApp_20160524_01_Anj\node_modules\node-sass\lib\index.js:12:11)
at Module._compile (module.js:541:32)
at Object.Module._extensions..js (module.js:550:10)
at Module.load (module.js:456:32)
at tryModuleLoad (module.js:415:12)
at Function.Module._load (module.js:407:3)
at Module.require (module.js:466:17)
at require (internal/module.js:20:19)
at Object.<anonymous> (E:\A Prem World\Team_Work_Tasks\Anjali\Anjali_20160524\QuizApp_20160524_01_Anj\node_modules\gulp-sass\index.js:187:21)
at Module._compile (module.js:541:32)
当前回答
如果你使用NVM, VS Code和VS Code任务资源管理器来运行使用node-sass的npm脚本,下面的警告将为你节省一些时间。
I was using VS Code's Task Explorer to run my scripts and have installed multiple Node versions using NVM, defaulting to the current latest version 16. When I opened my VS Code repository and ran nvm use 10 in a new terminal, the Node and npm version in that terminal window correctly downgrades, but the version of node/npm used by the Task Explorer runner remained at Node 16. So when running my webpack script using the VS Code Task Runner, node-sass would still throw the environment error of this question.
解决方案是不使用VS Code任务运行器,在你改变节点版本的终端上运行你的脚本,或者使用下面的命令改变默认的NVM节点版本,重新启动VS Code,然后使用任务资源管理器/运行器。
NVM别名默认10(或任何你需要node-sass兼容性的版本)
其他回答
以上这些方法对我都没用。我完全删除,然后重新安装,它解决了这个问题。
删除现有的:
npm uninstall --save-dev node-sass
然后重新安装:
npm install --save-dev node-sass
在我的例子中,这与节点版本有关。
我的项目使用的是12.18.3,但我使用的是14.5.0
所以npm rebuild node-sass没有在错误的节点版本(14.5.0)上解决这个问题。
我切换到正确的版本(12.18.3),所以它可以工作。
在我的情况下,问题是当我安装节点的最新版本,即;10.6.0. 同样的错误显示并参考@Quinn卸载该版本并安装8.11.3 LTS版本。现在工作很好:)
下面的堆栈跟踪链接帮助我解决了这个问题。
Module build failed: Error: Node Sass does not yet support your current environment: Windows 64-bit with Unsupported runtime (64)
For more information on which environments are supported please see:
https://github.com/sass/node-sass/releases/tag/v4.7.2
这个链接(https://github.com/sass/node-sass/releases/tag/v4.7.2)清楚地显示了所支持的节点版本。
OS Architecture Node
Windows x86 & x64 0.10, 0.12, 1, 2, 3, 4, 5, 6, 7, 8, 9
... ... ...
将节点版本降级到8.11.1后,再次执行npm install。收到以下信息。
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 Unsupported runtime (64)
This usually happens because your environment has changed since running `npm install`.
Run `npm rebuild node-sass --force` to build the binding for your current environment.
最后,按照指示运行npm rebuild node-sass——force,一切都开始工作了
对于visual studio 2019,需要更改MSBuild路径
npm config set msvs_version 2017
npm config set msbuild_path "C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Current\Bin\MSBuild.exe"
npm rebuild node-sass
推荐文章
- 在Ubuntu上安装Node.js
- Node -使用NODE_MODULE_VERSION 51根据不同的Node.js版本编译
- 禁用包的postinstall脚本
- NodeJS -用NPM安装错误
- 如何为本地安装npm包设置自定义位置?
- 如何用分发文件发布npm包?
- 如何判断一个npm包是全局安装还是本地安装
- NodeJS需要一个全局模块/包
- 在MacOS X上推荐用什么方式安装Node.js、nvm和npm ?
- npm install和npm run build有什么区别?
- npm start和npm run start的区别
- 有没有办法修复包锁。json lockfileVersion所以npm使用特定的格式?
- 如何使用npm全局安装一个模块?
- npm犯错!错误:EPERM:操作不允许,重命名
- Node Sass还不支持当前环境:Linux 64位,带false