Web Portal/Game Version Mismatch Since Last Patch (v0.107)

AresMUSH
1

The game engine seems to be running fine within the MUSH itself. However, the web portal seems to be stuck back on v0.104. When I run a website/deploy on OtherSpace, I get this error text:

%% Web portal deployed!

Build Output:
npm WARN old lockfile
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile
npm WARN old lockfile This is a one-time fix-up, please be patient…
npm WARN old lockfile
npm ERR! Cannot read property ‘resolve’ of null

npm ERR! A complete log of this run can be found in:
npm ERR! /home/ares/.npm/_logs/2022-04-14T03_27_47_021Z-debug-0.log
Cannot find module ‘./src/version-checker’
Require stack:

  • /home/ares/ares-webportal/node_modules/ember-cli-inject-live-reload/node_modules/ember-cli-version
    -checker/index.js
  • /home/ares/ares-webportal/node_modules/ember-cli-inject-live-reload/lib/index.js
  • /home/ares/.nvm/versions/node/v12.20.1/lib/node_modules/ember-cli/lib/models/package-info
    -cache/package-info.js
  • /home/ares/.nvm/versions/node/v12.20.1/lib/node_modules/ember-cli/lib/models/package-info
    -cache/index.js
  • /home/ares/.nvm/versions/node/v12.20.1/lib/node_modules/ember-cli/lib/models/project.js
  • /home/ares/.nvm/versions/node/v12.20.1/lib/node_modules/ember-cli/lib/utilities/get-config.js
  • /home/ares/.nvm/versions/node/v12.20.1/lib/node_modules/ember-cli/lib/utilities/instrumentation.js
  • /home/ares/.nvm/versions/node/v12.20.1/lib/node_modules/ember-cli/lib/cli/index.js
  • /home/ares/.nvm/versions/node/v12.20.1/lib/node_modules/ember-cli/bin/ember

Stack Trace and Error Report: /tmp/error.dump.a4add4cf2283eb0508fd87f390b00670.log

‘npm WARN’ statements are OK. A successful deploy will end with a list of file sizes.
Done!
%% Web portal deployed!

Build Output:
npm WARN old lockfile
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile
npm WARN old lockfile This is a one-time fix-up, please be patient…
npm WARN old lockfile
npm WARN cleanup Failed to remove some directories [
npm WARN cleanup [
npm WARN cleanup undefined,
npm WARN cleanup AssertionError [ERR_ASSERTION]: rimraf: missing path
npm WARN cleanup at rimraf
(/home/ares/.nvm/versions/node/v12.20.1/lib/node_modules/npm/node_modules/rimraf/rimraf.js:54:3)
npm WARN cleanup at internal/util.js:297:30
npm WARN cleanup at new Promise ()
npm WARN cleanup at rimraf (internal/util.js:296:12)
npm WARN cleanup at
/home/ares/.nvm/versions/node/v12.20.1/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/reify.js:532:20
npm WARN cleanup at Array.map ()
npm WARN cleanup at Arborist.[rollbackCreateSparseTree]
(/home/ares/.nvm/versions/node/v12.20.1/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/reify.js:532:8)
npm WARN cleanup at Arborist.[reifyPackages]
(/home/ares/.nvm/versions/node/v12.20.1/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/reify.js:235:31)
npm WARN cleanup at processTicksAndRejections (internal/process/task_queues.js:97:5) {
npm WARN cleanup generatedMessage: false,
npm WARN cleanup code: ‘ERR_ASSERTION’,
npm WARN cleanup actual: undefined,
npm WARN cleanup expected: true,
npm WARN cleanup operator: ‘==’
npm WARN cleanup }
npm WARN cleanup ]
npm WARN cleanup ]
npm ERR! Cannot read property ‘resolve’ of null

npm ERR! A complete log of this run can be found in:
npm ERR! /home/ares/.npm/_logs/2022-04-14T03_30_21_913Z-debug-0.log
Cannot find module ‘./src/version-checker’
Require stack:

  • /home/ares/ares-webportal/node_modules/ember-cli-inject-live-reload/node_modules/ember-cli-version
    -checker/index.js
  • /home/ares/ares-webportal/node_modules/ember-cli-inject-live-reload/lib/index.js
  • /home/ares/.nvm/versions/node/v12.20.1/lib/node_modules/ember-cli/lib/models/package-info
    -cache/package-info.js
  • /home/ares/.nvm/versions/node/v12.20.1/lib/node_modules/ember-cli/lib/models/package-info
    -cache/index.js
  • /home/ares/.nvm/versions/node/v12.20.1/lib/node_modules/ember-cli/lib/models/project.js
  • /home/ares/.nvm/versions/node/v12.20.1/lib/node_modules/ember-cli/lib/utilities/get-config.js
  • /home/ares/.nvm/versions/node/v12.20.1/lib/node_modules/ember-cli/lib/utilities/instrumentation.js
  • /home/ares/.nvm/versions/node/v12.20.1/lib/node_modules/ember-cli/lib/cli/index.js
  • /home/ares/.nvm/versions/node/v12.20.1/lib/node_modules/ember-cli/bin/ember

Stack Trace and Error Report: /tmp/error.dump.a4add4cf2283eb0508fd87f390b00670.log

Any thoughts on what’s going on? Thanks!

2

It says

npm WARN old lockfile The package-lock.json file was created with an old version of npm,

Which implies that you’re running with a newer version of node/npm, and shouldn’t be necessary.

Did you run the special upgrade steps for 107?

cd ~/ares-webportal
bin/update_npm
cd ~/aresmush
bin/startares

You can double check afterward that your node -v shows 12.something and npm -v shows 6.something

It’s also possible that your local version of package-lock.json may have gotten messed up during all the upgrade/downgrade shenanigans. You can delete it and re-create a new copy with the version from github. In ares-webportal:

rm package-lock.json
curl https://raw.githubusercontent.com/AresMUSH/ares-webportal/master/package-lock.json > package-lock.json
3

Yep, it helps to run those special upgrade steps for the webportal!

Thanks.

1 Like