npm ERR! code 1 npm ERR! path E:\zkwz\microalgae_manager-dev\node_modules\deasync npm ERR! command failed npm ERR! command C:\Windows\system32\cmd.exe /d /s /c node ./build.js npm ERR! `win32-x64-node-16` exists; testing npm ERR! Problem with the binary; manual build incoming npm ERR! stdout= npm ERR! err=null npm ERR! Debugger attached. npm ERR! Debugger attached. npm ERR! gyp info it worked if it ends with ok npm ERR! gyp info using [email protected] npm ERR! gyp info using [email protected] | win32 | x64 npm ERR! gyp ERR! find Python npm ERR! gyp ERR! find Python checking Python explicitly set from command line or npm configuration npm ERR! gyp ERR! find Python - "--python=" or "npm config get python" is "python3.8.0" npm ERR! gyp ERR! find Python - "python3.8.0" is not in PATH or produced an error npm ERR! gyp ERR! find Python Python is not set from environment variable PYTHON npm ERR! gyp ERR! find Python checking if "python3" can be used npm ERR! gyp ERR! find Python - "python3" is not in

时间: 2025-04-27 19:28:40 浏览: 50
<think>好的,我现在需要帮助用户解决在安装deasync模块时遇到的Python环境配置问题。用户提到的是npm install deasync时出现gyp ERR find Python错误,特别是win32系统下node-gyp找不到Python路径的问题。 首先,我需要回忆一下node-gyp在Windows上的依赖。根据之前的知识,node-gyp需要Python 2.7或3.x版本,但可能推荐使用Python 2.7,因为某些旧模块可能尚未兼容Python 3。不过现在可能有所变化,需要确认当前node-gyp的官方文档是否已更新支持Python 3。比如,node-gyp现在支持Python 3,但需要特定版本,如3.6到3.9之间,并且需要确保Python在系统路径中。 接下来,用户的问题可能是Python未正确安装,或者路径未添加到系统环境变量中。可能需要指导用户检查Python的安装情况,并确保安装时勾选了“Add Python to PATH”选项。如果用户之前安装时未勾选,可能需要手动添加Python的安装路径到环境变量中。 另外,用户可能安装了多个Python版本,导致node-gyp无法找到正确的版本。这时候需要指定使用哪个Python版本。可以通过npm config set python命令来设置,例如指向Python 3.9的路径。或者使用环境变量如NODE_GYP_FORCE_PYTHON来强制指定Python解释器的路径。 还有一种情况是用户安装了Visual Studio Build Tools或Windows SDK,因为node-gyp在Windows上还需要这些工具来编译C++代码。可能需要检查用户是否安装了必要的构建工具,如Visual C++ Build Tools 2019或更高版本,并确保安装时选择了C++相关组件。 另外,可能需要以管理员权限运行命令提示符,或者使用PowerShell时权限不足,导致无法访问某些目录。建议用户尝试在管理员模式下运行npm install。 总结下来,解决步骤可能包括:安装正确的Python版本并添加到PATH,安装构建工具,配置npm指向正确的Python路径,以及以管理员权限运行安装命令。此外,可能需要清除npm缓存或删除node_modules后重新安装。 同时,我需要参考用户提供的引用内容,其中提到node-sass在Windows上需要node-gyp和Python的支持。这可能与deasync的问题类似,因此解决方案可能有共通之处。比如,用户可能需要安装Python和构建工具,并正确配置环境变量。 最后,生成相关问题需要考虑用户在解决当前问题后可能遇到的后续问题,比如其他依赖node-gyp的模块安装问题,或者如何优化环境配置避免类似问题,以及不同Python版本的管理方法等。</think>### 解决npm安装deasync时Python环境配置问题的分步指南 #### 1. 确认Python安装与版本要求 - node-gyp要求Python 2.7或3.5+版本(推荐Python 3.9+以确保兼容性)[^1] - 通过命令行验证Python安装: ```bash python --version # 或尝试Python 3.x的别名 python3 --version ``` #### 2. 添加Python到系统PATH - 如果提示`python not found`,需手动添加Python路径: 1. 右键点击"此电脑" → 属性 → 高级系统设置 → 环境变量 2. 在"系统变量"中找到`Path`,添加Python安装路径(如`C:\Python39`)和脚本目录(如`C:\Python39\Scripts`) 3. 重启命令行工具使配置生效 #### 3. 配置npm使用指定Python版本 ```bash # 设置全局Python路径(替换为你的实际路径) npm config set python "C:\Python39\python.exe" # 验证配置 npm config get python ``` #### 4. 安装Windows构建工具链 - 必需组件: - Visual Studio 2019/2022的C++桌面开发工作负载 - Windows SDK - Python 3.x 可通过以下任一方式安装: ```bash # 方式1:使用微软官方工具 npm install --global windows-build-tools --vs2019 # 方式2:手动安装 # 下载Visual Studio Installer后选择"C++桌面开发"工作负载 ``` #### 5. 修复安装流程(管理员权限运行) ```bash # 清理旧缓存 npm cache clean --force rmdir /s /q node_modules # 重新安装(使用管理员命令行) npm install --global --production windows-build-tools npm install deasync --build-from-source ``` #### 典型错误解决方案 **错误示例**: ``` gyp ERR! find Python gyp ERR! stack Error: Could not find any Python installation ``` **修复方法**: ```bash # 设置临时环境变量(替换实际路径) set PYTHON=C:\Python39\python.exe npm install deasync ```
阅读全文

相关推荐

npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code EPERM npm ERR! syscall open npm ERR! path D:\Node\node_cache\_cacache\tmp\eb2d693d npm ERR! errno -4048 npm ERR! Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\eb2d693d' npm ERR! [OperationalError: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\eb2d693d'] { npm ERR! cause: [Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\eb2d693d'] { npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\eb2d693d' npm ERR! }, npm ERR! isOperational: true, npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\eb2d693d' npm ERR! } npm ERR! npm ERR! The operation was rejected by your operating system. npm ERR! It's possible that the file was already in use (by a text editor or antivirus), npm ERR! or that you lack permissions to access it. npm ERR! npm ERR! If you believe this might be a permissions issue, please double-check the npm ERR! permissions of the file and its containing directories, or try running npm ERR! the command again as root/Administrator. npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code EPERM npm ERR! syscall open npm ERR! path D:\Node\node_cache\_cacache\tmp\eb2d693d npm ERR! errno -4048 npm ERR! Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\eb2d693d' npm ERR! [OperationalError: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\eb2d693d'] { npm ERR! cause: [Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\eb2d693d'] { npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\eb2d693d' npm ERR! }, npm ERR! isOperational: true, npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\eb2d693d' npm ERR! } npm ERR! npm ERR! The operation was rejected by your operating system. npm ERR! It's possible that the file was already in use (by a text editor or antivirus), npm ERR! or that you lack permissions to access it. npm ERR! npm ERR! If you believe this might be a permissions issue, please double-check the npm ERR! permissions of the file and its containing directories, or try running npm ERR! the command again as root/Administrator. npm ERR! code EPERM npm ERR! syscall open npm ERR! path D:\Node\node_cache\_cacache\tmp\a4a16f53 npm ERR! errno -4048 npm ERR! Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\a4a16f53' npm ERR! [OperationalError: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\a4a16f53'] { npm ERR! cause: [Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\a4a16f53'] { npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\a4a16f53' npm ERR! }, npm ERR! isOperational: true, npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\a4a16f53' npm ERR! } npm ERR! npm ERR! The operation was rejected by your operating system. npm ERR! It's possible that the file was already in use (by a text editor or antivirus), npm ERR! or that you lack permissions to access it. npm ERR! npm ERR! If you believe this might be a permissions issue, please double-check the npm ERR! permissions of the file and its containing directories, or try running npm ERR! the command again as root/Administrator. npm WARN registry Unexpected warning for https://registry.npmjs.org/: Miscellaneous Warning EPERM: EPERM: operation not permitted, open 'D:\\Node\\node_cache\\_cacache\\tmp\\6ee0a780' npm WARN registry Using stale data from https://registry.npmjs.org/ due to a request error during revalidation. npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code EPERM npm ERR! syscall open npm ERR! path D:\Node\node_cache\_cacache\tmp\aa34d15e npm ERR! errno -4048 npm ERR! Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\aa34d15e' npm ERR! [OperationalError: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\aa34d15e'] { npm ERR! cause: [Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\aa34d15e'] { npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\aa34d15e' npm ERR! }, npm ERR! isOperational: true, npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\aa34d15e' npm ERR! } npm ERR! npm ERR! The operation was rejected by your operating system. npm ERR! It's possible that the file was already in use (by a text editor or antivirus), npm ERR! or that you lack permissions to access it. npm ERR! npm ERR! If you believe this might be a permissions issue, please double-check the npm ERR! permissions of the file and its containing directories, or try running npm ERR! the command again as root/Administrator. npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code EPERM npm ERR! syscall open npm ERR! path D:\Node\node_cache\_cacache\tmp\dd6cc8ed npm ERR! errno -4048 npm ERR! Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\dd6cc8ed' npm ERR! [OperationalError: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\dd6cc8ed'] { npm ERR! cause: [Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\dd6cc8ed'] { npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\dd6cc8ed' npm ERR! }, npm ERR! isOperational: true, npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\dd6cc8ed' npm ERR! } npm ERR! npm ERR! The operation was rejected by your operating system. npm ERR! It's possible that the file was already in use (by a text editor or antivirus), npm ERR! or that you lack permissions to access it. npm ERR! npm ERR! If you believe this might be a permissions issue, please double-check the npm ERR! permissions of the file and its containing directories, or try running npm ERR! the command again as root/Administrator. npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code EPERM npm ERR! syscall open npm ERR! path D:\Node\node_cache\_cacache\tmp\df92457e npm ERR! errno -4048 npm ERR! Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\df92457e' npm ERR! [OperationalError: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\df92457e'] { npm ERR! cause: [Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\df92457e'] { npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\df92457e' npm ERR! }, npm ERR! isOperational: true, npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\df92457e' npm ERR! } npm ERR! npm ERR! The operation was rejected by your operating system. npm ERR! It's possible that the file was already in use (by a text editor or antivirus), npm ERR! or that you lack permissions to access it. npm ERR! npm ERR! If you believe this might be a permissions issue, please double-check the npm ERR! permissions of the file and its containing directories, or try running npm ERR! the command again as root/Administrator. npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code EPERM npm ERR! syscall open npm ERR! path D:\Node\node_cache\_cacache\tmp\dd6cc8ed npm ERR! errno -4048 npm ERR! Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\dd6cc8ed' npm ERR! [OperationalError: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\dd6cc8ed'] { npm ERR! cause: [Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\dd6cc8ed'] { npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\dd6cc8ed' npm ERR! }, npm ERR! isOperational: true, npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\dd6cc8ed' npm ERR! } npm ERR! npm ERR! The operation was rejected by your operating system. npm ERR! It's possible that the file was already in use (by a text editor or antivirus), npm ERR! or that you lack permissions to access it. npm ERR! npm ERR! If you believe this might be a permissions issue, please double-check the npm ERR! permissions of the file and its containing directories, or try running npm ERR! the command again as root/Administrator. npm ERR! code EPERM npm ERR! syscall open npm ERR! path D:\Node\node_cache\_cacache\tmp\01bdab06 npm ERR! errno -4048 npm ERR! Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\01bdab06' npm ERR! [OperationalError: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\01bdab06'] { npm ERR! cause: [Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\01bdab06'] { npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\01bdab06' npm ERR! }, npm ERR! isOperational: true, npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\01bdab06' npm ERR! } npm ERR! npm ERR! The operation was rejected by your operating system. npm ERR! It's possible that the file was already in use (by a text editor or antivirus), npm ERR! or that you lack permissions to access it. npm ERR! npm ERR! If you believe this might be a permissions issue, please double-check the npm ERR! permissions of the file and its containing directories, or try running npm ERR! the command again as root/Administrator. npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code EPERM npm ERR! syscall open npm ERR! path D:\Node\node_cache\_cacache\tmp\eb849235 npm ERR! errno -4048 npm ERR! Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\eb849235' npm ERR! [OperationalError: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\eb849235'] { npm ERR! cause: [Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\eb849235'] { npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\eb849235' npm ERR! }, npm ERR! isOperational: true, npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\eb849235' npm ERR! } npm ERR! npm ERR! The operation was rejected by your operating system. npm ERR! It's possible that the file was already in use (by a text editor or antivirus), npm ERR! or that you lack permissions to access it. npm ERR! npm ERR! If you believe this might be a permissions issue, please double-check the npm ERR! permissions of the file and its containing directories, or try running npm ERR! the command again as root/Administrator. npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code EPERM npm ERR! syscall open npm ERR! path D:\Node\node_cache\_cacache\tmp\df92457e npm ERR! errno -4048 npm ERR! Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\df92457e' npm ERR! [OperationalError: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\df92457e'] { npm ERR! cause: [Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\df92457e'] { npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\df92457e' npm ERR! }, npm ERR! isOperational: true, npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\df92457e' npm ERR! } npm ERR! npm ERR! The operation was rejected by your operating system. npm ERR! It's possible that the file was already in use (by a text editor or antivirus), npm ERR! or that you lack permissions to access it. npm ERR! npm ERR! If you believe this might be a permissions issue, please double-check the npm ERR! permissions of the file and its containing directories, or try running npm ERR! the command again as root/Administrator. npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code EPERM npm ERR! syscall open npm ERR! path D:\Node\node_cache\_cacache\tmp\3688e03a npm ERR! errno -4048 npm ERR! Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\3688e03a' npm ERR! [OperationalError: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\3688e03a'] { npm ERR! cause: [Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\3688e03a'] { npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\3688e03a' npm ERR! }, npm ERR! isOperational: true, npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\3688e03a' npm ERR! } npm ERR! npm ERR! The operation was rejected by your operating system. npm ERR! It's possible that the file was already in use (by a text editor or antivirus), npm ERR! or that you lack permissions to access it. npm ERR! npm ERR! If you believe this might be a permissions issue, please double-check the npm ERR! permissions of the file and its containing directories, or try running npm ERR! the command again as root/Administrator. npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code EPERM npm ERR! syscall open npm ERR! path D:\Node\node_cache\_cacache\tmp\35daa67e npm ERR! errno -4048 npm ERR! Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\35daa67e' npm ERR! [OperationalError: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\35daa67e'] { npm ERR! cause: [Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\35daa67e'] { npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\35daa67e' npm ERR! }, npm ERR! isOperational: true, npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\35daa67e' npm ERR! } npm ERR! npm ERR! The operation was rejected by your operating system. npm ERR! It's possible that the file was already in use (by a text editor or antivirus), npm ERR! or that you lack permissions to access it. npm ERR! npm ERR! If you believe this might be a permissions issue, please double-check the npm ERR! permissions of the file and its containing directories, or try running npm ERR! the command again as root/Administrator. npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code EPERM npm ERR! syscall open npm ERR! path D:\Node\node_cache\_cacache\tmp\35daa67e npm ERR! errno -4048 npm ERR! Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\35daa67e' npm ERR! [OperationalError: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\35daa67e'] { npm ERR! cause: [Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\35daa67e'] { npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\35daa67e' npm ERR! }, npm ERR! isOperational: true, npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\35daa67e' npm ERR! } npm ERR! npm ERR! The operation was rejected by your operating system. npm ERR! It's possible that the file was already in use (by a text editor or antivirus), npm ERR! or that you lack permissions to access it. npm ERR! npm ERR! If you believe this might be a permissions issue, please double-check the npm ERR! permissions of the file and its containing directories, or try running npm ERR! the command again as root/Administrator. npm ERR! code EPERM npm ERR! syscall open npm ERR! path D:\Node\node_cache\_cacache\tmp\01bdab06 npm ERR! errno -4048 npm ERR! Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\01bdab06' npm ERR! [OperationalError: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\01bdab06'] { npm ERR! cause: [Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\01bdab06'] { npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\01bdab06' npm ERR! }, npm ERR! isOperational: true, npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\01bdab06' npm ERR! } npm ERR! npm ERR! The operation was rejected by your operating system. npm ERR! It's possible that the file was already in use (by a text editor or antivirus), npm ERR! or that you lack permissions to access it. npm ERR! npm ERR! If you believe this might be a permissions issue, please double-check the npm ERR! permissions of the file and its containing directories, or try running npm ERR! the command again as root/Administrator. npm ERR! code EPERM npm ERR! syscall open npm ERR! path D:\Node\node_cache\_cacache\tmp\884bfc72 npm ERR! errno -4048 npm ERR! Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\884bfc72' npm ERR! [OperationalError: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\884bfc72'] { npm ERR! cause: [Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\884bfc72'] { npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\884bfc72' npm ERR! }, npm ERR! isOperational: true, npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\884bfc72' npm ERR! } npm ERR! npm ERR! The operation was rejected by your operating system. npm ERR! It's possible that the file was already in use (by a text editor or antivirus), npm ERR! or that you lack permissions to access it. npm ERR! npm ERR! If you believe this might be a permissions issue, please double-check the npm ERR! permissions of the file and its containing directories, or try running npm ERR! the command again as root/Administrator. npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code EPERM npm ERR! syscall open npm ERR! path D:\Node\node_cache\_cacache\tmp\aa34d15e npm ERR! errno -4048 npm ERR! Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\aa34d15e' npm ERR! [OperationalError: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\aa34d15e'] { npm ERR! cause: [Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\aa34d15e'] { npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\aa34d15e' npm ERR! }, npm ERR! isOperational: true, npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\aa34d15e' npm ERR! } npm ERR! npm ERR! The operation was rejected by your operating system. npm ERR! It's possible that the file was already in use (by a text editor or antivirus), npm ERR! or that you lack permissions to access it. npm ERR! npm ERR! If you believe this might be a permissions issue, please double-check the npm ERR! permissions of the file and its containing directories, or try running npm ERR! the command again as root/Administrator. npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code EPERM npm ERR! syscall open npm ERR! path D:\Node\node_cache\_cacache\tmp\3688e03a npm ERR! errno -4048 npm ERR! Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\3688e03a' npm ERR! [OperationalError: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\3688e03a'] { npm ERR! cause: [Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\3688e03a'] { npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\3688e03a' npm ERR! }, npm ERR! isOperational: true, npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\3688e03a' npm ERR! } npm ERR! npm ERR! The operation was rejected by your operating system. npm ERR! It's possible that the file was already in use (by a text editor or antivirus), npm ERR! or that you lack permissions to access it. npm ERR! npm ERR! If you believe this might be a permissions issue, please double-check the npm ERR! permissions of the file and its containing directories, or try running npm ERR! the command again as root/Administrator.

npm ERR! code EPERM npm ERR! syscall mkdir npm ERR! path E:\NODE\node_cache\_cacache\index-v5\ae\cb npm ERR! errno -4048 npm ERR! Error: EPERM: operation not permitted, mkdir 'E:\NODE\node_cache\_cacache\index-v5\ae\cb' npm ERR! [Error: EPERM: operation not permitted, mkdir 'E:\NODE\node_cache\_cacache\index-v5\ae\cb'] { npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'mkdir', npm ERR! path: 'E:\\NODE\\node_cache\\_cacache\\index-v5\\ae\\cb', npm ERR! requiredBy: '.' npm ERR! } npm ERR! npm ERR! The operation was rejected by your operating system. npm ERR! It's possible that the file was already in use (by a text editor or antivirus), npm ERR! or that you lack permissions to access it. npm ERR! npm ERR! If you believe this might be a permissions issue, please double-check the npm ERR! permissions of the file and its containing directories, or try running npm ERR! the command again as root/Administrator. npm ERR! Log files were not written due to an error writing to the directory: E:\NODE\node_cache\_logs npm ERR! You can rerun the command with --loglevel=verbose to see the logs in your terminal ERROR Error: command failed: npm install --loglevel error --legacy-peer-deps Error: command failed: npm install --loglevel error --legacy-peer-deps at ChildProcess.<anonymous> (E:\NODE\node_global\node_modules\@vue\cli\lib\util\executeCommand.js:138:16) at ChildProcess.emit (node:events:513:28) at cp.emit (E:\NODE\node_global\node_modules\@vue\cli\node_modules\cross-spawn\lib\enoent.js:34:29) at maybeClose (node:internal/child_process:1091:16) at ChildProcess._handle.onexit (node:internal/child_process:302:5)

npm ERR! code EPERM npm ERR! syscall rename npm ERR! path D:\nodejs\node_modules\cnpm\node_modules\npm\node_modules\.node-gyp.DELETE\node_modules\@npmcli npm ERR! dest D:\nodejs\node_modules\cnpm\node_modules\npm\node_modules\node-gyp\node_modules\@npmcli npm ERR! errno -4048 npm ERR! Error: EPERM: operation not permitted, rename 'D:\nodejs\node_modules\cnpm\node_modules\npm\node_modules\.node-gyp.DELETE\node_modules\@npmcli' -> 'D:\nodejs\node_modules\cnpm\node_modules\npm\node_modules\node-gyp\node_modules\@npmcli' npm ERR! { [Error: EPERM: operation not permitted, rename 'D:\nodejs\node_modules\cnpm\node_modules\npm\node_modules\.node-gyp.DELETE\node_modules\@npmcli' -> 'D:\nodejs\node_modules\cnpm\node_modules\npm\node_modules\node-gyp\node_modules\@npmcli'] npm ERR! cause: npm ERR! { Error: EPERM: operation not permitted, rename 'D:\nodejs\node_modules\cnpm\node_modules\npm\node_modules\.node-gyp.DELETE\node_modules\@npmcli' -> 'D:\nodejs\node_modules\cnpm\node_modules\npm\node_modules\node-gyp\node_modules\@npmcli' npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'rename', npm ERR! path: npm ERR! 'D:\\nodejs\\node_modules\\cnpm\\node_modules\\npm\\node_modules\\.node-gyp.DELETE\\node_modules\\@npmcli', npm ERR! The operation was rejected by your operating system. npm ERR! It's possible that the file was already in use (by a text editor or antivirus),npm ERR! or that you lack permissions to access it. npm ERR! npm ERR! If you believe this might be a permissions issue, please double-check thenpm ERR! permissions of the file and its containing directories, or try runningnpm ERR! the command again as root/Administrator. npm ERR! A complete log of this run can be found in: npm ERR! C:\Users\猫管家\AppData\Roaming\npm-cache\_logs\2023-04-18T06_19_27_636Z-debug.log

npm ERR! code 1 npm ERR! git dep preparation failed npm ERR! command D:\Program Files\nodejs\node.exe D:\node\nodejs\node_global\node_modules\npm\bin\npm-cli.js install --force --cache=D:\Program Files\nodejs\node_cache --prefer-offline=false --prefer-online=false --offline=false --no-progress --no-save --no-audit --include=dev --include=peer --include=optional --no-package-lock-only --no-dry-run npm ERR! npm WARN using --force Recommended protections disabled. npm ERR! npm WARN deprecated [email protected]: This package is no longer supported. npm ERR! npm WARN deprecated [email protected]: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful. npm ERR! npm WARN deprecated @npmcli/[email protected]: This functionality has been moved to @npmcli/fs npm ERR! npm WARN deprecated @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-properties instead. npm ERR! npm WARN deprecated [email protected]: This package is deprecated. Use require('node:util').isDeepStrictEqual instead. npm ERR! npm WARN deprecated @humanwhocodes/[email protected]: Use @eslint/config-array instead npm ERR! npm WARN deprecated [email protected]: This package is no longer supported. npm ERR! npm WARN deprecated [email protected]: Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility npm ERR! npm WARN deprecated [email protected]: See https://github.com/lydell/source-map-url#deprecated npm ERR! npm WARN deprecated [email protected]: Rimraf versions prior to v4 are no longer supported npm ERR! npm WARN deprecated [email protected]: Rimraf versions prior to v4 are no longer supported npm ERR! npm WARN deprecated [email protected]: This module is no longer supported. npm ERR! npm WARN deprecated [email protected]: Rimraf versions prior to v4 are no longer supported npm ERR! npm WARN deprecated [email protected]: Rimraf versions prior to v4 are no longer supported npm ERR! npm WARN deprecated [email protected]: Rimraf versions prior to v4 are no longer supported npm ERR! npm WARN deprecated [email protected]: Rimraf versions prior to v4 are no longer supported npm ERR! npm WARN deprecated [email protected]: This package is no longer supported. npm ERR! npm WARN deprecated @hapi/[email protected]: This version has been deprecated and is no longer supported or maintained npm ERR! npm WARN deprecated @hapi/[email protected]: This version has been deprecated and is no longer supported or maintained npm ERR! npm WARN deprecated [email protected]: Rimraf versions prior to v4 are no longer supported npm ERR! npm WARN deprecated [email protected]: Rimraf versions prior to v4 are no longer supported npm ERR! npm WARN deprecated [email protected]: Please upgrade to consolidate v1.0.0+ as it has been modernized with several long-awaited fixes implemented. Maintenance is supported by Forward Email at https://forwardemail.net ; follow/watch https://github.com/ladjs/consolidate for updates and release changelog npm ERR! npm WARN deprecated [email protected]: This package is no longer supported. npm ERR! npm WARN deprecated [email protected]: Please see https://github.com/lydell/urix#deprecated npm ERR! npm WARN deprecated [email protected]: this library is no longer supported npm ERR! npm WARN deprecated [email protected]: Rimraf versions prior to v4 are no longer supported npm ERR! npm WARN deprecated [email protected]: Glob versions prior to v9 are no longer supported npm ERR! npm WARN deprecated [email protected]: You or someone you depend on is using Q, the JavaScript Promise library that gave JavaScript developers strong feelings about promises. They can almost certainly migrate to the native JavaScript promise now. Thank you literally everyone for joining me in this bet against the odds. Be excellent to each other. npm ERR! npm WARN deprecated npm ERR! npm WARN deprecated (For a CapTP with native promises, see @endo/eventual-send and @endo/captp) npm ERR! npm WARN deprecated [email protected]: Glob versions prior to v9 are no longer supported npm ERR! npm WARN deprecated @humanwhocodes/[email protected]: Use @eslint/object-schema instead npm ERR! npm WARN deprecated [email protected]: See https://github.com/lydell/source-map-resolve#deprecated npm ERR! npm WARN deprecated [email protected]: https://github.com/lydell/resolve-url#deprecated npm ERR! npm WARN deprecated [email protected]: This package is no longer supported. npm ERR! npm WARN deprecated [email protected]: 3.x is no longer supported npm ERR! npm WARN deprecated [email protected]: This package is no longer supported. npm ERR! npm WARN deprecated @hapi/[email protected]: Moved to 'npm install @sideway/address' npm ERR! npm WARN deprecated [email protected]: babel-eslint is now @babel/eslint-parser. This package will no longer receive updates. npm ERR! npm WARN deprecated @babel/[email protected]: 🚨 This package has been deprecated in favor of separate inclusion of a polyfill and regenerator-runtime (when needed). See the @babel/polyfill docs (https://babeljs.io/docs/en/babel-polyfill) for more information. npm ERR! npm WARN deprecated [email protected]: This package is no longer supported. npm ERR! npm WARN deprecated [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm ERR! npm WARN deprecated [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm ERR! npm WARN deprecated [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm ERR! npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142 npm ERR! npm WARN deprecated [email protected]: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info. npm ERR! npm WARN deprecated [email protected]: This package is no longer supported. npm ERR! npm WARN deprecated @hapi/[email protected]: This version has been deprecated and is no longer supported or maintained npm ERR! npm WARN deprecated @hapi/[email protected]: Switch to 'npm install joi' npm ERR! npm WARN deprecated [email protected]: This SVGO version is no longer supported. Upgrade to v2.x.x. npm ERR! npm WARN deprecated [email protected]: This version of tar is no longer supported, and will not receive security updates. Please upgrade asap. npm ERR! npm WARN deprecated [email protected]: The zlib module provides APIs for brotli compression/decompression starting with Node.js v10.16.0, please use it over iltorb npm ERR! npm WARN deprecated [email protected]: Vue 2 has reached EOL and is no longer actively maintained. See https://v2.vuejs.org/eol/ for more details. npm ERR! npm WARN deprecated [email protected]: Node Sass is no longer supported. Please use sass or sass-embedded instead. npm ERR! npm WARN deprecated [email protected]: This version is no longer supported. Please see https://eslint.org/version-support for other options. npm ERR! npm WARN deprecated [email protected]: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, fea ture detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js. npm ERR! npm WARN deprecated [email protected]: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, fea ture detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js. npm ERR! npm WARN cleanup Failed to remove some directories [ npm ERR! npm WARN cleanup [ npm ERR! npm WARN cleanup 'D:\\Program Files\\nodejs\\node_cache\\_cacache\\tmp\\git-cloneuwf27x\\node_modules\\mozjpeg', npm ERR! npm WARN cleanup [Error: EBUSY: resource busy or locked, rmdir 'D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\mozjpeg'] { npm ERR! npm WARN cleanup errno: -4082, npm ERR! npm WARN cleanup code: 'EBUSY', npm ERR! npm WARN cleanup syscall: 'rmdir', npm ERR! npm WARN cleanup path: 'D:\\Program Files\\nodejs\\node_cache\\_cacache\\tmp\\git-cloneuwf27x\\node_modules\\mozjpeg' npm ERR! npm WARN cleanup } npm ERR! npm WARN cleanup ], npm ERR! npm WARN cleanup [ npm ERR! npm WARN cleanup 'D:\\Program Files\\nodejs\\node_cache\\_cacache\\tmp\\git-cloneuwf27x\\node_modules\\optipng-bin', npm ERR! npm WARN cleanup [Error: EBUSY: resource busy or locked, rmdir 'D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\optipng-bin'] { npm ERR! npm WARN cleanup errno: -4082, npm ERR! npm WARN cleanup code: 'EBUSY', npm ERR! npm WARN cleanup syscall: 'rmdir', npm ERR! npm WARN cleanup path: 'D:\\Program Files\\nodejs\\node_cache\\_cacache\\tmp\\git-cloneuwf27x\\node_modules\\optipng-bin' npm ERR! npm WARN cleanup } npm ERR! npm WARN cleanup ], npm ERR! npm WARN cleanup [ npm ERR! npm WARN cleanup 'D:\\Program Files\\nodejs\\node_cache\\_cacache\\tmp\\git-cloneuwf27x\\node_modules\\cwebp-bin', npm ERR! npm WARN cleanup [Error: EBUSY: resource busy or locked, rmdir 'D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\cwebp-bin'] { npm ERR! npm WARN cleanup errno: -4082, npm ERR! npm WARN cleanup code: 'EBUSY', npm ERR! npm WARN cleanup syscall: 'rmdir', npm ERR! npm WARN cleanup path: 'D:\\Program Files\\nodejs\\node_cache\\_cacache\\tmp\\git-cloneuwf27x\\node_modules\\cwebp-bin' npm ERR! npm WARN cleanup } npm ERR! npm WARN cleanup ], npm ERR! npm WARN cleanup [ npm ERR! npm WARN cleanup 'D:\\Program Files\\nodejs\\node_cache\\_cacache\\tmp\\git-cloneuwf27x\\node_modules\\gifsicle', npm ERR! npm WARN cleanup [Error: EBUSY: resource busy or locked, rmdir 'D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\gifsicle'] { npm ERR! npm WARN cleanup errno: -4082, npm ERR! npm WARN cleanup code: 'EBUSY', npm ERR! npm WARN cleanup syscall: 'rmdir', npm ERR! npm WARN cleanup path: 'D:\\Program Files\\nodejs\\node_cache\\_cacache\\tmp\\git-cloneuwf27x\\node_modules\\gifsicle' npm ERR! npm WARN cleanup } npm ERR! npm WARN cleanup ], npm ERR! npm WARN cleanup [ npm ERR! npm WARN cleanup 'D:\\Program Files\\nodejs\\node_cache\\_cacache\\tmp\\git-cloneuwf27x\\node_modules\\pngquant-bin', npm ERR! npm WARN cleanup [Error: EBUSY: resource busy or locked, rmdir 'D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\pngquant-bin'] { npm ERR! npm WARN cleanup errno: -4082, npm ERR! npm WARN cleanup code: 'EBUSY', npm ERR! npm WARN cleanup syscall: 'rmdir', npm ERR! npm WARN cleanup path: 'D:\\Program Files\\nodejs\\node_cache\\_cacache\\tmp\\git-cloneuwf27x\\node_modules\\pngquant-bin' npm ERR! npm WARN cleanup } npm ERR! npm WARN cleanup ], npm ERR! npm WARN cleanup [ npm ERR! npm WARN cleanup 'D:\\Program Files\\nodejs\\node_cache\\_cacache\\tmp\\git-cloneuwf27x\\node_modules', npm ERR! npm WARN cleanup [Error: EBUSY: resource busy or locked, rmdir 'D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\cwebp-bin'] { npm ERR! npm WARN cleanup errno: -4082, npm ERR! npm WARN cleanup code: 'EBUSY', npm ERR! npm WARN cleanup syscall: 'rmdir', npm ERR! npm WARN cleanup path: 'D:\\Program Files\\nodejs\\node_cache\\_cacache\\tmp\\git-cloneuwf27x\\node_modules\\cwebp-bin' npm ERR! npm WARN cleanup } npm ERR! npm WARN cleanup ], npm ERR! npm WARN cleanup [ npm ERR! npm WARN cleanup 'D:\\Program Files\\nodejs\\node_cache\\_cacache\\tmp\\git-cloneuwf27x\\node_modules\\@babel\\polyfill', npm ERR! npm WARN cleanup [Error: EPERM: operation not permitted, rmdir 'D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\@babel\polyfill'] { npm ERR! npm WARN cleanup errno: -4048, npm ERR! npm WARN cleanup code: 'EPERM', npm ERR! npm WARN cleanup syscall: 'rmdir', npm ERR! npm WARN cleanup path: 'D:\\Program Files\\nodejs\\node_cache\\_cacache\\tmp\\git-cloneuwf27x\\node_modules\\@babel\\polyfill' npm ERR! npm WARN cleanup } npm ERR! npm WARN cleanup ] npm ERR! npm WARN cleanup ] npm ERR! npm ERR! code 1 npm ERR! npm ERR! path D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\node-sass npm ERR! npm ERR! command failed npm ERR! npm ERR! command C:\WINDOWS\system32\cmd.exe /d /s /c node scripts/build.js npm ERR! npm ERR! Building: D:\Program Files\nodejs\node.exe D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\node-gyp\bin\node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library= npm ERR! npm ERR! �ڴ˽��������һ������һ����Ŀ����Ҫ���ò������ɣ������ӡ�/m�����ء� npm ERR! npm ERR! ��������ʱ��Ϊ 2025/5/27 15:48:02�� npm ERR! npm ERR! �ڵ� 1 �ϵ���Ŀ��D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\node-sass\build\binding.sln��(Ĭ��Ŀ��)�� npm ERR! npm ERR! ValidateSolutionConfiguration: npm ERR! npm ERR! �������ɽ���������á�Release|x64���� npm ERR! npm ERR! MSBUILD : error MSB3428: δ�ܼ��� Visual C++ �����VCBuild.exe����Ҫ��������⣬1) ��װ .NET Framework 2.0 SDK��2) ��װ Microsoft Visual Studio 2005���� 3) ������������װ��������λ�ã��뽫��λ�����ӵ�ϵͳ·���С� [D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\node-sass\build\binding.sln] npm ERR! npm ERR! �����������Ŀ��D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\node-sass\build\binding.sln��(Ĭ��Ŀ��)�IJ��� - ʧ�ܡ� npm ERR! npm ERR! npm ERR! npm ERR! ����ʧ�ܡ� npm ERR! npm ERR! npm ERR! npm ERR! ��D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\node-sass\build\binding.sln��(Ĭ��Ŀ��) (1) -> npm ERR! npm ERR! (_src_\libsass Ŀ��) -> npm ERR! npm ERR! MSBUILD : error MSB3428: δ�ܼ��� Visual C++ �����VCBuild.exe����Ҫ��������⣬1) ��װ .NET Framework 2.0 SDK��2) ��װ Microsoft Visual Studio 2005���� 3) ������������װ��������λ�ã��뽫��λ�����ӵ�ϵͳ·���С� [D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\node-sass\build\binding.sln] npm ERR! npm ERR! npm ERR! npm ERR! 0 ������ npm ERR! npm ERR! 1 ������ npm ERR! npm ERR! npm ERR! npm ERR! ����ʱ�� 00:00:00.40 npm ERR! npm ERR! gyp info it worked if it ends with ok npm ERR! npm ERR! gyp verb cli [ npm ERR! npm ERR! gyp verb cli 'D:\\Program Files\\nodejs\\node.exe', npm ERR! npm ERR! gyp verb cli 'D:\\Program Files\\nodejs\\node_cache\\_cacache\\tmp\\git-cloneuwf27x\\node_modules\\node-gyp\\bin\\node-gyp.js', npm ERR! npm ERR! gyp verb cli 'rebuild', npm ERR! npm ERR! gyp verb cli '--verbose', npm ERR! npm ERR! gyp verb cli '--libsass_ext=', npm ERR! npm ERR! gyp verb cli '--libsass_cflags=', npm ERR! npm ERR! gyp verb cli '--libsass_ldflags=', npm ERR! npm ERR! gyp verb cli '--libsass_library=' npm ERR! npm ERR! gyp verb cli ] npm ERR! npm ERR! gyp info using [email protected] npm ERR! npm ERR! gyp info using [email protected] | win32 | x64 npm ERR! npm ERR! gyp verb command rebuild [] npm ERR! npm ERR! gyp verb command clean [] npm ERR! npm ERR! gyp verb clean removing "build" directory npm ERR! npm ERR! gyp verb command configure [] npm ERR! npm ERR! gyp verb check python checking for Python executable "python2" in the PATH npm ERR! npm ERR! gyp verb which failed Error: not found: python2 npm ERR! npm ERR! gyp verb which failed at getNotFoundError (D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\node-gyp\node_modules\which\which.js:13:12) npm ERR! npm ERR! gyp verb which failed at F (D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\node-gyp\node_modules\which\which.js:68:19) npm ERR! npm ERR! gyp verb which failed at E (D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\node-gyp\node_modules\which\which.js:80:29) npm ERR! npm ERR! gyp verb which failed at D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\node-gyp\node_modules\which\which.js:89:16 npm ERR! npm ERR! gyp verb which failed at D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\isexe\index.js:42:5 npm ERR! npm ERR! gyp verb which failed at D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\isexe\windows.js:36:5 npm ERR! npm ERR! gyp verb which failed at FSReqCallback.oncomplete (fs.js:192:21) npm ERR! npm ERR! gyp verb which failed python2 Error: not found: python2 npm ERR! npm ERR! gyp verb which failed at getNotFoundError (D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\node-gyp\node_modules\which\which.js:13:12) npm ERR! npm ERR! gyp verb which failed at F (D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\node-gyp\node_modules\which\which.js:68:19) npm ERR! npm ERR! gyp verb which failed at E (D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\node-gyp\node_modules\which\which.js:80:29) npm ERR! npm ERR! gyp verb which failed at D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\node-gyp\node_modules\which\which.js:89:16 npm ERR! npm ERR! gyp verb which failed at D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\isexe\index.js:42:5 npm ERR! npm ERR! gyp verb which failed at D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\isexe\windows.js:36:5 npm ERR! npm ERR! gyp verb which failed at FSReqCallback.oncomplete (fs.js:192:21) { npm ERR! npm ERR! gyp verb which failed code: 'ENOENT' npm ERR! npm ERR! gyp verb which failed } npm ERR! npm ERR! gyp verb check python checking for Python executable "python" in the PATH npm ERR! npm ERR! gyp verb which succeeded python D:\Python27\python.EXE npm ERR! npm ERR! gyp verb check python version D:\Python27\python.EXE -c "import sys; print "2.7.0 npm ERR! npm ERR! gyp verb check python version .%s.%s" % sys.version_info[:3];" returned: %j npm ERR! npm ERR! gyp verb get node dir no --target version specified, falling back to host node version: 14.20.0 npm ERR! npm ERR! gyp verb command install [ '14.20.0' ] npm ERR! npm ERR! gyp verb install input version string "14.20.0" npm ERR! npm ERR! gyp verb install installing version: 14.20.0 npm ERR! npm ERR! gyp verb install --ensure was passed, so won't reinstall if already installed npm ERR! npm ERR! gyp verb install version is already installed, need to check "installVersion" npm ERR! npm ERR! gyp verb got "installVersion" 9 npm ERR! npm ERR! gyp verb needs "installVersion" 9 npm ERR! npm ERR! gyp verb install version is good npm ERR! npm ERR! gyp verb get node dir target node version installed: 14.20.0 npm ERR! npm ERR! gyp verb build dir attempting to create "build" dir: D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\node-sass\build npm ERR! npm ERR! gyp verb build dir "build" dir needed to be created? D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\node-sass\build npm ERR! npm ERR! gyp verb Not using VS2017: Could not use PowerShell to find VS2017 npm ERR! npm ERR! gyp verb build/config.gypi creating config file npm ERR! npm ERR! gyp verb build/config.gypi writing out config file: D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\node-sass\build\config.gypi npm ERR! npm ERR! gyp verb config.gypi checking for gypi file: D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\node-sass\config.gypi npm ERR! npm ERR! gyp verb common.gypi checking for gypi file: D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\node-sass\common.gypi npm ERR! npm ERR! gyp verb gyp gyp format was not specified; forcing "msvs" npm ERR! npm ERR! gyp info spawn D:\Python27\python.EXE npm ERR! npm ERR! gyp info spawn args [ npm ERR! npm ERR! gyp info spawn args 'D:\\Program Files\\nodejs\\node_cache\\_cacache\\tmp\\git-cloneuwf27x\\node_modules\\node-gyp\\gyp\\gyp_main.py', npm ERR! npm ERR! gyp info spawn args 'binding.gyp', npm ERR! npm ERR! gyp info spawn args '-f', npm ERR! npm ERR! gyp info spawn args 'msvs', npm ERR! npm ERR! gyp info spawn args '-G', npm ERR! npm ERR! gyp info spawn args 'msvs_version=auto', npm ERR! npm ERR! gyp info spawn args '-I', npm ERR! npm ERR! gyp info spawn args 'D:\\Program Files\\nodejs\\node_cache\\_cacache\\tmp\\git-cloneuwf27x\\node_modules\\node-sass\\build\\config.gypi', npm ERR! npm ERR! gyp info spawn args '-I', npm ERR! npm ERR! gyp info spawn args 'D:\\Program Files\\nodejs\\node_cache\\_cacache\\tmp\\git-cloneuwf27x\\node_modules\\node-gyp\\addon.gypi', npm ERR! npm ERR! gyp info spawn args '-I', npm ERR! npm ERR! gyp info spawn args 'C:\\Users\\23969\\.node-gyp\\14.20.0\\include\\node\\common.gypi', npm ERR! npm ERR! gyp info spawn args '-Dlibrary=shared_library', npm ERR! npm ERR! gyp info spawn args '-Dvisibility=default', npm ERR! npm ERR! gyp info spawn args '-Dnode_root_dir=C:\\Users\\23969\\.node-gyp\\14.20.0', npm ERR! npm ERR! gyp info spawn args '-Dnode_gyp_dir=D:\\Program Files\\nodejs\\node_cache\\_cacache\\tmp\\git-cloneuwf27x\\node_modules\\node-gyp', npm ERR! npm ERR! gyp info spawn args '-Dnode_lib_file=C:\\Users\\23969\\.node-gyp\\14.20.0\\<(target_arch)\\node.lib', npm ERR! npm ERR! gyp info spawn args '-Dmodule_root_dir=D:\\Program Files\\nodejs\\node_cache\\_cacache\\tmp\\git-cloneuwf27x\\node_modules\\node-sass', npm ERR! npm ERR! gyp info spawn args '-Dnode_engine=v8', npm ERR! npm ERR! gyp info spawn args '--depth=.', npm ERR! npm ERR! gyp info spawn args '--no-parallel', npm ERR! npm ERR! gyp info spawn args '--generator-output', npm ERR! npm ERR! gyp info spawn args 'D:\\Program Files\\nodejs\\node_cache\\_cacache\\tmp\\git-cloneuwf27x\\node_modules\\node-sass\\build', npm ERR! npm ERR! gyp info spawn args '-Goutput_dir=.' npm ERR! npm ERR! gyp info spawn args ] npm ERR! npm ERR! Warning: unrecognized setting VCCLCompilerTool/MultiProcessorCompilation npm ERR! npm ERR! Warning: unrecognized setting VCCLCompilerTool/MultiProcessorCompilation npm ERR! npm ERR! Warning: unrecognized setting VCCLCompilerTool/MultiProcessorCompilation npm ERR! npm ERR! Warning: unrecognized setting VCCLCompilerTool/MultiProcessorCompilation npm ERR! npm ERR! gyp verb command build [] npm ERR! npm ERR! gyp verb build type Release npm ERR! npm ERR! gyp verb architecture x64 npm ERR! npm ERR! gyp verb node dev dir C:\Users\23969\.node-gyp\14.20.0 npm ERR! npm ERR! gyp verb found first Solution file build/binding.sln npm ERR! npm ERR! gyp verb could not find "msbuild.exe" in PATH - finding location in registry npm ERR! npm ERR! gyp info spawn C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe npm ERR! npm ERR! gyp info spawn args [ npm ERR! npm ERR! gyp info spawn args 'build/binding.sln', npm ERR! npm ERR! gyp info spawn args '/nologo', npm ERR! npm ERR! gyp info spawn args '/p:Configuration=Release;Platform=x64' npm ERR! npm ERR! gyp info spawn args ] npm ERR! npm ERR! gyp ERR! build error npm ERR! npm ERR! gyp ERR! stack Error: C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe failed with exit code: 1 npm ERR! npm ERR! gyp ERR! stack at ChildProcess.onExit (D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\node-gyp\lib\build.js:262:23) npm ERR! npm ERR! gyp ERR! stack at ChildProcess.emit (events.js:400:28) npm ERR! npm ERR! gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:285:12) npm ERR! npm ERR! gyp ERR! System Windows_NT 10.0.26100 npm ERR! npm ERR! gyp ERR! command "D:\\Program Files\\nodejs\\node.exe" "D:\\Program Files\\nodejs\\node_cache\\_cacache\\tmp\\git-cloneuwf27x\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library=" npm ERR! npm ERR! gyp ERR! cwd D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\node-sass npm ERR! npm ERR! gyp ERR! node -v v14.20.0 npm ERR! npm ERR! gyp ERR! node-gyp -v v3.8.0 npm ERR! npm ERR! gyp ERR! not ok npm ERR! npm ERR! Build failed with error code: 1

最新推荐

recommend-type

软件测试和质量保证行业技术趋势分析.pptx

软件测试和质量保证行业技术趋势分析.pptx
recommend-type

WEB精确打印技术:教你实现无差错打印输出

根据给定文件信息,本篇将深入探讨实现Web精确打印的技术细节和相关知识点。 Web精确打印是指在Web应用中实现用户可以按需打印网页内容,并且在纸张上能够保持与屏幕上显示相同的布局、格式和尺寸。要实现这一目标,需要从页面设计、CSS样式、打印脚本以及浏览器支持等方面进行周密的考虑和编程。 ### 页面设计 1. **布局适应性**:设计时需要考虑将网页布局设计成可适应不同尺寸的打印纸张,这意味着通常需要使用灵活的布局方案,如响应式设计框架。 2. **内容选择性**:在网页上某些内容可能是为了在屏幕上阅读而设计,这不一定适合打印。因此,需要有选择性地为打印版本设计内容,避免打印无关元素,如广告、导航栏等。 ### CSS样式 1. **CSS媒体查询**:通过媒体查询,可以为打印版和屏幕版定义不同的样式。例如,在CSS中使用`@media print`来设置打印时的背景颜色、边距等。 ```css @media print { body { background-color: white; color: black; } nav, footer, header, aside { display: none; } } ``` 2. **避免分页问题**:使用CSS的`page-break-after`, `page-break-before`和`page-break-inside`属性来控制内容的分页问题。 ### 打印脚本 1. **打印预览**:通过JavaScript实现打印预览功能,可以在用户点击打印前让他们预览将要打印的页面,以确保打印结果符合预期。 2. **触发打印**:使用JavaScript的`window.print()`方法来触发用户的打印对话框。 ```javascript document.getElementById('print-button').addEventListener('click', function() { window.print(); }); ``` ### 浏览器支持 1. **不同浏览器的兼容性**:需要考虑不同浏览器对打印功能的支持程度,确保在主流浏览器上都能获得一致的打印效果。 2. **浏览器设置**:用户的浏览器设置可能会影响打印效果,例如,浏览器的缩放设置可能会改变页面的打印尺寸。 ### 实践技巧 1. **使用辅助工具类**:如Bootstrap等流行的前端框架中包含了专门用于打印的样式类,可以在设计打印页面时利用这些工具快速实现布局的调整。 2. **测试打印**:在不同的打印机和纸张尺寸上测试打印结果,确保在所有目标打印环境下都有良好的兼容性和效果。 3. **优化图片和图形**:确保所有用于打印的图片和图形都有足够的分辨率,且在打印时不会因为尺寸缩小而失真。 4. **使用打印样式表**:创建一个专门的打印样式表(print.css),并将其链接到HTML文档的`<link>`标签中。这样可以在打印时引用独立的CSS文件,实现对打印内容的精细控制。 ### 总结 Web精确打印的实现涉及到前端设计和开发的多个方面,从设计、样式的编写到JavaScript脚本的运用,都需要紧密配合。开发者需要具备对打印技术深刻的理解,并且能够熟练使用现代前端技术来达到精确打印的要求。通过上述的知识点介绍,可以为开发者提供一个全面的指导,帮助他们在Web项目中实现高质量的打印输出。
recommend-type

【性能测试基准】:为RK3588选择合适的NVMe性能测试工具指南

# 1. NVMe性能测试基础 ## 1.1 NVMe协议简介 NVMe,全称为Non-Volatile Memory Express,是专为固态驱动器设计的逻辑设备接口规范。与传统的SATA接口相比,NVMe通过使用PCI Express(PCIe)总线,大大提高了存储设备的数据吞吐量和IOPS(每秒输入输出操作次数),特别适合于高速的固态存储设备。
recommend-type

服务器无感部署

<think>首先,用户的问题是:“我想在不引起服务中断的情况下进行服务器部署请问如何实现服务器无感部署无需停机的部署方法”。这涉及到零停机部署,确保服务在更新过程中不间断。我需要参考提供的引用:-引用[1]:讨论了Web服务的无缝更新,强调零停机部署的重要性。 -引用[2]:提供了自动化运维中零停机构建与部署的实践,包括命令示例。 -引用[3]:描述了无感知部署方案,如蓝绿部署。 -引用[4]:提到了负载均衡和服务器横向分布的重要性。系统级指令:-所有行内数学表达式使用$...$格式。-独立公式使用$$...$$格式并单独成段。 -LaTeX语法正确。-使用中文回答。-生成相关问题。 -在回
recommend-type

C++源代码实现:分段线性插值与高斯消去法

根据提供的文件信息,我们可以详细解析和讨论标题和描述中涉及的知识点。以下内容将围绕“计算方法C++源代码”这一主题展开,重点介绍分段线性插值、高斯消去法、改进的EULAR方法和拉格朗日法的原理、应用场景以及它们在C++中的实现。 ### 分段线性插值(Piecewise Linear Interpolation) 分段线性插值是一种基本的插值方法,用于在一组已知数据点之间估算未知值。它通过在相邻数据点间画直线段来构建一个连续函数。这种方法适用于任何连续性要求不高的场合,如图像处理、计算机图形学以及任何需要对离散数据点进行估算的场景。 在C++中,分段线性插值的实现通常涉及到两个数组,一个存储x坐标值,另一个存储y坐标值。通过遍历这些点,我们可以找到最接近待求点x的两个数据点,并在这两点间进行线性插值计算。 ### 高斯消去法(Gaussian Elimination) 高斯消去法是一种用于解线性方程组的算法。它通过行操作将系数矩阵化为上三角矩阵,然后通过回代求解每个未知数。高斯消去法是数值分析中最基本的算法之一,广泛应用于工程计算、物理模拟等领域。 在C++实现中,高斯消去法涉及到对矩阵的操作,包括行交换、行缩放和行加减。需要注意的是,算法在实施过程中可能遇到数值问题,如主元为零或非常接近零的情况,因此需要采用适当的措施,如部分或完全选主元技术,以确保数值稳定性。 ### 改进的EULAR方法 EULAR方法通常是指用于解决非线性动力学系统的数值积分方法,尤其是在动力系统的仿真中应用广泛。但在这里可能是指对Euler方法的某种改进。Euler方法是一种简单的单步求解初值问题的方法,适用于求解常微分方程的初值问题。 Euler方法的基本思想是利用当前点的导数信息来预测下一个点的位置,进而迭代求解整个系统。在C++实现中,通常需要定义一个函数来描述微分方程,然后根据这个函数和步长进行迭代计算。 ### 拉格朗日法(Lagrange Interpolation) 拉格朗日插值法是一种多项式插值方法,它构建一个最高次数不超过n-1的多项式,使得这个多项式在n个已知数据点的值与这些点的已知值相等。拉格朗日插值法适用于数据点数量较少,且对插值精度要求较高的情况。 在C++中,实现拉格朗日插值法需要计算每个基多项式的值并将其乘以对应的已知函数值,然后将这些多项式相加得到最终的插值多项式。这一过程可能会涉及到大量计算,尤其是当数据点数量增多时。 ### 源代码文件列表 - 计算方法代码 虽然文件列表仅提供了“计算方法代码”这一名称,我们可以推断,压缩包中包含了上述所有计算方法的C++源代码文件。每个文件可能对应一个算法的实现,例如,可能会有一个名为“GaussianElimination.cpp”的文件专门用于实现高斯消去法。 ### 结论 文件信息指出,压缩包内包含了一系列计算方法的C++源代码,包括分段线性插值、高斯消去法、改进的EULAR方法和拉格朗日法等。这些方法在数值分析和科学计算领域扮演着重要的角色,它们各自的C++实现展现了程序员在面对不同类型问题时所采取的算法策略和编程技巧。这些代码对于理解算法原理和将其应用到实际问题中是非常有价值的资源。
recommend-type

【固态硬盘寿命延长】:RK3588平台NVMe维护技巧大公开

# 1. 固态硬盘寿命延长的基础知识 ## 1.1 固态硬盘的基本概念 固态硬盘(SSD)是现代计算设备中不可或缺的存储设备之一。与传统的机械硬盘(HDD)相比,SSD拥有更快的读写速度、更小的体积和更低的功耗。但是,SSD也有其生命周期限制,主要受限于NAND闪存的写入次数。 ## 1.2 SSD的写入次数和寿命 每块SSD中的NAND闪存单元都有有限的写入次数。这意味着,随着时间的推移,SSD的
recommend-type

代码解释 ```cpp LinkList tail = L; // 尾指针指向头结点 ```

<think>我们分析代码行:`LinkList tail= L;//尾指针指向头结点`在完整的代码中,这段代码位于创建头结点之后,尾插法创建链表之前。功能和作用:1.定义了一个LinkList类型的指针变量tail,并将其初始化为指向头结点L。2.注释说明“尾指针指向头结点”,这意味着tail将作为链表尾部的指针,在尾插法构建链表时用于跟踪当前链表的最后一个节点。3.在后续的尾插法循环中,每次添加新节点时,都会将新节点链接到tail所指向的节点(即当前尾节点)的后面,然后更新tail指向这个新节点,以保持tail始终指向链表的最后一个节点。4.这样做的目的是为了提高链表构建的效率。因为如果不
recommend-type

VC摄像头远程控制与图像采集传输技术

从提供的文件信息中,我们可以提取出关于VC(Visual C++)环境下对摄像头的控制,图像采集,编解码过程以及远程传输的关键知识点。接下来,我将对这些知识点进行详细的解释和阐述。 ### VC摄像头控制 在VC环境中,对摄像头进行控制通常涉及Windows API函数调用或者第三方库的使用。开发者可以通过调用DirectShow API或者使用OpenCV等图像处理库来实现摄像头的控制和图像数据的捕获。这包括初始化摄像头设备,获取设备列表,设置和查询摄像头属性,以及实现捕获图像的功能。 ### 图像的采集 图像采集是指利用摄像头捕获实时图像或者视频的过程。在VC中,可以使用DirectShow SDK中的Capture Graph Builder和Sample Grabber Filter来实现从摄像头捕获视频流,并进行帧到帧的操作。另外,OpenCV库提供了非常丰富的函数用于图像采集,包括VideoCapture类来读取视频文件或者摄像头捕获的视频流。 ### 编解码过程 编解码过程是指将采集到的原始图像数据转换成适合存储或传输的格式(编码),以及将这种格式的数据还原成图像(解码)的过程。在VC中,可以使用如Media Foundation、FFmpeg、Xvid等库进行视频数据的编码与解码工作。这些库能够支持多种视频编解码标准,如H.264、MPEG-4、AVI、WMV等。编解码过程通常涉及对压缩效率与图像质量的权衡选择。 ### 远程传输 远程传输指的是将编码后的图像数据通过网络发送给远程接收方。这在VC中可以通过套接字编程(Socket Programming)实现。开发者需要配置服务器和客户端,使用TCP/IP或UDP协议进行数据传输。传输过程中可能涉及到数据包的封装、发送、接收确认、错误检测和重传机制。更高级的传输需求可能会用到流媒体传输协议如RTSP或HTTP Live Streaming(HLS)。 ### 关键技术实现 1. **DirectShow技术:** DirectShow是微软提供的一个用于处理多媒体流的API,它包含了一系列组件用于视频捕获、音频捕获、文件读写、流媒体处理等功能。在VC环境下,利用DirectShow可以方便地进行摄像头控制和图像数据的采集工作。 2. **OpenCV库:** OpenCV是一个开源的计算机视觉和机器学习软件库。它提供了许多常用的图像处理函数和视频处理接口,以及强大的图像采集功能。在VC中,通过包含OpenCV库,开发者可以快速实现图像的采集和处理。 3. **编解码库:** 除了操作系统自带的编解码技术外,第三方库如FFmpeg是视频处理领域极为重要的工具。它支持几乎所有格式的音视频编解码,是一个非常强大的多媒体框架。 4. **网络编程:** 在VC中进行网络编程,主要涉及到Windows Sockets API。利用这些API,可以创建数据包的发送和接收,进而实现远程通信。 5. **流媒体协议:** 实现远程视频传输时,开发者可能会使用到RTSP、RTMP等流媒体协议。这些协议专门用于流媒体数据的网络传输,能够提供稳定和实时的传输服务。 ### 结语 文件标题《VC摄像头控制.图像得采集以及远程传输等》所涉及的内容是多方面的,涵盖了图像处理与传输的多个关键步骤,包括摄像头控制、图像采集、视频编解码以及网络传输。对于希望在VC环境下进行视频处理开发的工程师而言,了解上述技术细节至关重要。只有掌握了这些知识点,才能设计出稳定、高效的视频处理及传输系统。希望本篇内容能够为从事相关工作或学习的朋友们提供有益的参考与帮助。
recommend-type

【故障恢复策略】:RK3588与NVMe固态硬盘的容灾方案指南

# 1. RK3588处理器与NVMe固态硬盘的概述 ## 1.1 RK3588处理器简介 RK3588是Rockchip推出的一款高端处理器,具备强大的性能和多样的功能,集成了八核CPU和六核GPU,以及专用的AI处理单元,主要用于高端移动设备、边缘计算和
recommend-type

代码解释 ```cpp LinkList L = (LinkList)malloc(sizeof(LNode)); ```

<think>我们分析给定的代码行:`LinkListL =(LinkList)malloc(sizeof(LNode));`这段代码位于main函数中,是创建单链表的第一步:创建头结点。具体分析如下:1.`malloc(sizeof(LNode))`:动态分配内存,大小为LNode结构体的大小。2. `(LinkList)`:将malloc返回的void*指针强制转换为LinkList类型(即LNode*类型)。3.`LinkList L`:声明一个LinkList类型的指针变量L,并将malloc分配的内存地址赋给L。功能:创建链表的头结点。头结点不存储实际数据,其next指针指向链表的第