Vladimir Yakovlev

You could try this: ``` @IsArray() @IsString({each: true}) ```

> "npm exec electron-builder" doesn't work on Windows `npm exec --package=electron-builder -- electron-builder` same?

I don't run Windows, but I remember it worker well on GH CI Windows image/env. > yes, that's the same, doens't change a thing `npm -v` (If I remember it...

Looks like the same issue as #391.

Spectron is not yet compatible with Webdriver v5. So you should use v4, see: - https://github.com/electron-userland/spectron/blob/1fdf0814ce661bb86b3bda446a1cf977562a2158/package.json#L35 - https://github.com/electron-userland/spectron/issues/349 - https://github.com/electron-userland/spectron/issues/497

@suwi transition to "playwright" I guess, see details in #896.

@adam-lynch, `npm install` => `npm ci`. If someone runs `yarn`, there is `resolutions` package.json section for this purpose.

You could also run it with --no-sandbox argument. My guess is that one day electron-builder will have appimage package shipped with this argument hardcoded in sh loader script.

By the way, aside from `gnome-keyring`, [keepassxc](https://github.com/keepassxreboot/keepassxc) also implements needed [Secret Service](https://specifications.freedesktop.org/secret-service/latest/) interfaces, see details in [this FAQ](https://github.com/vladimiry/ElectronMail/wiki/FAQ). So `keepassxc` is an alternative to `gnome-keyring`.

> Not sure I understand the issue, as we're using 3.1.0 in the lockfile: Lock file doesn't make sense if the module is installed from npm (since lock files don't...