我正在尝试在 Ubuntu 20.04 上安装 wetty，但遇到了一些问题。运行命令时，我收到很多警告和错误npm install。我找到的所有指南都与旧版本的 Ubuntu 有关。Ubuntu 20.04 支持 wetty 吗？
以下是错误。
root@coral:~# node -v
v10.19.0
root@coral:~# npm -v
6.14.4
root@coral:~# git clone https://github.com/krishnasrinivas/wetty
Cloning into 'wetty'...
remote: Enumerating objects: 2233, done.
remote: Counting objects: 100% (345/345), done.
remote: Compressing objects: 100% (283/283), done.
remote: Total 2233 (delta 158), reused 160 (delta 56), pack-reused 1888
Receiving objects: 100% (2233/2233), 3.40 MiB | 6.31 MiB/s, done.
Resolving deltas: 100% (1163/1163), done.
root@coral:~# cd wetty
root@coral:~/wetty# npm install
npm WARN deprecated @types/[email protected]: This is a stub types definition. winston provides its own type definitions, so you do not need this installed.
npm WARN deprecated @types/[email protected]: This is a stub types definition.
socket.io-parser provides its own type definitions, so you do not need this installed.
npm WARN deprecated [email protected]: request-promise-native has been
deprecated because it extends the now deprecated request package, see https://github.com>/request/request/issues/3142
npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated [email protected]: this library is no longer supported
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 WARN deprecated [email protected]: "Please update to latest v2.3 or v2.2"
[email protected] install /root/wetty/node_modules/bufferutil
node-gyp-build
sh: 1: node-gyp-build: Permission denied
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.2 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN notsup Unsupported engine for [email protected]: wanted: {"node":">=12"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: [email protected]
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.1.2 (node_modules/rollup/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm ERR! code ELIFECYCLE
npm ERR! syscall spawn
npm ERR! file sh
npm ERR! errno ENOENT
npm ERR! [email protected] install: node-gyp-build
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the [email protected] install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2021-12-02T12_19_34_219Z-debug.log