[Pkg-javascript-devel] electron packaging

[Hubert Chathi]

On Fri, 14 Jun 2019 12:57:15 +0200, Paolo Greppi <paolo.greppi at libpf.com> said:

[...]

> The first step would be to evaluate which of the electron apps we (as
> js-team) want to focus on.  Next find out if a single electron version
> can be used.  From a first look, it seems problematic:

> - atom: "electronVersion": "3.1.10"
> - beaker: "electron": "5.0.0"
> - franz: "electron": "5.0.2",
> - mattermost-desktop: "electron": "^4.0.0"
> - riot-web: "electronVersion": "4.2.4",

FWIW, riot-web should be able to run on electron 5 with only minor
changes, and will probably switch to electron 5.  I would expect that
most apps that use electron 4 are similar, and I think that the reason
most apps are using electron 4 is that electron 5 is only a couple
months old.  So I think that if you want to work on packaging electron,
it would make most sense work on electron 5, especially since it's too
late to get it in buster, and by buster+1, most apps will surely be off
of electron 4.

> - signal-desktop: "electron": "4.2.2"
> - ssb-patchwork: "electron": "^4.2.4",
> - vscode: target "4.2.4" (for vscode it is not in package.json, I found it here (?):
> https://github.com/microsoft/vscode/blob/master/.yarnrc)

-- 
Hubert Chathi <uhoreg at debian.org> -- https://www.uhoreg.ca/
Jabber: hubert at uhoreg.ca -- Matrix: @uhoreg:matrix.org
PGP/GnuPG key: 4096R/F24C F749 6C73 DDB8 DCB8  72DE B2DE 88D3 113A 1368