I just tried to install nodeGame on a different machine than I’ve been using for development, and encountered a bunch of warnings and errors. This all seems like some sort of version skew, but I *think* I grabbed the latest nodeGame installer, and that I’m running an up to date version of node.js. This is on Ubuntu 18.04. I just created the directory /home/ddmlab/experiments/twobytwo/ so I don't think it can be a conflict with any previously installed version of nodeGame or anything like that. Any pointers to what I’m doing wrong?
Pasted below is what got spat to my terminal, and attached is the log file it cites.
Thanks
========================================================================
dfm@halle:/home/ddmlab/experiments/twobytwo$ node nodegame-installer.js
***********************************************
** WELCOME TO NODEGAME INSTALLER v6.2.4 **
***********************************************
nodeGame: fast, scalable JavaScript for online, large-scale,
multiplayer, real-time games and experiments in the browser.
creator: Stefano Balietti
website: https://nodegame.org
license: MIT
mail: in...@nodegame.org
twitter: @nodegameorg
bugs: https://github.com/nodeGame/nodegame/issues
forum: https://groups.google.com/forum/?fromgroups#!forum/nodegame
----------------------------------------------
node version: v14.10.1
nodeGame version: v6.2.4
install directory: /home/ddmlab/experiments/twobytwo/nodegame-v6.2.4
Downloading and installing nodeGame packages.
This might take a few minutes ◰
Oops! The following error/s occurred:
- npm WARN deprecated transf...@2.1.0: Deprecated, use jstransformer
npm WARN deprecated cryp...@2.0.5: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please
upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid
support is available for older versions (hapi.im/commercial).
npm WARN deprecated constan...@3.0.2: Please update to at least constantinople 3.1.1
npm WARN deprecated bo...@2.10.1: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upg
rade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid supp
ort is available for older versions (hapi.im/commercial).
npm WARN deprecated sn...@1.0.9: This module moved to @hapi/sntp. Please make sure to switch over as this distribution is no longer support
ed and may contain bugs and critical security issues.
npm WARN deprecated phan...@2.1.7: Package renamed to phantomjs-prebuilt. Please update 'phantomjs' package references to 'phantomjs-pre
built'
npm WARN deprecated tough-...@2.2.2: ReDoS vulnerability parsing Set-Cookie https://nodesecurity.io/advisories/130
npm WARN deprecated node...@1.4.8: Use uuid module instead
npm WARN deprecated mkd...@0.5.0: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surfa
ce has changed to use Promises in 1.x.)
npm WARN deprecated har-va...@5.1.5: this library is no longer supported
npm WARN deprecated har-va...@2.0.6: this library is no longer supported
npm WARN deprecated ho...@2.16.3: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upg
rade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid supp
ort is available for older versions (hapi.im/commercial).
npm WARN deprecated req...@2.88.0: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated req...@2.67.0: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated de...@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js e
nvironment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated de...@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js e
nvironment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated de...@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js e
nvironment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated ha...@3.1.3: This module moved to @hapi/hawk. Please make sure to switch over as this distribution is no longer support
ed and may contain bugs and critical security issues.
npm WARN deprecated ja...@1.11.0: Jade has been renamed to pug, please install the latest version of pug instead of jade
npm WARN deprecated cor...@2.6.12: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please,
upgrade your dependencies to the actual version of core-js@3.
npm ERR! code 1
npm ERR! path /home/ddmlab/experiments/twobytwo/node_modules/phantomjs
npm ERR! command failed
npm ERR! command sh -c node install.js
npm ERR! Considering PhantomJS found at /usr/bin/phantomjs
npm ERR! Found PhantomJS at /usr/bin/phantomjs ...verifying
npm ERR! Error verifying phantomjs, continuing Error: Command failed: /usr/bin/phantomjs --version
npm ERR! qt.qpa.screen: QXcbConnection: Could not connect to display
npm ERR! Could not connect to any X display.
npm ERR!
npm ERR! at ChildProcess.exithandler (child_process.js:308:12)
npm ERR! at ChildProcess.emit (events.js:314:20)
npm ERR! at maybeClose (internal/child_process.js:1047:16)
npm ERR! at Process.ChildProcess._handle.onexit (internal/child_process.js:287:5) {
npm ERR! killed: false,
npm ERR! code: 1,
npm ERR! signal: null,
npm ERR! cmd: '/usr/bin/phantomjs --version'
npm ERR! }
npm ERR! Phantom installation failed TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received undefined
npm ERR! at validateString (internal/validators.js:122:11)
npm ERR! at Object.join (path.js:1039:7)
npm ERR! at findSuitableTempDirectory (/home/ddmlab/experiments/twobytwo/node_modules/phantomjs/install.js:127:30)
npm ERR! at /home/ddmlab/experiments/twobytwo/node_modules/phantomjs/install.js:476:19
npm ERR! at nextTickCallback (/home/ddmlab/experiments/twobytwo/node_modules/kew/kew.js:47:28)
npm ERR! at processTicksAndRejections (internal/process/task_queues.js:75:11) {
npm ERR! code: 'ERR_INVALID_ARG_TYPE'
npm ERR! } TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received undefined
npm ERR! at validateString (internal/validators.js:122:11)
npm ERR! at Object.join (path.js:1039:7)
npm ERR! at findSuitableTempDirectory (/home/ddmlab/experiments/twobytwo/node_modules/phantomjs/install.js:127:30)
npm ERR! at /home/ddmlab/experiments/twobytwo/node_modules/phantomjs/install.js:476:19
npm ERR! at nextTickCallback (/home/ddmlab/experiments/twobytwo/node_modules/kew/kew.js:47:28)
npm ERR! at processTicksAndRejections (internal/process/task_queues.js:75:11)
npm ERR! A complete log of this run can be found in:
npm ERR! /home/dfm/.npm/_logs/2021-03-24T13_17_23_811Z-debug.log
Installation did not complete successfully.
----------------------------------------------
If you think this might be a bug, please report it. You can either:
- open an issue at: https://github.com/nodeGame/nodegame/issues
- send an email to in...@nodegame.org
dfm@halle:/home/ddmlab/experiments/twobytwo$ node --version
v14.10.1
dfm@halle:/home/ddmlab/experiments/twobytwo$ npm --version
7.7.0
dfm@halle:/home/ddmlab/experiments/twobytwo$
--
Don Morrison <
df...@cmu.edu>
“Styles change less readily in building than in decoration, for the
requirements of stability are less fluid than the tides of taste.”
– Will and Ariel Durant, /The Age of Voltaire/