Here's the complete error log occurs on Windows.
Screenshots:
![CM~8([email protected]]F~36]U8.png](https://i.imgur.com/ccs4Yq0.png)
![CM~8([email protected]]F~36]U8.png](https://i.imgur.com/TsXwusY.png)
Log text:
Dependencies outdated or not yet installed.
Installing them now...
npm WARN deprecated [email protected]: [email protected]<3 is no longer maintained and not recommended for usage due to the number of iss
ues. Please, upgrade your dependencies to the actual version of [email protected]
npm ERR! code 128
npm ERR! Command failed: git clone --mirror -q git://github.com/thomaspark/bootswatch.git C:\Users\huawei\AppData\Roaming\npm
-cache_cacache\tmp\git-clone-3825054a.git --config core.longpaths=true
npm ERR! warning: templates not found in C:\Users\huawei\AppData\Local\Temp\pacote-git-template-tmp\git-clone-fd3314bb
npm ERR! fatal: read error: Invalid argument
npm ERR! fatal: early EOF
npm ERR! fatal: index-pack failed
npm ERR!
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\huawei\AppData\Roaming\npm-cache_logs\2020-06-13T03_49_30_961Z-debug.log
Error installing dependencies!
message: Command failed: npm install --production
stdout: null
stderr: null
D:\Coding\Web_Project\NodeBB-v1.14.x\src\cli\package-install.js:72
throw e;
^
Error: Command failed: npm install --production
at checkExecSyncError (child_process.js:630:11)
at Object.execSync (child_process.js:666:15)
at Object.installAll (D:\Coding\Web_Project\NodeBB-v1.14.x\src\cli\package-install.js:63:9)
at Object.<anonymous> (D:\Coding\Web_Project\NodeBB-v1.14.x\src\cli\index.js:60:18)
at Module._compile (internal/modules/cjs/loader.js:1138:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1158:10)
at Module.load (internal/modules/cjs/loader.js:986:32)
at Function.Module._load (internal/modules/cjs/loader.js:879:14)
at Module.require (internal/modules/cjs/loader.js:1026:19)
at require (internal/modules/cjs/helpers.js:72:18) {
status: 1,
signal: null,
output: [ null, null, null ],
pid: 552,
stdout: null,
stderr: null
}
I suppose I can just forbid users from changing skins to bypass this error.
