App does not open upon newest update.

[tjhexf]

Aknowledgements

• I have checked that there's no other issue describing the same or
  similar problem that I currently have, regardless if it has been
  closed or open.

• I can confirm that this is not an issue with the Discord website,
  but it is a problem specific to the WebCord itself. I have tested
  if this bug occurs on Chromium/Chrome or any other Chromium-based
  browser that uses unpatched/upstream Chromium engine.

• I have tried running the build from the master branch and it does
  not have any fixes implemented according to my issue.

• My issue describes one of the unstable and/or not fully implemented
  features.

• I have found a workaround to mitigate or temporarily fix this issue
  in affected releases (please write it in Additional context section
  below).

Operating System / Platform

🐧️ Linux

Operating system architecture

x64 (64-bit Intel/AMD)

Electron version

20.0.3-2

Application version

3.8.7

Bug description

Unknown option '--ozone-platform-hint'
      at checkOptionUsage (/usr/lib/webcord/node_modules/@pkgjs/parseargs/index.js:96:11)
      at parseArgs (/usr/lib/webcord/node_modules/@pkgjs/parseargs/index.js:323:3)
      at Object.<anonymous> (/usr/lib/webcord/app/code/common/main.js:42:31)

prevents the app from opening. I'm on latest arch linux.

Additional context

downgrading the package causes it to open normally again.

[tjhexf]

Nevermind. Fixed it, i screwed up and still had this ozone option from when i was using wayland. Still weird that it doesn't work on the newest one though

[BowDown097]

Also having problems with the --disable-http-cache option.

[MetallicGoat]

My version of the error looks a little different. If its helpful

[chmanie]

The question here would be, is there a way to run it in native wayland mode again?

[SpacingBat3]

@chmanie, @MetallicGoat, @tjhexf (and anyone interested at this issue): I'm currently working on it, the bug is a human error (i.e. I've enforced strict flags checking, which basically means that any flag outside of those in --help will not work). I'll release a fix, but first I have to deal with another issue brought by ESLint update, so please be patient a little…

[chmanie]

@SpacingBat3 Thanks so much for the quick reply! Let me know if I can help in any way (e.g. fix some pesky eslint issues).

[SpacingBat3]

Let me know if I can help in any way (e.g. fix some pesky eslint issues).

There's no help needed on that, looks like @typescript-eslint/* packages just broke at 5.40.0 and there's an internal error in the linter itself, I just need to pin it to 5.39.0…

I want to make some final touches to the code and I guess I'll just release 3.8.8.

[MetallicGoat]

Don't mean to rush you, just wanted to send my version of error in case it would help you track down the issue. Take your time :)