-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
RFC: remove node packages #14532
Copy link
Copy link
Closed as not planned
Labels
2.status: stalehttps://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.mdhttps://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md6.topic: nodejsNode.js is a free, open-source, cross-platform JavaScript runtime environmentNode.js is a free, open-source, cross-platform JavaScript runtime environment9.needs: reporter feedbackThis issue needs the person who filed it to respondThis issue needs the person who filed it to respond
Metadata
Metadata
Assignees
Labels
2.status: stalehttps://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.mdhttps://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md6.topic: nodejsNode.js is a free, open-source, cross-platform JavaScript runtime environmentNode.js is a free, open-source, cross-platform JavaScript runtime environment9.needs: reporter feedbackThis issue needs the person who filed it to respondThis issue needs the person who filed it to respond
Fields
Give feedbackNo fields configured for issues without a type.
I just had a look at
node-packages-generated.nix. While I didn't go through every single package basically any package that I picked out was utterly outdated. I sure hope nobody is relying on those packages and so I currently see little value in having those.In #13103 (comment) @svanderburg comments:
I would thus suggest to do exactly that: remove most of
node-packages.jsonleaving only what falls into one of the two categories above.It is too bad that interfacing with npm is such a flakey business so the integration cannot be automated further to allow for up to date packages with less manual work. Which is exactly the reason why the scope of included node packages should be limited.
I'm happy to provide a PR if this OK with everyone.
/cc @zimbatm @lo1tuma