dependency issues after initial -> npm install -- and Blank (White) screen after npm run)

[AiFxApp]

• What operating system are you using?
  Windows 11
• What version of Node.js is on your system?
  v17.5.0
  NPM -v
  8.5.1

Warning Message after cloning repo and running 'npm install'

$ npm install
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 deprecated [email protected]: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated [email protected]: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated [email protected]: See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated [email protected]: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated [email protected]: Deprecated due to CVE-2021-21366 resolved in 0.5.0
npm WARN deprecated [email protected]: See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated [email protected]: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated [email protected]: 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 [email protected]: this library is no longer supported
npm WARN deprecated [email protected]: CircularJSON is in maintenance only, flatted is its successor.
npm WARN deprecated [email protected]: outdated version, please use @next
npm WARN deprecated [email protected]: 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 [email protected]: Support has ended for 9.x series. Upgrade to @latest

added 825 packages, and audited 960 packages in 2m

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

31 vulnerabilities (20 moderate, 9 high, 2 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.

[i-johnso]

I have the same issue

OS: mac os 12.3.1
npm: 8.5.5
node: 17.8.0

When running in debug mode using the command npm run dev I do see JavaScript errors

[ezel]

#508 (comment)

[LondonWebFactory]

Same Issue:

[CharlesShan-hub]

I also encountered this problem!

[CharlesShan-hub]

[Harrylever]

Same Issue here

[Harrylever]

[Welding-Torch]

I have run into the same error

[codetoadsnow]

The same

[miki-long]

[Mickey]已经收到了，谢谢

[moarwick]

Sadly, same here (OSX Big Sur) -- just a white blank screen (no error dialog even)

[jwoo92]

npm i electron@^7.2.4
npm start

[acantepie]

Same issue.

@jwoo92

❯ yarn add electron@^7.2.4
❯ node_modules/.bin/electron .
(electron) 'getName function' is deprecated and will be removed. Please use 'name property' instead.
[19:55:24.494] [info] update-electron-app config looks good; aborting updates since app is in development mode
Fontconfig warning: "/usr/share/fontconfig/conf.avail/05-reset-dirs-sample.conf", line 6: unknown element "reset-dirs"
[5863:0919/195526.182579:FATAL:gpu_data_manager_impl_private.cc(986)] The display compositor is frequently crashing. Goodbye.

It's always the same with Js app, they can't work more than 3 months...

[miki-long]

[Mickey]已经收到了，谢谢

[jwoo92]

Same issue.

@jwoo92

❯ yarn add electron@^7.2.4

❯ node_modules/.bin/electron .

(electron) 'getName function' is deprecated and will be removed. Please use 'name property' instead.

[19:55:24.494] [info] update-electron-app config looks good; aborting updates since app is in development mode

Fontconfig warning: "/usr/share/fontconfig/conf.avail/05-reset-dirs-sample.conf", line 6: unknown element "reset-dirs"

[5863:0919/195526.182579:FATAL:gpu_data_manager_impl_private.cc(986)] The display compositor is frequently crashing. Goodbye.

It's always the same with Js app, they can't work more than 3 months...

@acantepie steps I recommended fix only the white screen issue.

[miki-long]

[Mickey]已经收到了，谢谢