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

⬆️ Bump vue from 2.7.16 to 3.0.0 #58

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

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Oct 25, 2024

Bumps vue from 2.7.16 to 3.0.0.

Changelog

Sourced from vue's changelog.

3.0.0 (2020-09-18)

3.0.0-rc.13 (2020-09-18)

Bug Fixes

  • hmr: make hmr working with class components (#2144) (422f05e)
  • reactivity: avoid length mutating array methods causing infinite updates (#2138) (f316a33), closes #2137
  • suspense: should discard unmount effects of invalidated pending branch (5bfcad1)
  • types: component instance inference without props (#2145) (57bdaa2)

Code Refactoring

Features

  • runtime-core: support using inject() inside props default functions (58c31e3)
  • watch: support dot-delimited path in watch option (1c9a0b3)

BREAKING CHANGES

  • watch APIs now default to use flush: 'pre' instead of flush: 'post'. This change affects watch, watchEffect, the watch component option, and this.$watch. See (49bb447) for more details.

3.0.0-rc.12 (2020-09-16)

Bug Fixes

  • reactivity: effect should only recursively self trigger with explicit options (3810de7), closes #2125
  • runtime-core: ensure root stable fragments inherit elements for moving (bebd44f), closes #2134
  • runtime-core: should still do full traverse of stable fragment children in dev + hmr (dd40ad8)
  • runtime-core/async-component: fix error component when there are no error handlers (c7b4a37), closes #2129
  • types/tsx: optional props from Mixin/Extends are treated as required (#2048) (89e9ab8)

Features

  • compiler-sfc: additionalData support for css preprocessors (#2126) (066d514)

3.0.0-rc.11 (2020-09-15)

... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

Summary by CodeRabbit

  • New Features

    • Upgraded to Vue.js version 3.0.0, introducing new features and improvements.
  • Bug Fixes

    • Enhanced compatibility with other dependencies due to the major version update.

Bumps [vue](https://github.com/vuejs/core) from 2.7.16 to 3.0.0.
- [Release notes](https://github.com/vuejs/core/releases)
- [Changelog](https://github.com/vuejs/core/blob/v3.0.0/CHANGELOG.md)
- [Commits](https://github.com/vuejs/core/commits/v3.0.0)

---
updated-dependencies:
- dependency-name: vue
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Oct 25, 2024
@ThomasAFink
Copy link
Member

@coderabbitai full review

Copy link

coderabbitai bot commented Nov 29, 2024

Walkthrough

The pull request involves a significant update to the package.json file, specifically changing the version of the Vue.js framework from "vue": "^2.7.16" to "vue": "^3.0.0". This upgrade reflects a transition to a newer major version of Vue, which may influence compatibility with other dependencies and the overall application structure. No other dependencies or configurations within the file were modified.

Changes

File Change Summary
package.json Updated Vue dependency from "vue": "^2.7.16" to "vue": "^3.0.0"

Poem

In the garden of code, we hop with glee,
Upgrading Vue, as bright as can be!
From two to three, we leap and bound,
New features await, oh what joy we've found!
With every change, our project will thrive,
Hopping along, keeping our dreams alive! 🐇✨


🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Outside diff range and nitpick comments (1)
package.json (1)

Incompatible Vue dependencies detected

Several dependencies are using Vue 2.x versions and are incompatible with Vue 3:

  • vue-router v3.6.5 is a Vue 2 version (Vue 3 requires v4.x)
  • vuex v3.6.2 is a Vue 2 version (Vue 3 requires v4.x)
  • vue-i18n v8.28.2 is a Vue 2 version (Vue 3 requires v9.x)
  • vuetify v2.7.2 is a Vue 2 version (Vue 3 requires v3.x)
  • vue-class-component v7.2.6 and vue-property-decorator v9.1.2 are Vue 2 versions and the composition API is recommended for Vue 3
  • vue-toastification v1.7.14 is a Vue 2 version (use v2.x for Vue 3)
  • vuex-persist v3.1.3 requires Vuex 3 (Vue 2), needs upgrade to support Vuex 4

The codebase is still using Vue 2 patterns and imports (import Vue from 'vue'), which are incompatible with Vue 3. Either downgrade Vue to v2.x or upgrade all dependencies to their Vue 3 compatible versions.

🔗 Analysis chain

Line range hint 14-29: Verify compatibility of other dependencies with Vue 3

Please verify these dependencies are compatible with Vue 3:

  • vue-toastification: Might need upgrade or replacement
  • vuex-persist: Check Vue 3/Vuex 4 compatibility
  • moment: Consider using date-fns or luxon as recommended by Vue team
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for Vue 3 compatible versions of dependencies

# Check latest versions and Vue 3 compatibility
for pkg in vue-toastification vuex-persist; do
  echo "Checking $pkg:"
  curl -s "https://registry.npmjs.org/$pkg" | jq -r '.["dist-tags"].latest, .versions[] | select(contains("vue3"))'
done

Length of output: 677


Script:

#!/bin/bash
# Let's try a different approach to check package versions and their dependencies

# Check package.json for current versions
echo "Current package versions:"
cat package.json | jq '.dependencies'

# Search for Vue 3 migration guides or documentation in the codebase
echo -e "\nSearching for Vue 3 migration related files:"
fd -t f -e md -e txt | xargs rg -l "vue 3|migration|upgrade" || true

# Check if there are any Vue 2 specific imports or usage
echo -e "\nChecking Vue 2 specific usage:"
rg "import.*from 'vue'" -A 2

# Check for Vuex store setup
echo -e "\nChecking Vuex store setup:"
fd store.ts -o store.js | xargs cat || true

Length of output: 2475

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 3b3f4a8 and cd59fd0.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (1)
  • package.json (1 hunks)
🔇 Additional comments (1)
package.json (1)

20-20: Verify the impact on existing components

Let's analyze the codebase to understand the scope of required changes:

@@ -17,7 +17,7 @@
"@fontsource/roboto": "^5.0.12",
"graphemer": "^1.4.0",
"moment": "^2.30.1",
"vue": "^2.7.16",
"vue": "^3.0.0",
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

❌ Cannot upgrade to Vue 3 without upgrading ecosystem packages first

This direct upgrade to Vue 3 will break the application as several critical dependencies are still Vue 2 specific:

  • vue-router (v3)
  • vuex (v3)
  • vuetify (v2)
  • vue-class-component (v7)
  • vue-i18n (v8)
  • vue-property-decorator (v9)
  • vue-toastification (v1)

Here's a recommended migration path:

  1. First, upgrade these packages to their Vue 3 compatible versions:
-    "vue-router": "^3.6.5",
+    "vue-router": "^4.0.0",
-    "vuex": "^3.6.2",
+    "vuex": "^4.0.0",
-    "vuetify": "^2.7.2",
+    "vuetify": "^3.0.0",
-    "vue-i18n": "^8.28.2",
+    "vue-i18n": "^9.0.0",
  1. Replace class-based components:
  • Remove vue-class-component and vue-property-decorator
  • Migrate to either Options API or Composition API
  1. Update testing setup:
-    "@vue/test-utils": "1.3.6",
+    "@vue/test-utils": "^2.0.0",
-    "@vue/vue2-jest": "^27.0.0",
+    "@vue/vue3-jest": "^27.0.0",
  1. Consider these alternatives:
  • Replace Vuex with Pinia (recommended by Vue team)
  • Use Vuetify 3 Beta if stable version isn't available
  • Find Vue 3 compatible alternatives for other plugins

Would you like me to:

  1. Create a detailed migration guide as a new issue?
  2. Generate a migration script to help identify components that need updates?

Committable suggestion skipped: line range outside the PR's diff.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant