Set specific "package.json" in the repo as main file

[bombillazo]

Description

It would be great to specify one package.json file within the monorepo to act as the "main" file, meaning this file is a version driver from which all other files are resolved to. Doing so will automatically limit all other packages from raising the versions if this package.json is lower than the rest while bringing the rest to the latest version specified in this main file.

Suggested Solution

Have a new option in the configuration/cli to specify this "main" package.json file.

[JamieMason]

Hi Hector,
For the upcoming hoist feature there's the idea of a --target file and multiple --source files, but in the general case of syncing versions I think this idea in its current form could be unintuitive. Could you go into some more detail? Maybe a specific command for this use case would be clearer. Thanks.

[bombillazo]

Yes, after using this library a bit, I could envision this new feature as another optionGroup type configuration where you specify a group of files and the "main" file from which the semver will be inherited. This is useful when one is required to keep specific versions stable but instead of creating versionGroups, one could use a specific package.json as the driver for the rest of the files. In my case with a monorepo, one app inside the repo is determining the versions for the rest of the apps, including the root deps.

[JamieMason]

Closing as duplicate of #87