Use workspace's dependencies versions as source of truth in fix-mismatches

[bompus]

Description

When running fix-mismatches in a folder containing a pnpm workspace, it always uses the highest version found in any of the packages, instead of the version specified in the workspace root, which I personally use as the source of truth for shared external dependencies.

Suggested Solution

I'd like a setting to prefer the dependencies versions listed in the workspace's root package.json, instead of the highest version found in any of the workspace projects. This allows quick dependencies / devDependencies / peerDependencies version downgrades across an entire workspace by simply updating the root package.json and then running fix-mismatches.

[JamieMason]

At first I didn't think this was already a feature, but while working on 6.0.0 I saw that this should already be the case:

syncpack/src/bin-fix-mismatches/fix-mismatches.ts

Lines 27 to 29 in fd7ef19

	const nextVersion =
	getWorkspaceVersion(name, input.wrappers) ||
	getHighestVersion(instances.map(({ version }) => version));

Please give 6.0.0 a try and reopen this issue if this does indeed need adding.

Thanks a lot.

[chbdetta]

How does this work again? I am using an npm workspace and it doesn't use my root package.json as the source of truth

[JamieMason]

How does this work again? I am using an npm workspace and it doesn't use my root package.json as the source of truth

I think at the time I misread this issue as being reporting a bug in `--workspace`, where we use the versions of packages developed in your monorepo as the source of truth. I think I realise now what you're asking for is the `snapTo` feature. If you follow #87 you can track progress.