AncientBeast icon indicating copy to clipboard operation
AncientBeast copied to clipboard

Unable to Run Development Environment on Windows 10

Open pranshugupta01 opened this issue 8 months ago • 7 comments

Describe the bug I'm not able to successfully run the development environment for the project on Windows 10. Although npm i, npm run build:dev, and npm run start complete without crashing, the development server does not open a working instance in the browser, and nothing seems to load properly. The process ends with a "Gracefully shutting down" message.

To Reproduce Steps to reproduce the behavior:

  1. Clone the repository on Windows 10.
  2. Run npm i
  3. Run npm run build:dev
  4. Run npm start
  5. Observe that the server starts and shuts down without fully launching.

Terminal output :

Admin@DESKTOP-46J7OTP MINGW64 ~/Desktop/AncientBeast (master)
$ npm install
npm WARN deprecated [email protected]: core-js@<3.23.3 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. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.

added 1049 packages, and audited 1050 packages in 1m

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

3 moderate severity vulnerabilities

To address all issues, run:
  npm audit fix

Run `npm audit` for details.
Admin@DESKTOP-46J7OTP MINGW64 ~/Desktop/AncientBeast (master)
$ npm run build:dev

> [email protected] build:dev
> webpack --mode=development

assets by path assets/units/ 3.73 MiB 370 assets
assets by path assets/autoload/phaser/ 423 KiB 77 assets
assets by path assets/stats/ 174 KiB 38 assets
assets by path assets/icons/ 55.8 KiB 32 assets
assets by path assets/interface/ 685 KiB 24 assets
assets by path *.js 35.1 MiB 23 assets
assets by path assets/music/ 62.4 MiB 17 assets
assets by path assets/drops/stock/*.png 3.68 KiB 12 assets
assets by path assets/sounds/*.ogg 252 KiB 9 assets
assets by path assets/cards/ 110 KiB 9 assets
assets by path assets/locations/ 791 KiB 4 assets
assets by path assets/fonts/ 75.3 KiB
  assets by path assets/fonts/*.woff 41.8 KiB 2 assets
  assets by path assets/fonts/*.woff2 33.5 KiB 2 assets
+ 4 assets
runtime modules 8.48 KiB 13 modules
javascript modules 8.99 MiB
  modules by path ./node_modules/ 7.89 MiB 635 modules
  modules by path ./src/ 1.04 MiB 71 modules
  ./assets/index.js 63.3 KiB [built] [code generated]
asset modules 24.5 KiB (javascript) 68.7 MiB (asset) 597 modules
json modules 37.7 KiB
  ./package.json 2.44 KiB [built] [code generated]
  ./node_modules/node-emoji/lib/emoji.json 35.2 KiB [built] [code generated]
webpack 5.94.0 compiled successfully in 83880 ms
Admin@DESKTOP-46J7OTP MINGW64 ~/Desktop/AncientBeast (master)
$ npm run start

> [email protected] start
> cross-env NODE_ENV=production webpack-dev-server

<i> [webpack-dev-server] [HPM] Proxy created: /api  -> 159.65.232.104:7350
<i> [webpack-dev-server] Project is running at:
<i> [webpack-dev-server] Loopback: http://localhost:8080/
<i> [webpack-dev-server] On Your Network (IPv4): http://192.168.29.5:8080/
<i> [webpack-dev-server] On Your Network (IPv6): http://[fe80::e11f:b247:bc1e:aa99]:8080/
<i> [webpack-dev-server] Content not from webpack is served from './' directory
<i> [webpack-dev-middleware] wait until bundle finished: /
assets by path assets/ 68.7 MiB 594 assets
assets by path *.js 3.62 MiB
  assets by info 3.62 MiB [immutable]
    assets by status 3.52 MiB [big]
      asset app.4ae3abce12adf5e3d993.bundle.js 2.61 MiB [emitted] [immutable] [minimized] [big] (name: app) 2 related assets
      asset vendor.e67bf7b54d3e44e73877.bundle.js 938 KiB [emitted] [immutable] [minimized] [big] (name: vendor) 2 related assets
    + 19 assets
  asset analytics.js 415 bytes [emitted] [from: static/analytics.js] [copied] [minimized]
  asset worker.js 351 bytes [emitted] [from: static/worker.js] [copied] [minimized]
asset index.html 28.4 KiB [emitted]
asset favicon.png 11.7 KiB [emitted]
asset manifest.json 507 bytes [emitted] [from: static/manifest.json] [copied]
orphan modules 827 KiB [orphan] 220 modules
runtime modules 58.7 KiB 28 modules
cacheable modules 9.22 MiB (javascript) 68.7 MiB (asset)
  modules by path ./assets/ 24.5 KiB (javascript) 68.7 MiB (asset) 597 modules
  javascript modules 9.17 MiB 513 modules
  ./node_modules/node-emoji/lib/emoji.json 35.2 KiB [built] [code generated]
./src/abilities/ lazy ^\.\/.*$ namespace object 160 bytes [built] [code generated]

WARNING in asset size limit: The following asset(s) exceed the recommended size limit (244 KiB).
This can impact web performance.
Assets:
  assets/647561b8960feafbb7a6..gif (261 KiB)
  assets/03c21f76fbf4674974a5..ogg (1.71 MiB)
  assets/c2214bdf35750743ec32..ogg (2.86 MiB)
  assets/3d590683bc21ee706809..ogg (2.94 MiB)
  assets/0c69d181053f0dfdf02b..ogg (3.52 MiB)
  assets/13fa7d1f597e0c7881be..ogg (5.49 MiB)
  assets/7030b3bebaf25ed0d7d2..ogg (3.24 MiB)
  assets/d8b81a839562d181752e..ogg (3.06 MiB)
  assets/ad26797556a3d2ce6412..ogg (3.29 MiB)
  assets/b959e80f6d08134998cd..ogg (2.88 MiB)
  assets/36ccd3896a3e4fb5c8de..ogg (3.21 MiB)
  assets/9605e5d3713864fd343b..ogg (2.77 MiB)
  assets/e355e4fc667320b9a683..ogg (3.24 MiB)
  assets/2d607f69ae5d7f7afd34..ogg (7 MiB)
  assets/40a30beb49d97277d181..ogg (4.54 MiB)
  assets/e39f11c4f37dd594cb5d..ogg (4.7 MiB)
  assets/341376a360bda3fc90f2..ogg (3.04 MiB)
  assets/13a89453d1638e4e2104..ogg (4.92 MiB)
  vendor.e67bf7b54d3e44e73877.bundle.js (938 KiB)
  app.4ae3abce12adf5e3d993.bundle.js (2.61 MiB)

WARNING in entrypoint size limit: The following entrypoint(s) combined asset size exceeds the recommended limit (244 KiB). This can impact web performance.    
Entrypoints:
  vendor (938 KiB)
      vendor.e67bf7b54d3e44e73877.bundle.js
  app (2.61 MiB)
      app.4ae3abce12adf5e3d993.bundle.js


webpack 5.94.0 compiled with 2 warnings in 102934 ms
<i> [webpack-dev-server] Gracefully shutting down. To force exit, press ^C again. Please wait...

Expected behavior The development server should start and open the app in a browser (http://localhost:8080/), allowing development and testing.

Screenshots

Image

Desktop (please complete the following information):

  • OS: [e.g. iOS]
  • Browser : brave ,chrome
  • Node Versio : 20.11.1

Additional context

  1. npm i shows deprecation warning for [email protected]
  2. 3 moderate severity vulnerabilities shown after install
  3. Warnings during npm run start about large asset sizes
  4. Webpack compiles with warnings but doesn't show any runtime errors

pranshugupta01 avatar Apr 22 '25 16:04 pranshugupta01

You're doing it wrong, it's 'npm run start:dev'

DreadKnight avatar Apr 22 '25 16:04 DreadKnight

You're doing it wrong, it's 'npm run start:dev'

i am following Contributing guide in that command is different it is npm run start , and the one you have mentioned is for patch ig

pranshugupta01 avatar Apr 22 '25 16:04 pranshugupta01

You're doing it wrong, it's 'npm run start:dev'

i am following Contributing guide in that command is different it is npm run start , and the one you have mentioned is for patch ig

Well, you mentioned development server in title, which means the one for patching.

DreadKnight avatar Apr 22 '25 16:04 DreadKnight

You're doing it wrong, it's 'npm run start:dev'

i am following Contributing guide in that command is different it is npm run start , and the one you have mentioned is for patch ig

Well, you mentioned development server in title, which means the one for patching.

oh right sorry my bad , i'll close the issue

pranshugupta01 avatar Apr 22 '25 16:04 pranshugupta01

But why it is showing error when running the command npm run start @DreadKnight

pranshugupta01 avatar Apr 22 '25 17:04 pranshugupta01

But why it is showing error when running the command npm run start @DreadKnight

Could be bugged if that's the command for production. I removed some Google Analitics stuff a while ago.

DreadKnight avatar Apr 22 '25 17:04 DreadKnight

@pranshugupta01 Tested npm run start on Linux. Getting those errors as well, but that error page could be closed, though it was double (overlapped), requiring pressing upper right "x" from within the page twice. Game playable just fine regardless.

Anyway, issue would need some updating 🐻

DreadKnight avatar Apr 23 '25 05:04 DreadKnight