Confusing pnpm resolution

[jamestalmage]

I'd used proto pin pnpm 11 which generates an entry in .protools. It appears it is overridden by whatever is set as packageManager in package.json...

I think that's probably the right place for the config, as it allows other tools/build environments to resolve the correct package manager, but I think that means proto should refuse to pin it, or at least issue a warning if it's configured both places

[milesj]

@jamestalmage By default we use whichever version is found first: https://moonrepo.dev/docs/proto/config#detect-strategy

If you look at the logs, it will tell you where its coming from. But if they are in the same dir, it should prioritize proto first.

[jamestalmage]

They were definitely the same directory, and package.json was winning... Either way... I think the default should raise a warning or an exception when it finds both. Once someone picks an explicit strategy, then just silently follow the strategy.