nx migrate latest should update buildable lib dependency versions

[markgoho]

• I'd be willing to implement this feature (contributing guide)

Description

When running nx migrate latest a migration script should be added to update all dependency versions in any buildable libraries.

Motivation

Right now, we have an application with many buildable libraries. When we generate those libraries for the first time the generator uses the current version of Angular to write the package.json e.g.

"peerDependencies": {
  "@angular/common": "^12.2.0",
  "@angular/core": "^12.2.0"
},
"dependencies": {
  "tslib": "^2.3.0"
}

However, as we migrate to new versions of Angular, these package.json are left untouched. The library above was created more than a year ago and has remained on Angular 12 since that time.

Suggested Implementation

I think this feature would enhance the migration functionality to ensure some agreement between the root package.json Angular version and the version present in all the libraries.

It seems like there may be some folks out there that would want to keep their buildable libraries on the version of Angular that they were initially built with, but my assumption is that a vast majority of folks would rather have these angular versions update as the project Angular version is updated.

Alternate Implementations

We could do a codebase search/find and replace to update all outdated versions of Angular to the one that's currently active in the root.

[thatsBruno]

I ran into the same issue, any work around?

[sebastianhaberey]

I was wondering the same today when I stumbled across the peerDependencies of my libraries. They were all still Angular 15 even though I thought I had migrated my project completely to Angular 17.