> Would that differ from the general ecosystem? The npm command itself tells you to run `npm update -g` to grab the latest version every time you run it, so I would assume many/most people would already be running the latest npm against whichever Node version they were using. Am I mistaken?
I don't think that is the case. I believe most people stick with the version that has been validated/shipped with Node.js itself. I'll ask in our Node.js/JavaScript chat room to see what other people think. On Wed, Sep 7, 2022 at 9:41 AM Stephen Gallagher <[email protected]> wrote: > On Wed, Sep 7, 2022 at 9:31 AM Michael Dawson <[email protected]> wrote: > > > > By > > > I think there’s more value in making sure that the latest npm is > compatible with the older runtimes and standardize on that. > > > > Do you mean use that by default for all versions of Node.js? That would > be different than the general ecosystem and the most/best tested > combinations. > > > Would that differ from the general ecosystem? The npm command itself > tells you to run `npm update -g` to grab the latest version every time > you run it, so I would assume many/most people would already be > running the latest npm against whichever Node version they were using. > Am I mistaken? > > > > On Tue, Sep 6, 2022 at 7:51 PM Neal Gompa <[email protected]> wrote: > >> > >> On Tue, Sep 6, 2022 at 7:22 PM Frank R Dana Jr. <[email protected]> > wrote: > >> > > >> > > On Tue, Sep 6, 2022 at 5:03 PM Frank R Dana Jr. <ferdnyc(a) > gmail.com> wrote: > >> > > > >> > > I don’t think there’s really any value in using a different version > of > >> > > Node.js than the default to run npm, barring an exceptionally > serious bug. > >> > > Can you provide a specific example where it would matter? > >> > > >> > Not a definitive one, no. My main concern would be packages that > might install a different version, or install themselves differently > (different dependencies pulled in, etc.), based on the node version they're > being installed with — or is that not something npm supports? > >> > >> It does. It can definitely do that, especially with nodejs extension > modules. > >> > > I expect in the overwhelming majority of cases, people will only > install one Node.js version into the system, and therefore the > alternatives system will take care of this. In those other cases, is > `/usr/bin/node-18 /usr/bin/npm` particularly onerous? Is > `/usr/bin/npm-18` any better (it could be confusing)? I don't think > there's any accurate way to auto-detect which Node version you > intended to run against if there is more than one on the system. So > *somehow* the user would need to specify it explicitly. I'm open to > suggestions on how this could be done. > _______________________________________________ > 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] > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue >
_______________________________________________ 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] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
