Community Packages

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#73637 - [electron] standardize electron-based application packaging

Attached to Project: Community Packages
Opened by BrLi (brli) - Saturday, 05 February 2022, 13:12 GMT
Last edited by Andreas Radke (AndyRTR) - Wednesday, 16 February 2022, 07:30 GMT
Task Type Feature Request
Category Packages
Status Assigned
Assigned To Nicola Squartini (tensor5)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No



There are currently plenty of electron-based applications in the official repo.

With different package style.

Some includes the raw node_modules directory, some are using app.asar

There is the execute script, mime-type xml and .desktop, but not all of them are always separated into single file and put to source array.

And, most of the time, there are wastes for other OS, or readme, license, dot files etc. in the downloaded node modules, you may also want to avoid them.

node-prune is a neat golang-based tool for that.

Maybe the team needs to come up with a standardized electron packaging style so that packagers have rules to follow.

Additional info:
* package version(s) electron9, 11, 12, 13, 14, 15, 16(current latest)
* config and/or log files etc.
* link to upstream bug report, if any

Steps to reproduce:
This task depends upon