Update Error

I’m a few versions behind and when I’m trying to update I’m running into several errors in the webportal. Updates to aresmush have applied as expected and is showing the correct (updated) version, the webportal however is still on the version prior to the updates being applied.


node_modules/.staging/lodash-182d6616/fp/zipObj.js’
npm WARN tar ENOENT: no such file or directory, open ‘/home/ares/ares-webportal/node_modules/.staging/lodash-91ddac05/fp/zipObj.js’
npm WARN tar ENOENT: no such file or directory, open ‘/home/ares/ares-webportal/node_modules/.staging/lodash-3a127d26/fp/zipObj.js’
npm WARN tar ENOENT: no such file or directory, open ‘/home/ares/ares-webportal/node_modules/.staging/lodash-99112ec6/fp/zipObj.js’
npm WARN tar ENOENT: no such file or directory, open ‘/home/ares/ares-webportal/node_modules/.staging/lodash-7ea1ed39/fp/zipObject.js’
npm WARN tar ENOENT: no such file or directory, open ‘/home/ares/ares-webportal/node_modules/.staging/lodash-24f66bf4/fp/zipObject.js’
npm WARN tar ENOENT: no such file or directory, open ‘/home/ares/ares-webportal/node_modules/.staging/lodash-8ec2808c/fp/zipObject.js’
npm WARN tar ENOENT: no such file or directory, open ‘/home/ares/ares-webportal/node_modules/.staging/lodash-0961690e/fp/zipObjectDeep.js’
npm WARN tar ENOENT: no such file or directory, open ‘/home/ares/ares-webportal/node_modules/.staging/lodash-182d6616/fp/zipObject.js’
npm WARN tar ENOENT: no such file or directory, open ‘/home/ares/ares-webportal/node_modules/.staging/lodash-91ddac05/fp/zipObject.js’
npm WARN tar ENOENT: no such file or directory, open ‘/home/ares/ares-webportal/node_modules/.staging/lodash-3a127d26/fp/zipObject.js’
npm WARN tar ENOENT: no such file or directory, open ‘/home/ares/ares-webportal/node_modules/.staging/lodash-99112ec6/fp/zipObject.js’
npm WARN tar ENOENT: no such file or directory, open ‘/home/ares/ares-webportal/node_modules/.staging/lodash-6e127e6c/fp/zipObjectDeep.js’
npm WARN tar ENOENT: no such file or directory, open ‘/home/ares/ares-webportal/node_modules/.staging/lodash-8bebc360/fp/zipObjectDeep.js’
npm WARN tar ENOENT: no such file or directory, open ‘/home/ares/ares-webportal/node_modules/.staging/lodash-7ea1ed39/fp/zipObjectDeep.js’
npm WARN tar ENOENT: no such file or directory, open ‘/home/ares/ares-webportal/node_modules/.staging/lodash-24f66bf4/fp/zipObjectDeep.js’
npm WARN tar ENOENT: no such file or directory, open ‘/home/ares/ares-webportal/node_modules/.staging/lodash-8ec2808c/fp/zipObjectDeep.js’
npm WARN tar ENOENT: no such file or directory, open ‘/home/ares/ares-webportal/node_modules/.staging/lodash-0961690e/fp/zipWith.js’
npm WARN tar ENOENT: no such file or directory, open ‘/home/ares/ares-webportal/node_modules/.staging/lodash-182d6616/fp/zipObjectDeep.js’
npm WARN tar ENOENT: no such file or directory, open ‘/home/ares/ares-webportal/node_modules/.staging/lodash-91ddac05/fp/zipObjectDeep.js’
npm WARN tar ENOENT: no such file or directory, open ‘/home/ares/ares-webportal/node_modules/.staging/lodash-3a127d26/fp/zipObjectDeep.js’
npm WARN tar ENOENT: no such file or directory, open ‘/home/ares/ares-webportal/node_modules/.staging/lodash-99112ec6/fp/zipObjectDeep.js’
npm WARN tar ENOENT: no such file or directory, open ‘/home/ares/ares-webportal/node_modules/.staging/lodash-6e127e6c/fp/zipWith.js’
npm WARN tar ENOENT: no such file or directory, open ‘/home/ares/ares-webportal/node_modules/.staging/lodash-8bebc360/fp/zipWith.js’
npm WARN tar ENOENT: no such file or directory, open ‘/home/ares/ares-webportal/node_modules/.staging/lodash-7ea1ed39/fp/zipWith.js’
npm WARN tar ENOENT: no such file or directory, open ‘/home/ares/ares-webportal/node_modules/.staging/lodash-24f66bf4/fp/zipWith.js’
npm WARN tar ENOENT: no such file or directory, open ‘/home/ares/ares-webportal/node_modules/.staging/lodash-8ec2808c/fp/zipWith.js’
npm WARN tar ENOENT: no such file or directory, open ‘/home/ares/ares-webportal/node_modules/.staging/lodash-182d6616/fp/zipWith.js’
npm WARN tar ENOENT: no such file or directory, open ‘/home/ares/ares-webportal/node_modules/.staging/lodash-91ddac05/fp/zipWith.js’
npm WARN tar ENOENT: no such file or directory, open ‘/home/ares/ares-webportal/node_modules/.staging/lodash-3a127d26/fp/zipWith.js’
npm WARN tar ENOENT: no such file or directory, open ‘/home/ares/ares-webportal/node_modules/.staging/lodash-99112ec6/fp/zipWith.js’

npm ERR! A complete log of this run can be found in:
npm ERR! /home/ares/.npm/_logs/2020-12-22T20_03_58_669Z-debug.log

Missing npm packages:
Package: @ember/optional-features

  • Specified: ^2.0.0
  • Installed: 1.3.0

Package: @glimmer/component

  • Specified: ^1.0.1
  • Installed: 1.0.0

Package: @glimmer/tracking

  • Specified: ^1.0.1
  • Installed: 1.0.0

Package: ember-auto-import

  • Specified: ^1.6.0
  • Installed: 1.5.3

Package: ember-cli

  • Specified: ~3.21.2
  • Installed: 3.18.0

Package: ember-cli-babel

  • Specified: ^7.22.1
  • Installed: 7.19.0

Package: ember-cli-flash

  • Specified: ^1.9.0
  • Installed: 1.8.1

Package: ember-cli-head

  • Specified: ^1.0.0
  • Installed: 0.4.1

Package: ember-cli-htmlbars

  • Specified: ^5.3.1
  • Installed: 4.3.1

Package: ember-cli-sass

  • Specified: ^10.0.1
  • Installed: 7.2.0

Package: ember-cli-terser

  • Specified: ^4.0.0
  • Installed: (not installed)

Package: ember-fetch

  • Specified: ^8.0.2
  • Installed: 8.0.1

Package: ember-page-title

  • Specified: ^6.0.1
  • Installed: 5.2.1

Package: ember-pikaday

  • Specified: ^3.0.0
  • Installed: 2.4.1

Package: ember-power-select

  • Specified: ^4.0.5
  • Installed: 2.3.5

Package: ember-resolver

  • Specified: ^8.0.2
  • Installed: 8.0.0

Package: ember-simple-auth

  • Specified: ^3.0.0
  • Installed: 1.9.2

Package: ember-source

  • Specified: ~3.21.1
  • Installed: 3.18.1

Package: ember-template-lint

  • Specified: ^2.11.0
  • Installed: 2.7.0

Package: ember-truth-helpers

  • Specified: ^3.0.0
  • Installed: 2.1.0

Package: eslint

  • Specified: ^7.8.0
  • Installed: 5.16.0

Package: eslint-plugin-ember

  • Specified: ^8.13.0
  • Installed: 8.5.1

Package: sass

  • Specified: ^1.27.0
  • Installed: (not installed)

Package: node-sass

  • Specified: ^4.14.1
  • Installed: 4.13.0

Package: elliptic

  • Specified: ^6.5.3
  • Installed: 6.5.1

Package: lodash

  • Specified: ^4.17.19
  • Installed: 4.17.15

Package: websocket-extensions

  • Specified: ^0.1.4
  • Installed: 0.1.3

Package: https-proxy-agent

  • Specified: ^2.2.4
  • Installed: (not installed)

Package: node-fetch

  • Specified: ^2.6.1
  • Installed: 2.6.0

Run npm install to install missing dependencies.

Stack Trace and Error Report: /tmp/error.dump.b50bbd601d5d0222043b3b986f238570.log
An error occurred in the constructor for ember-cli-dependency-checker at /home/ares/ares-webportal/node_modules/ember-cli-dependency-checker

AresMUSH started!

it looks like something went awry with the web portal installation. Try doing as it says and running “npm install” from the ares-webportal directory and see what happens. Always make sure to do everything with the “ares” user; never with root.

Same thing there. A bunch of npm WARN tar ENOENT messages.

npm WARN tar ENOENT: no such file or directory, open ‘/home/ares/ares-webportal/node_modules/.staging/ember-source-a813b36b/dist/packages/@ember/object/lib/computed/reduce_computed_macros.js’

npm ERR! A complete log of this run can be found in:
npm ERR! /home/ares/.npm/_logs/2020-12-23T00_59_23_772Z-debug.log
ares@Aurora:~/ares-webportal$

Try doing this:

cd ares-webportal
rm -rf node_modules
npm install
bin/deploy

Same thing. Bunch of npm WARN tar ENOENT errors when running ‘npm install’ after which the node_modules file is created but empty.

npm WARN tar ENOENT: no such file or directory, open ‘/home/ares/ares-webportal/node_modules/.staging/caniuse-lite-8ec193c7/data/features/es6.js’
npm WARN tar ENOENT: no such file or directory, open ‘/home/ares/ares-webportal/node_modules/.staging/caniuse-lite-8ec193c7/data/regions/ET.js’
npm WARN tar ENOENT: no such file or directory, open ‘/home/ares/ares-webportal/node_modules/.staging/caniuse-lite-8ec193c7/data/features/eventsource.js’
npm WARN tar ENOENT: no such file or directory, open ‘/home/ares/ares-webportal/node_modules/.staging/caniuse-lite-8ec193c7/data/features/extended-system-fonts.js’
npm WARN tar ENOENT: no such file or directory, open ‘/home/ares/ares-webportal/node_modules/.staging/caniuse-lite-8ec193c7/data/features/feature-policy.js’
npm WARN tar ENOENT: no such file or directory, open ‘/home/ares/ares-webportal/node_modules/.staging/caniuse-lite-8ec193c7/dist/unpacker/feature.js’
npm WARN tar ENOENT: no such file or directory, open ‘/home/ares/ares-webportal/node_modules/.staging/caniuse-lite-8ec193c7/data/features.js’

npm ERR! A complete log of this run can be found in:
npm ERR! /home/ares/.npm/_logs/2020-12-23T11_19_58_573Z-debug.log

When were you getting those errors? When you did npm install, or when you tried to deploy the portal?

Also those are WARN statements from npm, so it seems like there may have been a different error. What does that logfile it mentions say?

They were on the npm install.

Lines 1-4076 are ‘silly decomposeActions’ for various files.

28088 silly install executeActions
28089 silly doSerial global-install 24804
28090 verbose correctMkdir /home/ares/.npm/_locks correctMkdir not in flight; initializing
28091 verbose lock using /home/ares/.npm/_locks/staging-d524089f69f99ae1.lock for /home/ares/ares-webportal/node_modules/.staging
28092 silly doParallel extract 2712

Lines 4082-4131 are ‘silly extract’ for various files.
Lines 4138-4181 are ‘silly tarball trying’ for various files.

28193 timing audit compress Completed in 393ms
28194 info audit Submitting payload of 179502bytes

Lines 4184-4199 are ‘silly extract’ for various files.
Lines 4200-4207 are ‘silly tarball trying’ for various files.
Pattern follows a few lines at a time through line 4259.

28271 http fetch POST 200 https://registry.npmjs.org/-/npm/v1/security/audits/quick 2221ms
28272 timing audit body Completed in 290ms

Similar pattern of lines of ‘silly extract’, ‘silly tarball trying’ and ‘fetch POST’ entries though line 5323. Then the ‘warn tar ENOENT’ messages start showing up with a few ‘silly extract’ lines thrown in here and there through line 9520.

33532 verbose unlock done using /home/ares/.npm/_locks/staging-d524089f69f99ae1.lock for /home/ares/ares-webportal/node_modules/.staging
33533 timing stage:rollbackFailedOptional Completed in 4ms
33534 timing stage:runTopLevelLifecycles Completed in 39035ms

Lines 9524-12999 are ‘silly saveTree’ for each file in the folder structure.

33536 warn express@4.17.1 had bundled packages that do not match the required version(s). They have been replaced with non-bundled versions.
33537 verbose stack Error: ENOENT: no such file or directory, rename ‘/home/ares/ares-webportal/node_modules/.staging/fs-merger-a7bfc38e/node_modules/wrappy’ -> ‘/home/ares/ares-webportal/node_modules/.staging/wrappy-44f7b5a3’
33538 verbose cwd /home/ares/ares-webportal
33539 verbose Linux 4.15.0-128-generic
33540 verbose argv “/home/ares/.nvm/versions/node/v11.0.0/bin/node” “/home/ares/.nvm/versions/node/v11.0.0/bin/npm” “install”
33541 verbose node v11.0.0
33542 verbose npm v6.4.1
33543 error path /home/ares/ares-webportal/node_modules/.staging/fs-merger-a7bfc38e/node_modules/wrappy
33544 error code ENOENT
33545 error errno -2
33546 error syscall rename
33547 error enoent ENOENT: no such file or directory, rename ‘/home/ares/ares-webportal/node_modules/.staging/fs-merger-a7bfc38e/node_modules/wrappy’ -> ‘/home/ares/ares-webportal/node_modules/.staging/wrappy-44f7b5a3’
33548 error enoent This is related to npm not being able to find a file.
33549 verbose exit [ -2, true ]

I’ve never seen that particular error before. Unfortunately, NPM is a package manager tool that’s not really part of Ares. I have limited capability to troubleshoot NPM issues.

You could try removing both the node_modules and package-lock.json files from ares-webportal and trying npm install again.

That worked!

Though when running npm install and deploying I did receive several warnings about deprecated packages.

ares@Aurora:~/ares-webportal$ npm install
npm WARN deprecated popper.js@1.16.1: You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1
npm WARN deprecated @babel/polyfill@7.12.1: :rotating_light: 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 WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated mkdirp@0.3.5: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN deprecated core-js@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 WARN deprecated fsevents@2.1.3: Please update to v 2.2.x
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated request-promise-native@1.0.9: 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 chokidar@2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated exists-sync@0.0.4: Please replace with usage of fs.existsSync
npm WARN deprecated request@2.81.0: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated har-validator@4.2.1: this library is no longer supported
npm WARN deprecated hawk@3.1.3: This module moved to @hapi/hawk. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
npm WARN deprecated hoek@2.16.3: 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 boom@2.10.1: 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 cryptiles@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 sntp@1.0.9: This module moved to @hapi/sntp. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
npm WARN deprecated socks@1.1.10: If using 2.x branch, please upgrade to at least 2.1.6 to avoid a serious bug with socket data flow and an import issue introduced in 2.1.0

yarn@1.22.10 preinstall /home/ares/ares-webportal/node_modules/yarn
:; (node ./preinstall.js > /dev/null 2>&1 || true)

node-sass@4.14.1 install /home/ares/ares-webportal/node_modules/node-sass
node scripts/install.js

ares@Aurora:~/ares-webportal$ bin/deploy
npm WARN deprecated fsevents@2.1.3: Please update to v 2.2.x
npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.1.2 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.2.7 (node_modules/watchpack-chokidar2/node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})
npm WARN jsdom@16.4.0 requires a peer of canvas@^2.5.0 but none is installed. You must install peer dependencies yourself.
npm WARN ws@7.4.1 requires a peer of bufferutil@^4.0.1 but none is installed. You must install peer dependencies yourself.
npm WARN ws@7.4.1 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must install peer dependencies yourself.

up to date in 33.312s
DEPRECATION: Node v11.0.0 is no longer supported by Ember CLI. We recommend that you use the most-recent “Active LTS” version of Node.js. See https://git.io/v7S5n for details.
WARNING: Node v11.0.0 is not tested against Ember CLI on your platform. We recommend that you use the most-recent “Active LTS” version of Node.js. See https://git.io/v7S5n for details.
Environment: production
⠋ Building(node:6230) ExperimentalWarning: The fs.promises API is experimental
⠸ building… [Babel: ember-concurrency > applyPatches]DEPRECATION: The use of the private {{-in-element}} is deprecated, please refactor to the public {{in-element}}. (‘ember-popper/templates/components/ember-popper-targeting-parent.hbs’ @ L1:C0) [deprecation id: glimmer.private-in-element]
at logDeprecationStackTrace (/home/ares/ares-webportal/node_modules/ember-source/dist/ember-template-compiler.js:1930:21)
at HANDLERS.(anonymous function) (/home/ares/ares-webportal/node_modules/ember-source/dist/ember-template-compiler.js:2027:9)
at raiseOnDeprecation (/home/ares/ares-webportal/node_modules/ember-source/dist/ember-template-compiler.js:1957:9)
at HANDLERS.(anonymous function) (/home/ares/ares-webportal/node_modules/ember-source/dist/ember-template-compiler.js:2027:9)
at invoke (/home/ares/ares-webportal/node_modules/ember-source/dist/ember-template-compiler.js:2039:9)
at deprecate (/home/ares/ares-webportal/node_modules/ember-source/dist/ember-template-compiler.js:1995:28)
at BlockStatement (/home/ares/ares-webportal/node_modules/ember-source/dist/ember-template-compiler.js:10730:59)
at visitNode (/home/ares/ares-webportal/node_modules/ember-source/dist/ember-template-compiler.js:7742:16)
at visitArray (/home/ares/ares-webportal/node_modules/ember-source/dist/ember-template-compiler.js:7833:20)
⠼ building… [Babel: ember-concurrency > applyPatches]DEPRECATION: The use of the private {{-in-element}} is deprecated, please refactor to the public {{in-element}}. (‘ember-popper/templates/components/ember-popper.hbs’ @ L1:C0) [deprecation id: glimmer.private-in-element]
at logDeprecationStackTrace (/home/ares/ares-webportal/node_modules/ember-source/dist/ember-template-compiler.js:1930:21)
at HANDLERS.(anonymous function) (/home/ares/ares-webportal/node_modules/ember-source/dist/ember-template-compiler.js:2027:9)
at raiseOnDeprecation (/home/ares/ares-webportal/node_modules/ember-source/dist/ember-template-compiler.js:1957:9)
at HANDLERS.(anonymous function) (/home/ares/ares-webportal/node_modules/ember-source/dist/ember-template-compiler.js:2027:9)
at invoke (/home/ares/ares-webportal/node_modules/ember-source/dist/ember-template-compiler.js:2039:9)
at deprecate (/home/ares/ares-webportal/node_modules/ember-source/dist/ember-template-compiler.js:1995:28)
at BlockStatement (/home/ares/ares-webportal/node_modules/ember-source/dist/ember-template-compiler.js:10730:59)
at visitNode (/home/ares/ares-webportal/node_modules/ember-source/dist/ember-template-compiler.js:7742:16)
at visitArray (/home/ares/ares-webportal/node_modules/ember-source/dist/ember-template-compiler.js:7833:20)
⠇ building… [broccoli-persistent-filter:TemplateCompiler > applyPatches]DEPRECATION: The use of the private {{-in-element}} is deprecated, please refactor to the public {{in-element}}. (‘ember-bootstrap/templates/components/bs-modal-simple.hbs’ @ L1:C0) [deprecation id: glimmer.private-in-element]
at logDeprecationStackTrace (/home/ares/ares-webportal/node_modules/ember-source/dist/ember-template-compiler.js:1930:21)
at HANDLERS.(anonymous function) (/home/ares/ares-webportal/node_modules/ember-source/dist/ember-template-compiler.js:2027:9)
at raiseOnDeprecation (/home/ares/ares-webportal/node_modules/ember-source/dist/ember-template-compiler.js:1957:9)
at HANDLERS.(anonymous function) (/home/ares/ares-webportal/node_modules/ember-source/dist/ember-template-compiler.js:2027:9)
at invoke (/home/ares/ares-webportal/node_modules/ember-source/dist/ember-template-compiler.js:2039:9)
at deprecate (/home/ares/ares-webportal/node_modules/ember-source/dist/ember-template-compiler.js:1995:28)
at BlockStatement (/home/ares/ares-webportal/node_modules/ember-source/dist/ember-template-compiler.js:10730:59)
at visitNode (/home/ares/ares-webportal/node_modules/ember-source/dist/ember-template-compiler.js:7742:16)
at visitArray (/home/ares/ares-webportal/node_modules/ember-source/dist/ember-template-compiler.js:7833:20)
DEPRECATION: The use of the private {{-in-element}} is deprecated, please refactor to the public {{in-element}}. (‘ember-bootstrap/templates/components/bs-modal.hbs’ @ L1:C0) [deprecation id: glimmer.private-in-element]
at logDeprecationStackTrace (/home/ares/ares-webportal/node_modules/ember-source/dist/ember-template-compiler.js:1930:21)
at HANDLERS.(anonymous function) (/home/ares/ares-webportal/node_modules/ember-source/dist/ember-template-compiler.js:2027:9)
at raiseOnDeprecation (/home/ares/ares-webportal/node_modules/ember-source/dist/ember-template-compiler.js:1957:9)
at HANDLERS.(anonymous function) (/home/ares/ares-webportal/node_modules/ember-source/dist/ember-template-compiler.js:2027:9)
at invoke (/home/ares/ares-webportal/node_modules/ember-source/dist/ember-template-compiler.js:2039:9)
at deprecate (/home/ares/ares-webportal/node_modules/ember-source/dist/ember-template-compiler.js:1995:28)
at BlockStatement (/home/ares/ares-webportal/node_modules/ember-source/dist/ember-template-compiler.js:10730:59)
at visitNode (/home/ares/ares-webportal/node_modules/ember-source/dist/ember-template-compiler.js:7742:16)
at visitArray (/home/ares/ares-webportal/node_modules/ember-source/dist/ember-template-compiler.js:7833:20)
cleaning up…
Built project successfully. Stored in “dist/”.
File sizes:

  • dist/assets/ares-webportal-35d421156fd26bc065cb9bf91351e8f8.css: 177.31 KB (25.5 KB gzipped)
  • dist/assets/ares-webportal-d4c5f6b668225a6285c5a64b4534ebfd.js: 1.06 MB (123.54 KB gzipped)
  • dist/assets/vendor-1b1b5d429649e752602a21386c918cfc.css: 5.85 KB (2.15 KB gzipped)
  • dist/assets/vendor-cef6542db1036525bc15eba5f9435e96.js: 3.74 MB (867.25 KB gzipped)
  • dist/scripts/ace_editor-0196270d42892dcac666a8754d514828.js: 364.44 KB (101.26 KB gzipped)
  • dist/scripts/alertify.min-1dfc05da2f216b35ce3565ae32389731.js: 35.02 KB (9.42 KB gzipped)
  • dist/scripts/ansi_up-158566dc1ff8f2804de972f7e841e2f6.js: 10.76 KB (2.83 KB gzipped)
  • dist/scripts/aresweb_version-5da32b736e5cc3cc140e17a1838ca5ff.js: 30 B (50 B gzipped)
  • dist/scripts/music_player-2464b1d0edbbfe5487df7a2912d8c14b.js: 1.44 KB (616 B gzipped)
    ares@Aurora:~/ares-webportal$

It looks like you have an outdated version of node/npm, which may have been related to the earlier issues. Not sure what environment you’re using, but I’m guessing it’s non-standard since the default installer sets up node 12 using NVM.

nvm install 12
nvm use 12

Not sure what environment it is either. Was setup quite awhile ago. That seemed to fix most of it though I’m still getting a few warnings.

ares@Aurora:~$ cd ares-webportal
ares@Aurora:~/ares-webportal$ nvm install 12
Downloading and installing node v12.20.0…
Downloading https://nodejs.org/dist/v12.20.0/node-v12.20.0-linux-x64.tar.xz
######################################################################### 100.0%
Computing checksum with sha256sum
Checksums matched!
Now using node v12.20.0 (npm v6.14.8)
ares@Aurora:~/ares-webportal$ nvm use 12
Now using node v12.20.0 (npm v6.14.8)
ares@Aurora:~/ares-webportal$ bin/deploy
npm WARN jsdom@16.4.0 requires a peer of canvas@^2.5.0 but none is installed. You must install peer dependencies yourself.
npm WARN ws@7.4.1 requires a peer of bufferutil@^4.0.1 but none is installed. You must install peer dependencies yourself.
npm WARN ws@7.4.1 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.3 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules/watchpack-chokidar2/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})

up to date in 34.763s
DEPRECATION: Node v11.0.0 is no longer supported by Ember CLI. We recommend that you use the most-recent “Active LTS” version of Node.js. See https://git.io/v7S5n for details.
WARNING: Node v11.0.0 is not tested against Ember CLI on your platform. We recommend that you use the most-recent “Active LTS” version of Node.js. See https://git.io/v7S5n for details.
Environment: production
⠋ Building(node:10596) ExperimentalWarning: The fs.promises API is experimental
cleaning up…
Built project successfully. Stored in “dist/”.
File sizes:

  • dist/assets/ares-webportal-35d421156fd26bc065cb9bf91351e8f8.css: 177.31 KB (25.5 KB gzipped)
  • dist/assets/ares-webportal-d4c5f6b668225a6285c5a64b4534ebfd.js: 1.06 MB (123.54 KB gzipped)
  • dist/assets/vendor-1b1b5d429649e752602a21386c918cfc.css: 5.85 KB (2.15 KB gzipped)
  • dist/assets/vendor-cef6542db1036525bc15eba5f9435e96.js: 3.74 MB (867.25 KB gzipped)
  • dist/scripts/ace_editor-0196270d42892dcac666a8754d514828.js: 364.44 KB (101.26 KB gzipped)
  • dist/scripts/alertify.min-1dfc05da2f216b35ce3565ae32389731.js: 35.02 KB (9.42 KB gzipped)
  • dist/scripts/ansi_up-158566dc1ff8f2804de972f7e841e2f6.js: 10.76 KB (2.83 KB gzipped)
  • dist/scripts/aresweb_version-5da32b736e5cc3cc140e17a1838ca5ff.js: 30 B (50 B gzipped)
  • dist/scripts/music_player-2464b1d0edbbfe5487df7a2912d8c14b.js: 1.44 KB (616 B gzipped)

Hmm, it looks like it’s still using the old version of node somehow:

DEPRECATION: Node v11.0.0 is no longer supported by Ember CLI. We recommend that you use the most-recent “Active LTS” version of Node.js. See https://git.io/v7S5n for details.

Not sure why, since I can clearly see you typed ‘nvm use 12’ right before that.

I’m using node 12.14 and I don’t see any deprecation warnings on my deploy:

ares@forum:~/ares-webportal$ node -v
v12.14.0

That ‘skipping optional dependency’ stuff for fsevents is normal though. Why it feels the need to spam you with four lines of warnings for an OPTIONAL dependency is beyond me. :joy:

Yeah, that was what was weird. I just tried it again and checked version before and after the deploy and it was showing as version 12 both times but I still got the message about Node v11 being deprecated.

I tried uninstalling v11 and after that did not get the message about it being deprecated and got this which seems odd too, but its still working.

ares@Aurora:~/ares-webportal$ bin/deploy
N/A: version “N/A -> N/A” is not yet installed.

You need to run “nvm install N/A” to install it before using it.

up to date in 27.957s
bin/deploy: line 4: ember: command not found

I would try doing all those steps above now that node 12 is installed and 11 is gone. Probably something 11-related was cached somewhere.

cd ares-webportal
rm package-lock.json
rm -rf node_modules
npm install
bin/deploy

Now it’s saying the install command isn’t found.

ares@Aurora:~/ares-webportal$ rm package-lock.json
ares@Aurora:~/ares-webportal$ rm -rf node_modules
ares@Aurora:~/ares-webportal$ npm install

Command ‘npm’ not found, but can be installed with:

sudo apt install npm

Whatever you did to uninstall v11 seems to have uninstalled npm entirely. Here are the steps that the install script uses to set that up on a fresh game. Maybe that will work?

As always, be sure to run with the ‘ares’ user.

sudo apt-get install -y nodejs
sudo apt-get install -y npm
sudo npm install -g npm
curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.33.8/install.sh | bash
export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh" # This loads nvm
nvm install 12
nvm use 12
npm install -g ember-cli

Still getting a message in there about ‘N/A: version “N/A -> N/A” is not yet installed.’ which is weird, but was able to deploy again. Thanks.

This may help: https://stackoverflow.com/questions/49449719/nvm-n-a-version-n-a-n-a-is-not-yet-installed

Thanks. That seems to have fixed.

1 Like