Gar

The root cause here is that `new URL` doesn't actually uri encode. It looks like it does cause it encodes *some* things. But the `new URL` will happily parse a...

Re-adding this to npm means first making it a proper config item. That is being done [here](https://github.com/npm/cli/pull/8129). `@npmcli/run-script` will also need to be made aware of this new config and...

Is there no other value available to us that lets us make a reasonable guess here? 16GB seems quite large. My system is only a few years old and that...

So this is a case where npm is being ran from pnpm for one of the various subtasks that it delegates to npm? Very interesting. Is there some sort of...

It looks like pnpm sets `npm_config_user_agent` in the environment, which npm will pick up and set as its own user-agent config ``` ~ $ set -x npm_config_user_agent 'gar/test 1.0.0 neat'...

I don't think it's outside the realm of practicality to parse the user-agent in a way that informs the packageManager portion of the engines check. Your points are valid though,...

One solution could be that we update the devEngines spec to isolate for certain commands. Unfortunately npm will currently exit with an error if it encounters invalid properties in the...

> OIDC is only implemented in the client We definitely have plans to isolate that code into a separate package, the initial implementation didn't do that because we didn't know...

Just to make sure we're thinking through all the possible iterations here. There is an `engine-strict` flag that npm has which is the equivalent to the `fail` config for `devEngines`....

Good point, ignoring devEngines altogether is likely more clear than trying to say "just don't log the warnings"