Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update vite & vue packages (major) #101

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 25, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@intlify/unplugin-vue-i18n (source) ^1.4.0 -> ^6.0.0 age adoption passing confidence
@julr/vite-plugin-validate-env ^0.2.4 -> ^1.0.0 age adoption passing confidence
@vitejs/plugin-vue (source) 4.6.2 -> 5.2.1 age adoption passing confidence
@vueuse/core (source) 10.7.2 -> 12.0.0 age adoption passing confidence
vite (source) 5.0.12 -> 6.0.3 age adoption passing confidence
vite-plugin-vue-devtools (source) 1.0.0-rc.8 -> 7.6.8 age adoption passing confidence
vue-i18n (source) 9.9.1 -> 10.0.5 age adoption passing confidence
vue-tsc (source) 1.8.27 -> 2.1.10 age adoption passing confidence

Release Notes

intlify/bundle-tools (@​intlify/unplugin-vue-i18n)

v6.0.1

⚡ Improvement Features
  • #​421 fix(unplugin-vue-i18n): check for vue compiler in directive transform hook (@​userquin)
Committers: 1

v6.0.0

⭐ Features
Committers: 1

v5.3.1

🐛 Bug Fixes
  • #​414 fix(unplugin-vue-i18n): don't analyze identifiers in vue files when using pug/jsx/tsx languages (@​userquin)
Committers: 1

v5.3.0

🐛 Bug Fixes
  • #​413 fix(unplugin-vue-i18n): remove directives plugin warnings on SSR build (@​userquin)
Committers: 2

v5.2.0

⭐ Features
Committers: 1

v5.1.0

⭐ Features
Committers: 1

v5.0.0

⚡ Improvement Features
Committers: 1

v4.0.0

Compare Source

⚡ Improvement Features
Committers: 1

v3.0.1

Compare Source

🐛 Bug Fixes
Committers: 1

v3.0.0

Compare Source

⚡ Improvement Features
  • #​349 breaking(unplugin-vue-i18n): deprecate around some options for Vue 2 (@​kazupon)
⚠️ Deprecated Features
  • #​349 breaking(unplugin-vue-i18n): deprecate around some options for Vue 2 (@​kazupon)
Committers: 1

v2.0.0

Compare Source

💥 Breaking Change
  • #​334 BREAKING CHANGE: drop @intlify/vite-plugin-vue-i18n/messages virtual module ID (@​kazupon)
⚠️ Deprecated Features
  • #​334 BREAKING CHANGE: drop @intlify/vite-plugin-vue-i18n/messages virtual module ID (@​kazupon)
Committers: 1
Julien-R44/vite-plugin-validate-env (@​julr/vite-plugin-validate-env)

v1.2.0

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v1.1.1

Compare Source

Fixes

    View changes on GitHub

v1.1.0

Compare Source

   🚀 Features
    View changes on GitHub

v1.0.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v1.0.0: 1.0.0

Compare Source

Breaking Changes

Before, the plugin didn't really work at 100%, or at least, it wasn't totally type safe. Only strings were stored in import.meta.env. Even when using z.number() or Schema.number(). Same for all other types other than string. It's all fixed now, everything works as expected. We've changed our strategy and now use define from vite rather than process.env.

This is the main reason for this major version change.

Features

  • Added a debug property in the plugin configuration that allows process.env to be logged before the vite-plugin-validate-env processing

Fixes

  • Previously, when .env file was modified and the vite dev server was running, the changes were not taken into account. This is now fixed

New Contributors

Full Changelog: Julien-R44/vite-plugin-validate-env@v0.2.5...v1.0.0

vitejs/vite-plugin-vue (@​vitejs/plugin-vue)

v5.2.1

v5.2.0

  • feat: add a feature option to support custom component id generator (#​461) (7a1fc4c), closes #​461

v5.1.5

v5.1.4

v5.1.3

v5.1.2

v5.1.1

  • fix(plugin-vue): clear script cache if recall (f5eb5ac), closes #​431

v5.1.0

v5.0.5

v5.0.4

v5.0.3

v5.0.2

  • fix: ensure consistent user template options when reusing AST (bc0ad64), closes #​322
  • fix: only enable ast reuse for vue 3.4.3+ (4a53b6f)
  • chore: bump vue to 3.4.2 (97002e1)

v5.0.1

v5.0.0

  • Breaking: drop reactivityTransform support
  • Breaking: drop Node 14/16 support
  • Breaking: drop Vite 4.x support
  • Vue 3.4 template AST reuse support
  • Vue 3.4 compile-time flag __VUE_PROD_HYDRATION_MISMATCH_DETAILS__ support
  • Added customElement option
  • Deprecated defineModel option
vueuse/vueuse (@​vueuse/core)

v12.0.0

Compare Source

   🚨 Breaking Changes

[!NOTE]
To Vue 3 users, v12.0.0 is equivalent to v11.3.0 on behaviors, only to remove some Vue 2 specific handling and will be slightly lighter. We expect future development to contain on v12.x and forward, and only backport if there are security issues. This means that VueUse would no longer be active on Vue 2 support.

    View changes on GitHub

v11.3.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v11.2.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v11.1.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v11.0.3

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v11.0.1

Compare Source

v11.0.0

Compare Source

   🚨 Breaking Changes
   🚀 Features
   🐞 Bug Fixes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/major-vite-and-vue-packages branch 10 times, most recently from 7a45f79 to c118ded Compare December 2, 2023 12:56
@renovate renovate bot force-pushed the renovate/major-vite-and-vue-packages branch 16 times, most recently from 2db1c13 to 1cd6394 Compare December 10, 2023 12:20
@renovate renovate bot force-pushed the renovate/major-vite-and-vue-packages branch 4 times, most recently from 3e4cfbd to 19c9921 Compare December 12, 2023 16:29
@renovate renovate bot force-pushed the renovate/major-vite-and-vue-packages branch 11 times, most recently from f697586 to 5165c8d Compare November 28, 2024 19:28
@renovate renovate bot force-pushed the renovate/major-vite-and-vue-packages branch 8 times, most recently from 0df9e5e to c2c2886 Compare December 6, 2024 10:26
@renovate renovate bot force-pushed the renovate/major-vite-and-vue-packages branch 6 times, most recently from d98af0f to 039d5eb Compare December 12, 2024 15:03
@renovate renovate bot force-pushed the renovate/major-vite-and-vue-packages branch 3 times, most recently from 4e94ac1 to 147d1bf Compare December 17, 2024 18:23
@renovate renovate bot force-pushed the renovate/major-vite-and-vue-packages branch from 147d1bf to 1f3fe2f Compare December 18, 2024 00:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants