Sorry, but this completely miss the point and unfortunately your view is quite limited.

For example, we have rubygem-uglifier, rubygem-jquery-rails, rubygem-coffee-script etc, which originally bundles JS libraries, but thanks to js-* counterparts, we were able unbundle them. If we have not unbundled them yet, it is typically because nobody bothered to follow the guidelines and provide the correct js- packages.

V.

Hi,

This page

https://fedoraproject.org/wiki/Packaging:JavaScript

is terribly outdated. Even when it was created years ago, IMO the advice was questionable. Today, it's definitely bad advice.

Modern web applications use webpack for JavaScript. With webpack, JavaScript is minified and bundled, and sometimes assets are even injected. I realize bundling libraries is bad for an old-school RPM-based application. But no one packages JavaScript into RPMs (try to find react and friends), and the page is leading to confusion on my team.

To prevent confusion, acceptable options would be: either simply deleting the page, or placing a giant "don't follow this outdated advice" banner at the top.

Best wishes,

Greg

-- 

GREG SHEREMETA

SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX

Red Hat NA

gshereme@redhat.com    IRC: gshereme

_______________________________________________
packaging mailing list -- packaging@lists.fedoraproject.org
To unsubscribe send an email to packaging-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/packaging@lists.fedoraproject.org/message/J4LSN4I5YQA4HHTE6PM3JCOZ57YX5XDE/