chore: update vue-component-type-helpers to current version

[kingyue737]

Fix unmatched peer deps warning

 WARN  Issues with peer dependencies found
├─┬ @nuxt/content 3.6.3
│ └─┬ nuxt-component-meta 0.12.2
│   └─┬ vue-component-meta 3.0.5
│     └── ✕ unmet peer vue-component-type-helpers@3.0.1: found 3.0.5

[pkg-pr-new]

Open in StackBlitz

vue-component-meta

npm i https://pkg.pr.new/vuejs/language-tools/vue-component-meta@5589

vue-component-type-helpers

npm i https://pkg.pr.new/vuejs/language-tools/vue-component-type-helpers@5589

@vue/language-core

npm i https://pkg.pr.new/vuejs/language-tools/@vue/language-core@5589

@vue/language-plugin-pug

npm i https://pkg.pr.new/vuejs/language-tools/@vue/language-plugin-pug@5589

@vue/language-server

npm i https://pkg.pr.new/vuejs/language-tools/@vue/language-server@5589

@vue/language-service

npm i https://pkg.pr.new/vuejs/language-tools/@vue/language-service@5589

vue-tsc

npm i https://pkg.pr.new/vuejs/language-tools/vue-tsc@5589

@vue/typescript-plugin

npm i https://pkg.pr.new/vuejs/language-tools/@vue/typescript-plugin@5589

commit: 7376039

[johnsoncodehk]

@ghiscoding When a workspace package is added to peerDependencies, it seems to cause version numbers to become out of sync when running lerna version. Is this expected behavior?

language-tools/packages/component-meta/package.json

Lines 20 to 23 in 1b98031

	"peerDependencies": {
	"typescript": "*",
	"vue-component-type-helpers": "3.0.5"
	},

[ghiscoding]

Lerna/Lerna-Lite doesn't touch peer dependencies by default because typically a package manager should never bump peer deps by itself since that is more of a user configuration and shouldn't be automated (it was explained by the original Lerna's author a while ago). But if you do want the tool to bump them, I added a new flag some time ago --allow-peer-dependencies-update which is in Lerna-Lite only

From original Lerna's author:

Changes to a peer version range are always semver major, and should be as broad as possible. Until we can get fancier, we should never automatically modify them to match the new version being published (which is the current incorrect behavior).

[johnsoncodehk]

Thank you for the clarification!