Gar

Rebased in #52

one of the requirements for npm packages is that their version field conform to [`semver`](https://docs.npmjs.com/about-semantic-versioning). See the docs for more info https://docs.npmjs.com/cli/v7/configuring-npm/package-json#version

~Tested against `latest` and this is no longer happening w/ the example repo. This was fixed by https://github.com/npm/cli/pull/7499~ Sorry, missed the `eslint@9` step. This is still happening.

> Surely the global install path should be in your $PATH variable, right? This was one thing npm bin -g checked for. The global install path should already be in...

This is very good feedback @molisani thank you for laying it out so clearly. Can you open a new issue in https://github.com/npm/rfcs suggesting we reintroduce a global only bin command?...

Here is a more detailed writeup of the v10 changes. Tasklists don't allow annotations like this in sub-bullet-points so I'm putting it here. # v10 breaking changes - [x] Engines...

user-agent switchover https://github.com/npm/make-fetch-happen/pull/255

Most of the smaller v10 changes in the cli https://github.com/npm/cli/pull/6641

Copied from v10 initiative ## v11 and beyond These are still future looking breaking changes that we want to keep in consideration going forward ```[tasklist] ### Breaking Changes: - [...

I just lost an hour of my day to this "clever" helpful line. We should drop support for this. https://github.com/npm/cli/blob/1114a12f2b4691d403d0863d4dca44f25580f57d/lib/cli-entry.js#L9-L12 ```js // if npm is called as "npmg" or "npm_g",...