- html - 出于某种原因,IE8 对我的 Sass 文件中继承的 html5 CSS 不友好?
- JMeter 在响应断言中使用 span 标签的问题
- html - 在 :hover and :active? 上具有不同效果的 CSS 动画
- html - 相对于居中的 html 内容固定的 CSS 重复背景?
我是 Web 项目的新成员,该项目使用 yarn
而不是 npm
。还有一些我不习惯使用的额外库和配置。
问题是,我一直在努力尝试使用 yarn 将 node-sass 安装到我的机器中。 yarn 添加 node-sass
但是指令给了我一个错误。
我尝试安装多个版本的 NodeJS,我安装了 yarn、python 2.7(包括配置 Windows 环境变量)。
此外,我还安装了 windows-build-tools:npm install --global --production windows-build-tools
并且还安装了 node-gyp:npm install --global node-gyp
我只安装了 Visual Studio 2019。.Net Framework 4.5.1
如果有人知道为什么会出现此问题,我们将不胜感激!
记录错误:
yarn add node-sass
yarn add v1.22.5
[1/5] Validating package.json...
[2/5] Resolving packages...
warning node-sass > node-gyp > request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
[3/5] Fetching packages...
info fsevents@2.1.2: The platform "win32" is incompatible with this module.
info "fsevents@2.1.2" is an optional dependency and failed compatibility check. Excluding it from installation.
info fsevents@1.2.11: The platform "win32" is incompatible with this module.
info "fsevents@1.2.11" is an optional dependency and failed compatibility check. Excluding it from installation.
[4/5] Linking dependencies...
warning " > vuex-persist@2.1.0" has unmet peer dependency "vuex@>=2.5".
warning "@vue/eslint-config-standard > eslint-import-resolver-webpack@0.12.1" has unmet peer dependency "webpack@>=1.11.0".
warning " > eslint-loader@3.0.3" has unmet peer dependency "webpack@^4.0.0 || ^5.0.0".
[5/5] Building fresh packages...
[-/5] ⠂ waiting...
[-/5] ⠂ waiting...
[3/5] ⠂ node-sass
[-/5] ⠂ waiting...
error C:\bitbucket\dcu-feature\node_modules\@quasar\app\node_modules\node-sass: Command failed.
Exit code: 1
Command: node scripts/build.js
Arguments:
Directory: C:\bitbucket\dcu-feature\node_modules\@quasar\app\node_modules\node-sass
Output:
Building: C:\Program Files\nodejs\node.exe C:\bitbucket\dcu-feature\node_modules\@quasar\app\node_modules\node-gyp\bin\node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library=
gyp info it worked if it ends with ok
gyp verb cli [
gyp verb cli 'C:\\Program Files\\nodejs\\node.exe',
gyp verb cli 'C:\\bitbucket\\dcu-feature\\node_modules\\@quasar\\app\\node_modules\\node-gyp\\bin\\node-gyp.js',
gyp verb cli 'rebuild',
gyp verb cli '--verbose',
gyp verb cli '--libsass_ext=',
gyp verb cli '--libsass_cflags=',
gyp verb cli '--libsass_ldflags=',
gyp verb cli '--libsass_library='
gyp verb cli ]
gyp info using node-gyp@3.8.0
gyp info using node@12.16.1 | win32 | x64
gyp verb command rebuild []
gyp verb command clean []
gyp verb clean removing "build" directory
gyp verb command configure []
gyp verb check python checking for Python executable "python2.7" in the PATH
gyp verb `which` failed Error: not found: python2.7
gyp verb `which` failed at getNotFoundError (C:\bitbucket\dcu-feature\node_modules\@quasar\app\node_modules\node-gyp\node_modules\which\which.js:13:12)
gyp verb `which` failed at F (C:\bitbucket\dcu-feature\node_modules\@quasar\app\node_modules\node-gyp\node_modules\which\which.js:68:19)
gyp verb `which` failed at E (C:\bitbucket\dcu-feature\node_modules\@quasar\app\node_modules\node-gyp\node_modules\which\which.js:80:29)
gyp verb `which` failed at C:\bitbucket\dcu-feature\node_modules\@quasar\app\node_modules\node-gyp\node_modules\which\which.js:89:16gyp verb `which` failed at C:\bitbucket\dcu-feature\node_modules\isexe\index.js:42:5
gyp verb `which` failed at C:\bitbucket\dcu-feature\node_modules\isexe\windows.js:36:5
gyp verb `which` failed at FSReqCallback.oncomplete (fs.js:166:21)
gyp verb `which` failed python2.7 Error: not found: python2.7
gyp verb `which` failed at getNotFoundError (C:\bitbucket\dcu-feature\node_modules\@quasar\app\node_modules\node-gyp\node_modules\which\which.js:13:12)
gyp verb `which` failed at F (C:\bitbucket\dcu-feature\node_modules\@quasar\app\node_modules\node-gyp\node_modules\which\which.js:68:19)
gyp verb `which` failed at E (C:\bitbucket\dcu-feature\node_modules\@quasar\app\node_modules\node-gyp\node_modules\which\which.js:80:29)
gyp verb `which` failed at C:\bitbucket\dcu-feature\node_modules\@quasar\app\node_modules\node-gyp\node_modules\which\which.js:89:16gyp verb `which` failed at C:\bitbucket\dcu-feature\node_modules\isexe\index.js:42:5
gyp verb `which` failed at C:\bitbucket\dcu-feature\node_modules\isexe\windows.js:36:5
gyp verb `which` failed at FSReqCallback.oncomplete (fs.js:166:21) {
gyp verb `which` failed stack: 'Error: not found: python2.7\n' +
gyp verb `which` failed ' at getNotFoundError (C:\\bitbucket\\dcu-feature\\node_modules\\@quasar\\app\\node_modules\\node-gyp\\node_modules\\which\\which.js:13:12)\n' +
gyp verb `which` failed ' at F (C:\\bitbucket\\dcu-feature\\node_modules\\@quasar\\app\\node_modules\\node-gyp\\node_modules\\which\\which.js:68:19)\n' +
gyp verb `which` failed ' at E (C:\\bitbucket\\dcu-feature\\node_modules\\@quasar\\app\\node_modules\\node-gyp\\node_modules\\which\\which.js:80:29)\n' +
gyp verb `which` failed ' at C:\\bitbucket\\dcu-feature\\node_modules\\@quasar\\app\\node_modules\\node-gyp\\node_modules\\which\\which.js:89:16\n' +
gyp verb `which` failed ' at C:\\bitbucket\\dcu-feature\\node_modules\\isexe\\index.js:42:5\n' +
gyp verb `which` failed ' at C:\\bitbucket\\dcu-feature\\node_modules\\isexe\\windows.js:36:5\n' +
gyp verb `which` failed ' at FSReqCallback.oncomplete (fs.js:166:21)',
gyp verb `which` failed code: 'ENOENT'
gyp verb `which` failed }
gyp verb could not find "python2.7". checking python launcher
gyp verb could not find "python2.7". guessing location
gyp verb ensuring that file exists: C:\Python27\python.exe
gyp verb check python version `C:\Python27\python.exe -c "import sys; print "2.7.15
gyp verb check python version .%s.%s" % sys.version_info[:3];"` returned: %j
gyp verb get node dir no --target version specified, falling back to host node version: 12.16.1
gyp verb command install [ '12.16.1' ]
gyp verb install input version string "12.16.1"
gyp verb install installing version: 12.16.1
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version is already installed, need to check "installVersion"
gyp verb got "installVersion" 9
gyp verb needs "installVersion" 9
gyp verb install version is good
gyp verb get node dir target node version installed: 12.16.1
gyp verb build dir attempting to create "build" dir: C:\bitbucket\dcu-feature\node_modules\@quasar\app\node_modules\node-sass\build
gyp verb build dir "build" dir needed to be created? C:\bitbucket\dcu-feature\node_modules\@quasar\app\node_modules\node-sass\build
gyp verb find vs2017 Found installation at: C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional
gyp verb find vs2017 - Found Microsoft.VisualStudio.Component.VC.Tools.x86.x64
gyp verb find vs2017 - Found Microsoft.VisualStudio.Component.Windows10SDK.17763
gyp verb find vs2017 - Found Microsoft.VisualStudio.VC.MSBuild.Base
gyp verb find vs2017 - Found Microsoft.VisualStudio.Component.Windows10SDK.18362
gyp verb find vs2017 - Found Microsoft.VisualStudio.Component.Windows10SDK.16299
gyp verb find vs2017 - Found Microsoft.VisualStudio.Component.Windows10SDK.17134
gyp verb find vs2017 - Using this installation with Windows 10 SDK
gyp verb find vs2017 using installation: C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional
gyp verb build/config.gypi creating config file
gyp verb build/config.gypi writing out config file: C:\bitbucket\dcu-feature\node_modules\@quasar\app\node_modules\node-sass\build\config.gypi
gyp verb config.gypi checking for gypi file: C:\bitbucket\dcu-feature\node_modules\@quasar\app\node_modules\node-sass\config.gypi
gyp verb common.gypi checking for gypi file: C:\bitbucket\dcu-feature\node_modules\@quasar\app\node_modules\node-sass\common.gypi
gyp verb gyp gyp format was not specified; forcing "msvs"
gyp info spawn C:\Python27\python.exe
gyp info spawn args [
gyp info spawn args 'C:\\bitbucket\\dcu-feature\\node_modules\\@quasar\\app\\node_modules\\node-gyp\\gyp\\gyp_main.py',
gyp info spawn args 'binding.gyp',
gyp info spawn args '-f',
gyp info spawn args 'msvs',
gyp info spawn args '-G',
gyp info spawn args 'msvs_version=2015',
gyp info spawn args '-I',
gyp info spawn args 'C:\\bitbucket\\dcu-feature\\node_modules\\@quasar\\app\\node_modules\\node-sass\\build\\config.gypi',
gyp info spawn args '-I',
gyp info spawn args 'C:\\bitbucket\\dcu-feature\\node_modules\\@quasar\\app\\node_modules\\node-gyp\\addon.gypi',
gyp info spawn args '-I',
gyp info spawn args 'C:\\Users\\m_bolanos-v\\.node-gyp\\12.16.1\\include\\node\\common.gypi',
gyp info spawn args '-Dlibrary=shared_library',
gyp info spawn args '-Dvisibility=default',
gyp info spawn args '-Dnode_root_dir=C:\\Users\\m_bolanos-v\\.node-gyp\\12.16.1',
gyp info spawn args '-Dnode_gyp_dir=C:\\bitbucket\\dcu-feature\\node_modules\\@quasar\\app\\node_modules\\node-gyp',
gyp info spawn args '-Dnode_lib_file=C:\\Users\\m_bolanos-v\\.node-gyp\\12.16.1\\<(target_arch)\\node.lib',
gyp info spawn args '-Dmodule_root_dir=C:\\bitbucket\\dcu-feature\\node_modules\\@quasar\\app\\node_modules\\node-sass',
gyp info spawn args '-Dnode_engine=v8',
gyp info spawn args '--depth=.',
gyp info spawn args '--no-parallel',
gyp info spawn args '--generator-output',
gyp info spawn args 'C:\\bitbucket\\dcu-feature\\node_modules\\@quasar\\app\\node_modules\\node-sass\\build',
gyp info spawn args '-Goutput_dir=.'
gyp info spawn args ]
gyp verb command build []
gyp verb build type Release
gyp verb architecture x64
gyp verb node dev dir C:\Users\m_bolanos-v\.node-gyp\12.16.1
gyp verb found first Solution file build/binding.sln
gyp verb using MSBuild: C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\15.0\Bin\MSBuild.exe
gyp info spawn C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\15.0\Bin\MSBuild.exe
gyp info spawn args [
gyp info spawn args 'build/binding.sln',
gyp info spawn args '/nologo',
gyp info spawn args '/p:Configuration=Release;Platform=x64'
gyp info spawn args ]
gyp ERR! UNCAUGHT EXCEPTION
gyp ERR! stack Error: spawn C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\15.0\Bin\MSBuild.exe ENOENT
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:267:19)
gyp ERR! stack at onErrorNT (internal/child_process.js:469:16)
gyp ERR! stack at processTicksAndRejections (internal/process/task_queues.js:84:21)
gyp ERR! System Windows_NT 10.0.19041
gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\bitbucket\\dcu-feature\\node_modules\\@quasar\\app\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
gyp ERR! cwd C:\bitbucket\dcu-feature\node_modules\@quasar\app\node_modules\node-sass
gyp ERR! node -v v12.16.1
gyp ERR! node-gyp -v v3.8.0
gyp ERR! This is a bug in `node-gyp`.
最佳答案
我的配置:
NodeJs 14.15.1
Global packages
NPM 6.14.8
yarn 1.22.5
@quasar/cli 1.1.2
好吧,这是我为让它再次工作所做的步骤:
"node-sass": "^4.11.0"
希望对某人有所帮助o/
关于node.js - yarn 尝试安装 node-sass 的问题,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/64884674/
说真的,你怎么能在不发疯的情况下处理所有这些异常呢?我是不是读了太多关于异常处理的文章或什么?我尝试重构了几次,但每次似乎都以更糟糕的结果告终。也许我应该承认确实会发生异常(exception)情况,
背景 两者 try/rescue和 try/catch是 Elixir 中的错误处理技术。根据 corresponding chapter在介绍指南中。 Errors can be rescued u
每当我尝试在 Raspberry PI 上运行此 python 脚本时,我都会遇到问题: import socket import sys # Create a TCP/IP socket sock
我想知道一些关于 PHP 的 try , catch声明。 让我们考虑以下示例。 abstract class ExceptionA extends Exception {} class Except
我的 laravel v5.4 项目中有两个模型,user 和 admin。 在 config/auth.php 中,我向守卫和提供者添加了管理员,如下所示: 'guards' => [ 'w
try: r = requests.get(url, params={'s': thing}) except requests.ConnectionError, e: print e
我有以下代码。 但是,它并不能捕获所有错误,而我仍然会收到“throw er;//未处理的'错误'事件”。 为什么是这样? app.post('/api/properties/zip/:zip/bed
问题与细节 我正在使用自定义错误处理,遇到的错误之一是“路径中的非法字符”。我有一个自定义函数,旨在通过路径字符串查找此类非法字符,并在找到它们时引发自定义错误。但是我发现,取决于非法字符,Test-
This question already has answers here: How do I catch a numpy warning like it's an exception (not j
我正在使用其他人的代码,但我不熟悉try/catch,因此我举了一个类似的小例子。在第11行上,如果我写了error(''),似乎没有发现错误并增加了索引j。但是,编写error(' ')或error
我在我的一个程序中遇到了这个问题,在这种情况下,尝试/异常(exception)的错误使程序变得更好,以防用户意外输入了他们不应该输入的内容。它仍然给我错误,我为为什么感到困惑。如果对我的问题确实很重
我在尝试TRY ... CATCH块时遇到问题。有人可以解释为什么以下代码无法执行我的sp吗? DECLARE @Result int SET @Result = 0 BEGIN TRY SE
我有一个相当大的 powershell 脚本,其中包含许多(20 多个)执行各种操作的函数。 现在所有代码实际上都没有任何错误处理或重试功能。如果某个特定的任务/功能失败,它就会失败并继续。 我想改进
为什么我尝试时需要导入 inputmismatchException catch(InputMismatchException e){ System.out.println("
我对此感到困惑 - 我为辅助方法编写了一个 try/catch 。它的目的是捕获任何无效输入(任何不是“男性”或“女性”的内容(没有特定情况)。如果输入无效,它将通知用户,然后让他们重试。如果有效,则
我有时会发现自己处于如下场景。尽可能简单地陈述问题 “有时我会创建一段代码,Java 让我将其包含在 try/catch 语句中。我没有使用 catch,所以我将其留空。为什么这是错误的?” boo
我有点困惑为什么当我不使用 Try block 时会出现 Try block 错误。 我在代码块底部附近收到错误通知。如果我不使用 try/catch,有人可以向我解释为什么会发生这种情况吗? 它是否
我已经盯着我的电脑两个小时了,我不知道我做错了什么。谁能帮助我看到光明? package blackjack; import java.util.Random; import java.util.Sc
我想将方法保存在 Enum 中,但 Class.getDeclaredMethod 抛出 NoSuchMethodException,那么我该如何处理呢?我的代码: public enum Car
这个问题已经有答案了: Executing multi-line statements in the one-line command-line (18 个回答) 已关闭 3 年前。 如何使用try.
我是一名优秀的程序员,十分优秀!