3 ms·
Point 4 has been implemented but I don't know how well it's adopted https://docs.npmjs.com/cli/v7/commands/npm-fund https://docs.npmjs.com/cli/v7/commands/npm-
by seniorsassycat 5y ago
Point 4 has been implemented but I don't know how well it's adopted
https://docs.npmjs.com/cli/v7/commands/npm-fund https://docs.npmjs.com/cli/v7/commands/npm-fund.
Point 3 is interesting, does it work across non-apt package managers?
- rezonant 5y agoFor that matter what about across different distros that all use apt but have different package names for the same piece of software?
- pxc 5y ago> Point 3 is interesting, does it work across non-apt package managers? At the very least it's not harmful. You could use something like repology or your own index to identify equivalent packages and then install them. Really what you'd want would be a package manager-agnostic way to declare dependencies on things outside the Node universe, and then plugins for NPM that could use to assert they were satisfied in an appropriate per-package-manager way, and maybe optionally try to install them for you using the appropriate external package manager. But the packagers for Node projects wouldn't be writing the mechanisms for that, they'd just be declaring the deps.