Bug#842420: electron packaging
I just filed a couple of RFPs for electron apps and immediately added this one as a blocker:
https://bugs.debian.org/842420
So yes there are some trending messaging apps and code editors built with electron !
Packaging it would be a huge task also because it is a mixed-language project.
sloccount reports:
cpp: 59225 (61.39%)
javascript: 29379 (30.46%)
ansic: 3833 (3.97%)
python: 3205 (3.32%)
sh: 824 (0.85%)
But electron is definitely part of the js ecosystem (exactly as nodejs) so we should be brave and pick it up.
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",
- 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)
Paolo
Reply to: