I've just submitted a review request for separating out NPM into its own package (again). This is being done for a couple reasons:
1) To get rid of the ridiculous release field and take advantage of the %autorelease macro 2) I'm planning to rework how the nodejs packages work to make different versions parallel-installable (with the alternatives infrastructure owning /usr/bin/node). I want to keep NPM in a common location (/usr/lib/node_modules) so that it will work with whatever Node is in use. If someone on this list would be willing to perform the package review, I'd be appreciative. ---------- Forwarded message --------- From: <bugzi...@redhat.com> Date: Wed, Apr 13, 2022 at 2:27 PM Subject: [Bug 2075170] New: Review Request: npm - A JavaScript Package Manager To: <sgall...@redhat.com> https://bugzilla.redhat.com/show_bug.cgi?id=2075170 Bug ID: 2075170 Summary: Review Request: npm - A JavaScript Package Manager Product: Fedora Version: rawhide Hardware: All OS: Linux Status: NEW Component: Package Review Severity: medium Priority: medium Assignee: nob...@fedoraproject.org Reporter: sgall...@redhat.com QA Contact: extras...@fedoraproject.org CC: package-rev...@lists.fedoraproject.org Target Milestone: --- Classification: Fedora Spec URL: https://copr-dist-git.fedorainfracloud.org/cgit/sgallagh/npm/npm.git/plain/npm.spec SRPM URL: https://download.copr.fedorainfracloud.org/results/sgallagh/npm/srpm-builds/04217393/npm-8.6.0-1.fc37.src.rpm Description: npm is the world's largest software registry. Open source developers from every continent use npm to share and borrow packages, and many organizations use npm to manage private development as well. npm consists of three distinct components: * the website * the Command Line Interface (CLI) * the registry Use the [*website*](https://npmjs.com) to discover packages, set up profiles, and manage other aspects of your npm experience. For example, you can set up [organizations](https://www.npmjs.com/features) to manage access to public or private packages. The [*CLI*](https://docs.npmjs.com/cli/npm) runs from a terminal, and is how most developers interact with npm. The [*registry*](https://docs.npmjs.com/misc/registry) is a large public database of JavaScript software and the meta-information surrounding it. ## Use npm to . . . * Adapt packages of code for your apps, or incorporate packages as they are. * Download standalone tools you can use right away. * Run packages without downloading using [npx](https://www.npmjs.com/package/npx). * Share code with any npm user, anywhere. * Restrict code to specific developers. * Create organizations to coordinate package maintenance, coding, and developers. * Form virtual teams by using organizations. * Manage multiple versions of code and code dependencies. * Update applications easily when underlying code is updated. * Discover multiple ways to solve the same puzzle. * Find other developers who are working on similar problems and projects. Fedora Account System Username: sgallagh -- You are receiving this mail because: You reported the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2075170 _______________________________________________ nodejs mailing list -- nodejs@lists.fedoraproject.org To unsubscribe send an email to nodejs-le...@lists.fedoraproject.org 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/nodejs@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
