mozilla hubs をローカルで起動する際に、シーンの読み込みに失敗する。

前提

機能拡張のためテスト環境として、mozilla Hubsをローカルで構築したいと考えています。
以下の公式サイト通りに作業を進めてHubsをローカルで起動することはできました。
しかし、「部屋を作成する」をおしたらシーンの読み込みに失敗してしまします。

エラーログがどこにあるのかさえ、理解できていないのでログのパスが分かるかたがいればご教授お願い致します。

参考にしたサイトは以下になります。
https://github.com/mozilla/hubs

実施手順

git clone https://github.com/mozilla/hubs.git
cd hubs
npm ci
npm run dev

発生している問題・エラーメッセージ

エラーがどこに吐き出されているのかも分かっていません。
気になる点としては、npm ciの時に以下の警告が出ています。

npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'aframe@1.0.3',
npm WARN EBADENGINE   required: { node: '>= 4.6.0', npm: '^2.15.9' },
npm WARN EBADENGINE   current: { node: 'v16.14.2', npm: '8.5.0' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'networked-aframe@0.6.1',
npm WARN EBADENGINE   required: { node: '>= 7.4.0', npm: '^4.0.5' },
npm WARN EBADENGINE   current: { node: 'v16.14.2', npm: '8.5.0' }
npm WARN EBADENGINE }
npm WARN deprecated set-value@0.4.3: Critical bug fixed in v3.0.1, please upgrade to the latest version.
・
・
・
npm WARN deprecated core-js@2.6.12: core-js@<3.4 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.
npm WARN deprecated core-js@2.6.12: core-js@<3.4 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.
npm WARN deprecated core-js@2.6.12: core-js@<3.4 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.
npm WARN deprecated core-js@2.6.12: core-js@<3.4 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.
npm WARN deprecated core-js@2.6.12: core-js@<3.4 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.
npm WARN deprecated core-js@2.6.12: core-js@<3.4 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.
npm WARN deprecated core-js@2.6.9: core-js@<3.4 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.

added 4103 packages, and audited 4104 packages in 6m

168 packages are looking for funding
  run `npm fund` for details

120 vulnerabilities (12 low, 38 moderate, 62 high, 8 critical)

To address issues that do not require attention, run:
  npm audit fix

To address all issues possible (including breaking changes), run:
  npm audit fix --force

Some issues need review, and may require choosing
a different dependency.

Run `npm audit` for details.