Project

General

Profile

Feature #1878

Updated by Alexander Watzinger over 1 year ago

Like discussed I tried today to use it following the installation instructions and encountered multiple issues on a Debian machine. I noted them all down here but likely later problems were caused by earlier ones: 

 * yarn install 
 ** command wasn't found so I installed it as root with *apt apt install yarn* yarn 
 ** I tried it again and this time I got the error: 
 <pre> 
 00h00m00s 0/0: : ERROR: [Errno 2] No such file or directory: 'install' 
 </pre> 

 * npm install 
 <pre> 
 ** I got a lot of *Unsupported engine* warnings but seem to have worked otherwise: 
 <pre> 
  added 816 packages, and audited 817 packages in 15s 
 </pre> 

 * pnpm install --shamefully-hoist 
 ** First I got *pnpm: command not found*, after searching in the web I executed *npm install -g pnpm* 
 ** After that I could run the command but got this error 
 <pre> 
 ERROR: This version of pnpm requires at least Node.js v14.6 
 The current version of Node.js is v12.22.12 
 </pre> 

 * npm run build 
 ** There I got this error: 
 <pre> 
 (node:27769) UnhandledPromiseRejectionWarning: SyntaxError: Unexpected token '.' 
     at Loader.moduleStrategy (internal/modules/esm/translators.js:133:18) 
 (node:27769) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1) 
 (node:27769) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. 
 </pre> 

 * Other issues with the git repository 
 ** *package-lock.json* and *package.json* are now showing up as modified 

Back