pnpm install --ignore-package-manager-version about pnpm HOT 8 CLOSED

Sorry, we forgot to document it. You can disable it by setting package-manager-strict to false

from pnpm.

I'm confused with the minor versions strict check. In my understanding this is not how semantic versioning works. So at least having the flag would be great.

from pnpm.

I'm confused with the minor versions strict check. In my understanding this is not how semantic versioning works. So at least having the flag would be great.

The issue with packageManager is that it does not check for semver at all but always uses exact matching. This is not a problem by pnpm, but how the committee decided to implement packageManager.
https://nodejs.org/api/packages.html#packagemanager

However, while corepack just picks the correct needed package manager, pnpm now fails hardly when the "wrong" pnpm version is installed on the computer 😕 and this is annoying, especially when using multiple projects with different packageManager values

from pnpm.

How do I use it?

pnpm install --package-manager-strict false

does not work 🤔
and results in

Unknown option: 'package-manager-strict'
Did you mean 'engine-strict'? Use "--config.unknown=value" to force an unknown option.

from pnpm.

See linked PR. There is an ENV property to set, other than the package.json field.

from pnpm.

I did salsita/node-pg-migrate#1105 for now, but I would prefer if it is possible to also do via CLI flag

from pnpm.

You can do pnpm install --config.package-manager-strict=false

from pnpm.

You can do pnpm install --config.package-manager-strict=false

This works on direct terminal (pnpm install --config.package-manager-strict=false) ✅,
but not when I wrap inside a package.json script 👀

e.g.

{ 
  "scripts": {
    "preflight": "pnpm install --config.package-manager-strict=false && run-s format lint build"
  }
}

pnpm run preflight

from pnpm.