Packaging the Javascript layer of Prometheus & Grafana

[Nicolas Mailhot]

Hi,

I'm currently investigating the packaging of Prometheus and Grafana in 
Fedora/Epel.

Both are cutting-edge high-visibility complex applications written in 
Go, that map well to Fedora/Epel historical sysadmin userbase
https://prometheus.io/
https://grafana.com/

I already spent a few months of work working on the Go layer, writing 
Golang-to-rpm plumbing, packaging guidelines, packaging and testing 
hundreds of spec files. It is finally looking like something that could 
end up in the distribution, even though there is still a ton of work to 
do plumbing-side to make Go packaging in Fedora simple and convenient. 
And I'd like to spend more time making this plumbing a reality.

However, at the same time, the target apps can not be used, since they 
include a javascript layer, and I haven't packaged it.

Prometheus provides a bundled copy of the javascript it needs, thus I 
supposed it could be packaged as-is, even though that is bad engineering 
and totally not what I did for the Go layer.
https://github.com/prometheus/prometheus/tree/master/web/ui/static/vendor

Grafana OTOH has a clean codebase with a build process that uses yarn to 
get third-party javascript
https://github.com/grafana/grafana/blob/master/yarn.lock

Therefore, I'm looking for help :
   1. either pointers or advice on how to package this javascript cleanly 
or
   2. ideally, people willing to take over this javascript packaging, so 
I can focus on finishing the Golang plumbing in Fedora

I suppose this is also a test if a distribution like Fedora/Epel can 
still be used to deploy the kind of apps written in 2018, or if it's 
condemned to fade and be replaced by other approaches like containers.

Regards,