Managing peerDependency versions at the root

Expected Behavior

As a developer, I’d like to be able to manage SOME of my packages’ peerDependencies at the root of my project.

Directory structure

package.json
| -- packages
     | -- foo
         | -- package.json
     | -- bar
         | -- package.json

foo’s package.json

{
  ...
  "peerDependencies": {
    "@angular/core": "NG_VERSION"
  } 
  ...
}

bar’s package.json

{
  ...
  "peerDependencies": {
    "@angular/core": "NG_VERSION"
  } 
  ...
}

root package.json

{
  ...
  "dependencies": {
    "@angular/core": "^8.0.0"
  } 
  ...
}

Current Behavior

I couldn’t find anything in the docs regarding this model, and as it stands, this makes version management of common packages across a large number of libraries extremely painful.

Possible Solution

Provide a way to link the peerDependency of a package to the root’s version.

lerna.json

{
  "packages": [
    "apps/*",
    "libs/*"
  ],
  "version": "0.0.1"
}

Context

I’d like to make common version management of my packages easier.

Your Environment

lerna --version
3.13.1

[damienwebdev]

@MunifTanjim what I’m saying is that when I run lerna publish I would like to use the variable version from the root as opposed to having to manage the same peerDependency in each package that depends upon it within my monorepo.

Apologies for the lack of clarity.

For example, if you publish fifteen libraries that depend on "react" : "^6.0.0" from the same monorepo, I would like to make sure that I don’t have to increment the react peerDependency in every single package when react publishes a new major version. I would instead like to be able to define it at the root and utilize the root version at publish time for lerna publish.

lerna.json
{
 "variables": {
    "NG_VERSION" : "^8.0.0"
  }
}

would even be sufficient.

[RoryH]

FEATURE