On 29/07/2020 22:38, Troy Dawson wrote:
I wanted to get a list of essential nodejs packages, and I thought of getting a list of nodejs packages that are required by non-nodejs packages.
How have you defined essential?
That list is amazingly small. # Binaries / Runtime packages statsd -> nodejs-generic-pool R-shiny -> nodejs-showdown notepadqq -> nodejs-shelljs mocha -> uglify-js and nodejs-jade kosmtik -> 11 nodejs libraries jake -> 5 nodejs libraries elasticdump -> 3 nodejs libraries discord-irc -> 10 nodejs libraries carto -> 4 nodejs libraries
As both kosmtik and carto originate with me - indeed kosmtik is kind of the original cause of my involvement in Node.js pacaging I can comment a bit on those. I wouldn't actually worry too much about keeping kosmtik to be honest. While carto is probably more useful the current version is rather out of date, because of tricky dependency issues in the newer versions so that dependency count will go up if it is updated I think. I also wonder if you missed some build/test toolchains that are required? Only that is where of the nasty trees of dependencies are I think. Tom -- Tom Hughes ([email protected]) http://compton.nu/ _______________________________________________ nodejs mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected]
