feat: support update peerDependencies

[LarchLiu]

Description

I am facing the same issue as mentioned in #46, so I added it.

Linked Issues

#46

Additional context

Maybe some additional param should be added? The current way of handling this is the same as optionalDependencies.

[antfu]

I think it was not added intentionally, as peerDeps are not really your dependencies but rather a specification of the range of deps the library supports. IMO, peerDeps should be as loose as possible to support a wider range of usages, and should not need to be upgraded frequently.

[Mister-Hope]

I think it was not added intentionally, as peerDeps are not really your dependencies but rather a specification of the range of deps the library supports. IMO, peerDeps should be as loose as possible to support a wider range of usages, and should not need to be upgraded frequently.

I agree the point, and this PR is unacceptable as it's including as the default behavior. but there are situations where peer are expected to bump: during the next major development.

For example, when you are trying to develop a new major of a eslint-plugin for eslint9 when it's staring alpha stage, the peer might be expected to be "locked" to a single version of alpha|beta|rc dep as there are possible breaking changes in the next version for eslint.

npm-check-updates has such a option for the peer bump and it needs opt-in, so I think adding such an option is meaningful.

In my usage, I am trying to bump vuepress/ecosystem with vuepress/core and we are in rc stage.