intlify / bridging Goto Github PK

Clear and concise description of the problem

About exported composables

See the release note:
https://github.com/vuejs/vue-router/blob/dev/CHANGELOG.md#360-2022-08-22

Suggested solution

we need support native [email protected] composables

Alternative

No response

Additional context

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guide.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): replace dependency npm-run-all with npm-run-all2 ^5.0.0
• chore(deps): update actions/cache action to v4
• chore(deps): update actions/setup-node action to v4
• chore(deps): update dependency globby to v14
• chore(deps): update dependency lint-staged to v15
• chore(deps): update dependency rimraf to v5
• chore(deps): update secretlint monorepo to v8 (major) (@secretlint/secretlint-rule-preset-recommend, secretlint)
• chore(deps): update stefanzweifel/git-auto-commit-action action to v5
• chore(deps): update typescript-eslint monorepo to v7 (major) (@typescript-eslint/eslint-plugin, @typescript-eslint/parser)
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

github-actions

.github/workflows/ci.yml

• actions/checkout v4
• pnpm/action-setup v2
• actions/setup-node v4
• actions/checkout v4
• pnpm/action-setup v2
• actions/setup-node v4
• actions/cache v3
• actions/checkout v4
• actions/setup-node v4
• actions/checkout v4
• actions/setup-node v4
• actions/checkout v4
• actions/setup-node v4
• actions/checkout v4
• pnpm/action-setup v2
• actions/setup-node v4

.github/workflows/github-label-sync.yml

• r7kamura/github-label-sync-action v0

.github/workflows/release.yml

• actions/checkout v4
• actions/setup-node v3
• pnpm/action-setup v2
• jungwinter/split v2
• stefanzweifel/git-auto-commit-action v4

npm

package.json

• @secretlint/secretlint-rule-preset-recommend ^7.0.7
• @types/js-yaml ^4.0.5
• @types/node ^20.6.0
• @typescript-eslint/eslint-plugin ^6.6.0
• @typescript-eslint/parser ^6.6.0
• bumpp ^9.2.0
• eslint ^8.49.0
• eslint-config-prettier ^9.0.0
• eslint-plugin-prettier ^5.0.0
• globby ^12.0.2
• jiti ^1.20.0
• js-yaml ^4.1.0
• lint-staged ^14.0.1
• mlly ^1.4.2
• node-actionlint ^1.2.1
• npm-run-all ^4.1.5
• pathe ^1.1.1
• pkg-types ^1.0.2
• playwright ^1.40.1
• prettier ^3.0.3
• rimraf ^3.0.2
• secretlint ^7.0.7
• typescript ^5.2.2
• node >= 14.6

packages/vue-i18n-bridge/package.json

• vue-i18n ^8.26.1 || >=9.2.0
• vue-i18n-bridge >=9.2.0
• @vue/composition-api ^1.0.0-rc.1
• node >= 12

packages/vue-router-bridge/package.json

• vue-demi >=0.13.5 < 1.0.0
• vue-router ^4.0.0-0 || ^3.0.0
• @vue/composition-api ^1.0.0-rc.1
• node >= 12

---

• Check this box to trigger a request for Renovate to run again on this repository

Clear and concise description of the problem

Hello,
i18n for nuxt3 @nuxtjs/i18n@next requires vue-i18n-routing and this modules requires @intlify/vue-router-bridge from this repo

problem is
vue-i18n-routing requires "vue-demi": "^0.14.5"
but @intlify/vue-router-bridge requires "vue-demi": "^0.13.5"

in npm ^ means: update until first non zero version number will change; so with package with zero major (first) version only patch (third) version can update

and this incompatibility cause issues in installing nuxt project with i18n at all
see
nuxt-modules/i18n#1640
nuxt-modules/i18n#2556
and many more issues

Suggested solution

i found this commit 82ef441 already updated vue-demi to ^0.14 which will fix issues

can you release new version of @intlify/vue-router-bridge with this change?

Alternative

maybe you can use ~0.13 instead of ^0.13
~ means that only major (first) version can not change in update, and then ^0.14 and ~0.13 will be compatible

Additional context

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guide.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.